Hi everyone.
I was used VMware Converter Standalone 6.0 to converter server 2003 on Hyper-V to host ESX of vCenter.
Hyper-V have IP : 10.132.2.200
vCenter have IP: 10.132.2.177
Host ESXi have IP : 10.132.2.192
We haven't policy firewall for 3 IP this. All ports are open in Firewall.
But, when I convertering 1% that have error with status : FAILED: An error occurred during the conversion: 'The operation experienced a network error'
So, Can you help me fix case this ?
Best regards.
Hello Hongchuong
it really looks like a blocked network communication. You write no firewall is blocking it but let's get into more details. The connection needs to be established from the Hyper-V host (10.132.2.200) to the ESXi host (10.132.2.192) on port 902, as in log lines:
2015-07-12T14:03:46.634+07:00 info vmware-converter-agent[03900] [Originator@6876 sub=task-1] establishing nfc connection to host 10.132.2.192 port 902
2015-07-12T14:03:47.193+07:00 info vmware-converter-agent[03900] [Originator@6876 sub=task-1] Sysimgbase_Nfc_PutFile source disk: E:\MayAo_Hyp\Hyp2K3-LT\Virtual Hard Disks\Hyp2K3-Goc_5110F977-7064-4B81-9452-BDAE36EE9C9D.avhd, target disk [Datastore-SAN2] Hyp2K3-HDND/Hyp2K3-HDND.vmdk
2015-07-12T14:06:44.992+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2015-07-12T14:06:44.992+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFile_SendMessage: data send failed:
2015-07-12T14:06:44.992+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] The operation experienced a network error -- Failed to send data message
2015-07-12T14:06:45.056+07:00 error vmware-converter-agent[03900] [Originator@6876 sub=task-1] Sysimgbase_Nfc_PutFile failed in H2MDiskCloneMgr with nfcError 'The operation experienced a network error' (error code:3)
2015-07-12T14:06:45.069+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] SSL: Unknown SSL Error
2015-07-12T14:06:45.069+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2015-07-12T14:06:45.069+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR
An easy way to try the connectivity is telnet from the Hyper-V host to the ESX host on port 902
I see you have also tried again to destination 10.132.2.191 with the same error. It is possible the Hyper-V firewall is blocking.
HTH
Plamen
Can you provide a log bundle of the failed task?
Hello
can upload the task log bundle? (right click on the failed task and export) The GUI and server logs are not very informative, the worker and agent logs are.
Regards,
Plamen
Hello Hongchuong
it really looks like a blocked network communication. You write no firewall is blocking it but let's get into more details. The connection needs to be established from the Hyper-V host (10.132.2.200) to the ESXi host (10.132.2.192) on port 902, as in log lines:
2015-07-12T14:03:46.634+07:00 info vmware-converter-agent[03900] [Originator@6876 sub=task-1] establishing nfc connection to host 10.132.2.192 port 902
2015-07-12T14:03:47.193+07:00 info vmware-converter-agent[03900] [Originator@6876 sub=task-1] Sysimgbase_Nfc_PutFile source disk: E:\MayAo_Hyp\Hyp2K3-LT\Virtual Hard Disks\Hyp2K3-Goc_5110F977-7064-4B81-9452-BDAE36EE9C9D.avhd, target disk [Datastore-SAN2] Hyp2K3-HDND/Hyp2K3-HDND.vmdk
2015-07-12T14:06:44.992+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2015-07-12T14:06:44.992+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcFile_SendMessage: data send failed:
2015-07-12T14:06:44.992+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] The operation experienced a network error -- Failed to send data message
2015-07-12T14:06:45.056+07:00 error vmware-converter-agent[03900] [Originator@6876 sub=task-1] Sysimgbase_Nfc_PutFile failed in H2MDiskCloneMgr with nfcError 'The operation experienced a network error' (error code:3)
2015-07-12T14:06:45.069+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] SSL: Unknown SSL Error
2015-07-12T14:06:45.069+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcNetTcpWrite: bWritten: -1
2015-07-12T14:06:45.069+07:00 warning vmware-converter-agent[03900] [Originator@6876 sub=Default] [,0] [NFC ERROR] NfcSendMessage: send failed: NFC_NETWORK_ERROR
An easy way to try the connectivity is telnet from the Hyper-V host to the ESX host on port 902
I see you have also tried again to destination 10.132.2.191 with the same error. It is possible the Hyper-V firewall is blocking.
HTH
Plamen
Dear Plamen !
I was checked to like you guide.
From Hyper-V server I can telnet to IP's ESXi port 902 but can't telnet to IP's vCenter port 902.
So, I can open port 902 on v-Center and Can you guide me ?
Thanks.
Hello hongchuong
You don't need to open port 902 on the vCenter server.
However there has been a bug related to V2V from Hyper-V with sparse disks, which has the same symptoms.
As a workaround you may try to force file-level cloning (I haven't tested that but hope it will work). You may, e.g, shrink a destination volume a little or change the cluster size to force file-level.
HTH
Plamen
Dear Plamen !
Yesterday, I was tried to converter a job and it was completed.
Although I wasn't changed any on firewall device and firewall soft on windows.
We can close the ticket for this case.
Thank and best regards.
I experienced a similar issue with VMware Converter 6.0 last week whilst trying to convert a Hyper-V 2008 R2 VM to VMware ESXi 5.5. The error message was totally misleading as it was not a network problem at all. I managed to resolve my issue by modifying the configuration of the destination virtual disks.
You can find more information here - http://timcarman.net/2015/07/20/vmware-converter-the-operation-experienced-a-network-error/
Thanks for your post. This saved myday
The link above is broken. What was the solution?
I am also interested in the solution!
I also think the error is very misleading and has nothing to do with firewalls or networking. I went into the host to see what is it that Standalone is doing and found that it connects on port 902 just fine but it is looking for things that don't exist and then it drops the connection. Here's the vmauthd.log from my host:
2022-03-26T21:32:41Z vmauthd[2667108]: Connect from remote socket (192.168.20.220:49582).
2022-03-26T21:32:41Z vmauthd[2667108]: Connect from 192.168.20.220
2022-03-26T21:32:42Z vmauthd[2667108]: Received PROXY command for vpxa-nfcssl, session = 52 48 37 99 f9 8e 82 f5-63 08 f0 fe f0 39 ac 3c
2022-03-26T21:32:42Z vmauthd[2667108]: vmware-vpxa: Connected to vpxa-nfcssl-fd, remote end sent pid: 2099167
2022-03-26T21:32:44Z vmauthd[2667109]: Msg_SetLocaleEx: HostLocale=UTF-8 UserLocale=NULL
2022-03-26T21:32:44Z vmauthd[2667109]: Could not expand environment variable HOME.
2022-03-26T21:32:44Z vmauthd[2667109]: Could not expand environment variable HOME.
2022-03-26T21:32:44Z vmauthd[2667109]: DictionaryLoad: Cannot open file "/usr/lib/vmware/config": No such file or directory.
2022-03-26T21:32:44Z vmauthd[2667109]: DictionaryLoad: Cannot open file "~/.vmware/config": No such file or directory.
2022-03-26T21:32:44Z vmauthd[2667109]: DictionaryLoad: Cannot open file "~/.vmware/preferences": No such file or directory.
2022-03-26T21:32:44Z vmauthd[2667109]: lib/ssl: OpenSSL using FIPS_drbg for RAND
It's looking for /usr/lib/vmware/config and few other files in ~/.vmware and since it finds none; IMHO it fails and that's the true underlying case.
Anyone else have ideas?
Thanks