VMware vSphere

 View Only
Expand all | Collapse all

Unable to connect to Convert Enterprise Server

  • 1.  Unable to connect to Convert Enterprise Server

    Posted Apr 07, 2008 02:49 AM

    is there any reason why when I try to do an import a machine from within my VI client, it say "Unable to connect to Convert Enterprise Server"? I have both VC 2.5 and VMware Convert Enterprise install on the same server. I try to restart the converter service without any help. Any idea?

    dwc



  • 2.  RE: Unable to connect to Convert Enterprise Server

    Posted Apr 07, 2008 02:53 AM

    Your post has been moved to the VMware Converter forum

    Dave Mishchenko

    VMware Communities User Moderator



  • 3.  RE: Unable to connect to Convert Enterprise Server

    Posted Apr 07, 2008 02:55 AM

    sorry, didn't know if the enterprise version fall with the same forum as the standalone

    dwc



  • 4.  RE: Unable to connect to Convert Enterprise Server
    Best Answer

    Posted Apr 21, 2008 08:01 AM

    for me this happend after i changed the ip address from the virtual center server. solution to fix the problem was to de-install and re-install the Converter Enterprise.

    changing the ip manually in the xml file didn't solved the problem in my case.



  • 5.  RE: Unable to connect to Convert Enterprise Server

    Posted May 19, 2008 07:58 PM

    This also happened to me and I did not change the IP of my VirtualCenter but my License Server got changed and buggered up the Converter.

    The fix was indeed to uninstall it from my VirtualCenter and reinstall it.



  • 6.  RE: Unable to connect to Convert Enterprise Server

    Posted Jun 11, 2008 12:03 PM

    Thanks guys for the tip, that solved my problem as well !



  • 7.  RE: Unable to connect to Convert Enterprise Server

    Posted May 14, 2009 05:37 PM

    Yes, I've had this issue for a while too. Restarting the converter service on vCenter worked for me.



  • 8.  RE: Unable to connect to Convert Enterprise Server

    Posted Jun 08, 2009 11:15 PM

    I did both.

    Restarted service on VC and ran "repair" on enterprise converter install on my local machine.

    Converter is operational again. :smileyhappy:



  • 9.  RE: Unable to connect to Convert Enterprise Server

    Posted Jun 17, 2008 09:57 AM

    is it any other way to solve this problem rather than uninstall the Converter Enterprise Server and install back....

    I have tried to do... but I still having problem in importing a machine to the esx server!!



  • 10.  RE: Unable to connect to Convert Enterprise Server

    Posted Jul 31, 2008 03:13 PM

    You can go to add/remove programs.. choose converter enterprise server - click change.. then click repair.. enter the new servername/ip.. worked for me.



  • 11.  RE: Unable to connect to Convert Enterprise Server

    Posted May 13, 2009 01:34 PM

    You can also try logging into your VC and restarting the Converter service. Thats what I do whenever I run into that problem.



  • 12.  RE: Unable to connect to Convert Enterprise Server

    Posted Jun 10, 2009 07:24 PM

    This worked for me.

    Thanks,

    JD



  • 13.  RE: Unable to connect to Convert Enterprise Server

    Posted Jul 08, 2009 03:11 PM

    You can go to add/remove programs.. choose converter enterprise server - click change.. then click repair.. enter the new servername/ip.. worked for me[/quote]

    Good call, worked well for me.



  • 14.  RE: Unable to connect to Convert Enterprise Server

    Posted Jul 10, 2009 01:34 PM

    The solution stated is correct on the uninstall. However, I just did a repair on VMWare Converter Enterprise and that solved the issue.



  • 15.  RE: Unable to connect to Convert Enterprise Server

    Posted Jul 30, 2009 01:19 AM

    Just had this issue too, restarting the Converter service on VI server took care of it for me as well. Thanks for the tip.



  • 16.  RE: Unable to connect to Convert Enterprise Server

    Posted Sep 28, 2009 03:42 PM

    I did a change/modify from add remove programs for converter and did a reinstall. It worked like a charm!

    thanks everyone for the updates and advice.