mellerbeck

vpxclient.exe runtime error vsphere vcenter import crashes

So I ran across the lovely error that vcenter would crash when I would go to import a machine. After much googling I finally ran across this post

http://www.vmware.com/support/vsphere4/doc/vsp_vcc_41_rel_notes.html

This is the jist of it

Microsoft Visual C++ Runtime Library error message is displayed during import or export of a machine
If a user environment has versions of VI Client 2.5 Update 1, Update 2, Update 3, or Update 4 that coexist with vSphere Client 4.0, and you install the vCenter Converter 4.1.0 client plug-in, when you start the vCenter Converter Import or Export wizard, the vSphere Client session is terminated abruptly. An OpenSSL DLL conflict between the VI Client versions and the vCenter Converter 4.1.0 client plug-in causes this problem.
Workaround: Go to the Launcher folder in the VI Client install directory, for example, C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher, and delete the following DLL files from that location:

  • libeay32.dll
  • ssleay32.dll

I deleted these file from my windows\system32 folder (after verifying that the timestamp was old) and this did the trick.

11 comments

  7. I’ve been having trouble with converters for months from every vendor. Finally got my vShpere licenses and thought I’d start converting and CRASH.

    Thanks for posting this and stopping more hair loss!

    Reply

  9. Thought I would just mention that if you have nmap installed on your virtual centre server as we did, then you will need to either remove nmap from your path or remove these same dll’s. Then restart the Vmware Virtual center service and restart the vCenter converter service.

    Reply

Leave a comment