VMware Cloud Community
pascuzzi
Contributor
Contributor
‎04-27-2007 11:01 AM

Convert 3.0.1 will not conect to my Virtual Center

I have just upgraded to Converter 3.0.1. When trying to connect to My Virtual Center ( 2.0.1) I get an error message saying that the managed host was actually running ESX 2.x, rather than 3.x or VC.

I was able to use converter before the upgrade to connect to the host.

I can still convert by going directly to the ESX server.

Is there something I need to change in my configuration of the VC?

0 Kudos
6 Replies
lvi123
Contributor
Contributor
‎04-27-2007 01:03 PM

Can you please check what port numbers do you have set under Administration => VirtualCenter Management... => Web Service? This is in the VirtualCenter client GUI.

0 Kudos
pascuzzi
Contributor
Contributor
‎04-27-2007 01:17 PM

I am using 8080 not 443 for https to the virtual center server. Looking in the log file the new version of Converter is trying to use 443.

My esx servers are using 443, so thats why it can connect to them

2007-04-27 14:07:23.609 'P2V' 3272 verbose] \[task,388] Transition succeeded

\[2007-04-27 14:07:23.609 'P2V' 3272 info] \[task,274] Starting execution of a Task

\[2007-04-27 14:07:23.625 'GetInventory' 3272 info] Connecting to host vc2.try.sybase.com on port 443 using protocol https

\[2007-04-27 14:07:24.718 'App' 3272 error] \[rpcConnectionWrapper,172] Failed to establish Vim connection to vc2.try.sybase.com. Vmacore::Exception: No connection could be made because the target machine actively refused it.

\[2007-04-27 14:07:24.750 'P2V' 3272 verbose] \[utils,77] Socket read succeeded, ret=86

\[2007-04-27 14:07:24.750 'P2V' 3272 verbose] \[utils,86] data="220 VMware Authentication Daemon Version 1.10: SSL required, MKSDisplayProtocol:VNC

0 Kudos
lvi123
Contributor
Contributor
‎04-27-2007 01:28 PM

Try entering vc2.try.sybase.com:8080 in Converter GUI when specifying VC location.

0 Kudos
pascuzzi
Contributor
Contributor
‎04-27-2007 01:48 PM

Thanks. That works

0 Kudos
JonnyT
Contributor
Contributor
‎06-11-2008 01:30 PM

I am getting the same error message when trying to select a destination for my converter. I just downloaded the newest VMware Server and VirtualCenter and am pretty new to the VM world..

"The managed host was actually running ESX 2.x, rather than 2.x or VC"

The statement above did not help.

0 Kudos
theanykey
Virtuoso
Virtuoso
‎06-12-2008 10:13 AM

Can you upgrade converter to 3.0.3 (www.vmware.com/downloads/converter)

Can you then choose the IP address of your ESX server using username "root" for your destination? This is assuming you have ESX 3.x

0 Kudos