Convert ESXi to Hyper-V - The server refused connection

[AussieCraig]

Hi,

I'm attempting to use V2V Converter to migrate a VM from ESXi vers 5.1 to Hyper-V on WS2019. Running V2VConv from the Hyper-V server. VM is off. The ESXi server has Veeam installed.

V2VConv can see and read the VMs on the ESXi server, and successfully creates the VM in Hyper-V, but it's getting the following errors when attempting to convert the image file (extract from log file):

1/9 16:31:13.934 1d9c Facility ???INFO: CPPConverting::ConvertImage: pathInput: [datastore1] MGMTPC01/MGMTPC01.vmdk, pathOutput: D:\VMs\MGMTPC01\MGMTPC01-System.vhdx
1/9 16:31:13.997 1d9c Facility ???INFO: ESXVmdk::ParseFile: sFilename - [datastore1] MGMTPC01/MGMTPC01.vmdk
1/9 16:31:13.997 1d9c Facility ???INFO: ESXVmdk::ParseFile: m_cSSLThumbprint - 4B:87:C3:BC:ED:8A:C4:31:C8:A8:3F:20:09:06:F3:B2:4A:79:E9:DD
1/9 16:31:13.997 1d9c Facility ???INFO: ESXVmdk::ParseFile: m_cvmxSpec - [datastore1] MGMTPC01/MGMTPC01.vmx
1/9 16:31:14.731 1d9c Facility ???ERROR: ESXVmdk::ParseFile: m_VixDiskLib_Open is fail - 14009, The server refused connection
1/9 16:31:14.731 1d9c Facility ???ERROR: ESXIDisk::CreateInputImage: ParseFile is fail
1/9 16:31:14.731 1d9c Facility ???INFO: CPPConverting::ConvertImage: CreateInputImage: 1
1/9 16:31:14.731 1d9c Facility ???ERROR: CPPConverting::Convert: FAILED

I noted other posts in this forum suggesting this may be a networking/firewall issue but I've tried disabling Windows firewall on the Hyper-V host and have verified all inbound ports on the ESXi host are enabled. The NFS Client wasn't enabled on the ESXi host - tried enabling this but it didn't help.

[yaroslav (staff)]

Greetings,

Welcome to StarWind Forum.
From what I see in the log, there is a communication problem. You can try copying the VMDK to the WS 2019 and converting the VMDK to VHDX as a local file.

[AussieCraig]

Hi Yaroslav,
Many thanks for the prompt response.
I can confirm that copying the VMDK, via the vSphere web client, to the WS2019 host did the trick. All good now.
Thanks again,
Craig

[yaroslav (staff)]

You are welcome

[aaronramsdale]

The server refused connection because nothing is listening on the IP:Port you are trying to connect to. So you can change IP and try again. Good luck!

[yaroslav (staff)]

Exactly.