VMware Cloud Community
JSCSJSCS
Contributor
Contributor

VSphere Converter Client cause vSphere Client to crash without error notice

I had some issue with the vSphere Client just dissapearing when I tried to load it. It was running, but for some reason it stopped loading. I uninstalled everything and reinstalled. After getting the client to to run again, I connected to vShere vCenter Server and went to plugins and started the vCenter Converter Plugin download process. After it downloaded, the application began to install the converter client on the local laptop. When the application finished installing, the vSphere Cleint application dissapeared again and would not run again as before.

I uninstalled the Converter Client from the laptop and the vShere Client was able to load without issue.

So what do you think? There are not errors in the event log. I am running Vista Ultimate with SP1 on a fairly well configured laptop.

Jim s.

0 Kudos
3 Replies
JSCSJSCS
Contributor
Contributor

Thanks to Atmos4. How the heck did you figure that out?! I renamed my libeay32.dll and ssleay32.dll files. I never found a libssl32.dll, but no matter. Then I rebooted and tried to install the converter client again. Afterward, I was able to load the vSphere client! I would have thought that if those files were causing a problem, a new install would reinstall them, but they are not back. So, I don't know whay those DLL's were on my laptop, what used them, or why they caused vSphere Client to not boot or crash, but my issue seems to be solved is solved thanks to you.

Jim S.

0 Kudos
AndyShinn
Contributor
Contributor

Just wanted to reply with a little more information since it seems the post from Atmos4 is gone?

The files to remove are actually libeay32.dll and ssleay32.dll in the WIndows System32 directory (C:\Windows\system32on my Windows 2008 server). It seems as if the client is trying to load the SSL libraries from the system directory first, if they exist, then its own directory. In my case the SSL libraries provided by VMware and the ones in system32 were different versions (0.9.7 vs 0.9.) which is likely causing the crash for the VMware Converter Plugin.

0 Kudos
admin
Immortal
Immortal

I'm a little late to the game here but I saw this KB article discussing this:

Enabling the Converter plug-in in VirtualCenter causes VMware

Infrastructure Client to fail

http://kb.vmware.com/kb/1005446

Rick Blythe

Social Media Specialist

VMware Inc.

0 Kudos