Vmware vCenter Converter Standalone 5 - Fatal Error Occurred

[scerazy]

Standalone on Server 2003 VM (one that I used ever since with v3 & then v4

Upgraded to v5, it starts & then clicking on Convert Machine it givs "nice" error:

Vmware vCenter Converter Standalone Fatal Error Occurred.  The most common reason for this is loss of network connection.
The wizard will now be closed.
Please check your network connection and try again

This - is not a solution in my case as I have no devices

Log shows:

2012-03-15T12:29:54.477Z [00188 info 'Ufa'] Plugin started
2012-03-15T12:29:54.477Z [00756 info 'Libs'] HOSTINFO 1204981260 @ 3579545Hz -> 0 @ 1000000000Hz
2012-03-15T12:29:54.477Z [00756 info 'Libs'] HOSTINFO ((x * 2343484437) >> 23) + -336629728041
2012-03-15T12:29:54.602Z [00188 info 'Default'] [serviceWin32,413] vmware-converter-server service started
2012-03-15T12:30:11.477Z [00188 info 'Default'] [user,890] Successfully authenticated user Administrator
2012-03-15T12:30:15.993Z [00188 info 'Default'] [user,890] Successfully authenticated user Administrator
2012-03-15T12:30:36.602Z [00756 error 'Default'] SSLStreamImpl::BIORead (0313e008) timed out
2012-03-15T12:30:36.618Z [00756 error 'Default'] SSLStreamImpl::DoClientHandshake (0313e008) SSL_connect failed with BIO Error
2012-03-15T12:30:36.618Z [00756 error 'HttpConnectionPool'] [ConnectComplete] Connect error SSL Exception: The SSL handshake timed out.
2012-03-15T12:30:36.649Z [00772 info 'vmomi.soapStub[0]'] Resetting stub adapter for server PIPE:\\.\pipe\vmware-converter-worker-soap : Closed
2012-03-15T12:30:36.649Z [00772 error 'Default'] SSL Exception: The SSL handshake timed out.
2012-03-15T12:30:55.633Z [00188 info 'Default'] [user,890] Successfully authenticated user Administrator
2012-03-15T12:31:02.602Z [00772 info 'Default'] [user,890] Successfully authenticated user Administrator
2012-03-15T12:31:03.102Z [00772 error 'Default'] Found dangling SSL error: [0] error:00000001:lib(0):func(0):reason(1)
2012-03-15T12:31:23.118Z [00772 error 'Default'] SSLStreamImpl::BIORead (03103008) timed out
2012-03-15T12:31:23.133Z [00772 error 'Default'] SSLStreamImpl::DoClientHandshake (03103008) SSL_connect failed with BIO Error
2012-03-15T12:31:23.133Z [00772 error 'HttpConnectionPool'] [ConnectComplete] Connect error SSL Exception: The SSL handshake timed out.
2012-03-15T12:31:23.133Z [00188 info 'vmomi.soapStub[1]'] Resetting stub adapter for server PIPE:\\.\pipe\vmware-converter-worker-soap : Closed
2012-03-15T12:31:23.133Z [00188 error 'Default'] SSL Exception: The SSL handshake timed out.

Seb

[UmeshAhuja]

Hi,

Request you to check 4 points

1) Cross check wether NetBIOS over TCP/IP is enable in your physical server.

2) Windows Installer , Windows module Installer and WMI Performance adapter and Virtual disk services are running.

3) Windows firewall service is stop

4) All the below mention ports are open in firewall.

Source	Destination	TCP  Ports	UDP  Ports	Notes
Converter  server	Source  computer	445, 139, 9089  or 9090	137,  138	If   the source computer  uses NetBIOS, port 445 is not required. If  NetBIOS  is not being used, ports 137,  138, and 139 are not required.  If in  doubt, make sure that none of the ports are  blocked. Port 9089 is  used for Converter Standalone versions, and 9090 is used for the Converter  plugin. Note:   Unless you  have installed Converter server to the source computer,  the  account used for  authentication to the source computer must have  a  password, the source computer  must have network file sharing  enabled,  and it cannot be using Simple File  Sharing.
Converter  server	VirtualCenter	443		Only required if the  conversion target is VirtualCenter.
Converter  client	Converter  server	443		Only required if a custom  installation was performed and the Converter server and client portions are on  different computers.
Source  computer	ESX	443,  902		If the conversion target  is VirtualCenter then only port 902 is required.

[ivivanov]

Hmm, this usually means Converter Server cannot connect to Converter Worker service. You said you have *upgraded* from Converter 4.x - I would suggest try uninstall and then clean reinstall.

[scerazy]

I have uninstalled & re-installed (kind of basic approach!)

yes, it means the very thing, yet I can not figure out why...

Seb

[ivivanov]

Is the Converter Woker service running?

[scerazy]

Yes it is (it would be too easy otherwise...)

Seb

[ivivanov]

One more easy question - is the worker process PID changing after each "disconnect" (in other words - is the worker service restarted)?

[scerazy]

It stays the same, the service does not crash/restart

I honestly have up to here various Vmware bits not working

Feel like constantly chasing a tail, just to get something working...

Seb

[POCEH]

What about firewall/ports? Please upload log bundle for investigation.

[scerazy]

Eventually deleted

rui.key
rui.crt

Repaired the installation

It then reinstalled the certificates with these dates of vailidy (how does that happen?) from 20/08/2011 to 19/09/2011

Ofcourse the certificate is

This certificate has expired or is not yet valid.

but at least converter works

Pure madness

Seb