It hasn’t happened to me yet, but enabling the Converter Enterprise plug-in apparently can crash your VC 2.5 Server. VMware Communities: Enabling Converter Enterprise Plugin … is a forum thread about the problem with some troubleshooting attempts and the resolution. From the VMware forum:

I had exactly the same problem and this was caused by a dll file confict, in my case I had an old version of the ssleay32.dll file in my windows\system32 directory. I removed the file and it now works correctly.

Yellow-bricks.com also reports on the problem with 2 posts and an alternative fix in the follow up - Part II post:

For those who did not have any luck with the deleting of the dll(ssleay32.dll) described in this blog, there’s another possibility to enable the VMware Converter plugin without crashing your VirtualCenter client:

    Go to the following registry key:

[HKEY_CURRENT_USER\Software\VMware\VMware Infrastructure Client\Preferences\UI]

    And set the following key to "Enabled"

“C:\\Program Files\\VMware\\Infrastructure\\Virtual Infrastructure Client\\Plugins\\Converter Enterprise\\plugin.dll”

Part I of the yellow-bricks.com post on this topic can be read here.

Related Posts

• Use VMware Converter to Solve ESX Snapshot Issues (5)
• FREE Disk space monitoring solutions for VMware virtual infrastructure (0)
• P2V multi processor servers to single processor VMs (8)
• Why do I need to install VMware Tools? (10)
• Configuration of host IP address is inconsistent on host - VMware HA issues (2)
• P2V error: File size is larger than maximum size supported by datastore (3)
• Current VirtualCenter customization wizard needs changes for Server 2008 (3)
• Put VM info on the desktop with BGInfo (0)
• Use the VI Client to bulk upgrade VM tools (2)
• P2V a Suse Linux Enterprise Server (2)

Tags: blogs, how to, issues, plugin, virtualcenter, vmware, vmware converter, windows, yellow-bricks.com

This entry was posted on Thursday, February 7th, 2008 at 12:12 pm and is filed under P2V, blogs, converter, esx3.5, how to, vc2.5. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.