Hello.

I've the same problem.

I'm running VC 2.5 (with ESX 3.5 U2) on Windows XP SP3 French version.

I've already tried to change TEMP and TMP variables path with no effect.

To perform P2V, I've completed the operation with VMWARE converter standalone.

What happened with Virtuel Center ?

Thanks

I had this same error and found two different ways to fix it:

1) Use monderick's method and create/use a local admin account

2) Delete any network connections to the physical server you are trying to import and re-run the Import wizard

a. Open Command Prompt

b. Identify the connections to remove by running:>net use

c. Remove the connections to the server by running:>net use \ \<servername>\IPC$ /del

(remove spaces between \ \)

d. Re-run Import Wizard and import the physical server

I have the same problem on VSpere. When I click on next after the disk size options it crashes

This is a big problem for us. It is on new Intel Neharlem CPU's . We have 2 other VSphere Dell m1000 invironmets running on AMD with out any problems.

What could be the problem here ?

It looks like the problem is on the vCenter Server side. All the clients from different PC's crash with this error if you point it to the vCenter on the Intel CPU. When you log into the vCenter running on the AMD platform all is OK and you can import the machines with no problems. All the patches have been loaded on both systems. This is very frustrating as we have other problems with the Intel CPU as well. Can sombody tell me were the logs are that I should have a look at?

Thanks

hello jaco

i have the same problem . but i have to know did you mean that you don't have problem when you run the plugin on amachine running the vsphere client with amd platform or the vcenter machine itself lies on an amd platform.

best regards

jacky