I am trying to move a virtual machine from a VCenter Essential 4.1 ESXi host to a new 5.5 ESX stand alone host server. I attempted to use the current version of Converter standalone and keep getting the same error. Converter fails with a message stating:
2014-09-07T21:30:37.121-04:00 [11148 error 'ConversionState'] Submit job failed: An error occured while opening a virtual disk. Verify that the Converter server and the running source machines have a network access to the source and destination ESX/ESXi hosts.
Looking up this error it seemed to indicate a DNS error using the host names between the machines which I verified were all working. Also verified ports 443 and 902 were not blocked between all related machines. Further investigation revealed the following in the worker logs:
2014-09-07T21:30:37.011-04:00 [04840 warning 'Default'] [,0] SSL_IsVerifyEnabled: failed to open the product registry key. Falling back to default behavior: verification on. LastError = 0
2014-09-07T21:30:37.011-04:00 [04840 warning 'Default'] [,0] SSL: Unknown SSL Error
2014-09-07T21:30:37.011-04:00 [04840 warning 'Default'] [,0] SSL: connect failed
2014-09-07T21:30:37.011-04:00 [04840 warning 'Default'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: The remote host certificate has these problems:
-->
--> * The host certificate chain is incomplete.
-->
--> * Host name does not match the subject name(s) in certificate.
-->
--> * unable to get local issuer certificate
2014-09-07T21:30:37.011-04:00 [04840 info 'Default'] Sysimgbase_DiskLib_OpenWithPassPhrase failed with 'NBD_ERR_NETWORK_CONNECT' (error code:2338)
2014-09-07T21:30:37.011-04:00 [04840 info 'Default'] Error 2338 opening disk ha-nfcssl://[Datastore2] WVIns-Data/WVIns-Data.vmdk@localhost.localdomain:902!52 62 eb ca de 30 b8 d8-e1 77 ab c7 ff be 48 8c.
2014-09-07T21:30:37.011-04:00 [04840 warning 'Default'] ERROR 2338 opening disk ha-nfcssl://[Datastore2] WVIns-Data/WVIns-Data.vmdk@localhost.localdomain:902!52 62 eb ca de 30 b8 d8-e1 77 ab c7 ff be 48 8c.
2014-09-07T21:30:37.011-04:00 [04840 error 'Default'] [BaseDiskSetComputer::DoOpen] OpenDisks failed, mntapi error: 37410
2014-09-07T21:30:37.011-04:00 [04840 error 'Default'] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 37410 MNTAPI errorType = 2, errorCode = 2338
2014-09-07T21:30:37.011-04:00 [04840 error 'Default'] TargetVmManagerImpl::CreateVM: Failed to retrieve the storage mapping with error converter.fault.ManagedDiskOpenFault
2014-09-07T21:30:37.011-04:00 [04840 info 'Default'] TargetVmManagerImpl::CreateVM: The target VM will be deleted now.
2014-09-07T21:30:37.011-04:00 [04840 info 'Default'] TargetVmManagerImpl::DeleteVM
2014-09-07T21:30:37.011-04:00 [04840 info 'Default'] Reusing existing VIM connection to localhost.localdomain
2014-09-07T21:30:37.011-04:00 [04840 info 'Default'] Destroying vim.VirtualMachine:23 on localhost.localdomain
2014-09-07T21:30:37.089-04:00 [04840 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds
2014-09-07T21:30:37.105-04:00 [04840 info 'vmomi.soapStub[43]'] Resetting stub adapter for server <cs p:02709048, TCP:localhost.localdomain:443> : Closed
I get this same error after attempting the conversion several different ways:
1) Installed converter on Windows 4.1 VCenter server and attempted to run from there by referencing the VCenter host and running with domain admin credentials using host names for the servers.
2) Installed converter on Windows 4.1 VCenter server and attempted to run from there by referencing the VCenter host and running with domain admin credentials using IP addresses for the servers.
3) Installed converter on Windows 4.1 VCenter server and attempted to run from there by referencing the ESXi host name and running with domain admin credentials using IP addresses for the servers.
4) Installed converter on Windows 2003 server that was a domain member and attempted to run from there by referencing the VCenter host and running with domain admin credentials using host names for the servers.
5) Installed converter on Windows 2003 server that was a domain member and attempted to run from there by referencing the VCenter host and running with domain admin credentials using IPs for the servers.
6) Installed converter on Windows 2003 server that was a domain member and attempted to run from there by referencing the ESXi host name and running with domain admin credentials using IP addresses for the servers.
All attempts give the same errors. I've used the registry setting to modify the SSL verification requirement but still get the same error. I've installed the VMDDK 5.1 update 2 which changes the SSL requirement as well and still get the same error. This doesn't make sense.
This is a small customer and we really don't care about SSL authentication of the VMs. Any thoughts or suggestions would be greatly appreciated.
Thanks.
Any help is greatly appreciated.