Troubleshooting issues using VMware Converter when the conversion process is slow

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Converting a physical or virtual machine takes longer than expected.
• The process of conversion is very slow, even though it appears that the source system is not busy.
• You receive one or more of these errors:

  • Image processing task has failed with MethodFault::Exception: sysimage.fault.DiskLibConnectionFault
  • Image processing task has failed with MethodFault::Exception: sysimage.fault.NfcConnectionFault
  • Image processing task has failed with PlatformError fault: 5666
  • Image processing task has failed with PlatformError fault: 79394
  • Image processing task has failed with PlatformError fault: 4898
  • [NFC ERROR] NfcNetTcpRead: timed out waiting for data
    [NFC ERROR] NfcFssrvrRecv: failed with code = 9
    [NFC ERROR] NfcFssrvr_DiskIo: failed to receive io reply
    DISKLIB-LIB : RWv failed ioId: #1 (5666) (34)
    NfcNetTcpWrite: timed out waiting for socket to be ready (101)
  • Error 5666 writing to the destination volume
  • [NFC ERROR] NfcNetTcpWrite: bWritten: -1 err: 10053
    [NFC ERROR] NfcFssrvrSend: failed
    [NFC ERROR] NfcFssrvr_Close: failed to send close message
    [NFC ERROR] NfcNetTcpWrite: bWritten: -1 err: 10053
  • Error 79394 writing to the destination volume
    DISKLIB-LIB : RWv failed ioId: #50301 (79394) (34)
    [NFC ERROR] NfcFssrvr_Close: received unexpected message 4 from server
  • NfcNetTcpRead: timed out waiting for data
    NfcNetTcpWrite: timed out waiting for socket to be ready (101)
    [NFC ERROR] NfcFileSendMessage: hdr send failed:
    [NFC ERROR] NfcFile_Send: Something is messed up
    [blockLevelCloningTaskImpl,831] File transfer failed.
    Dst error: Network error -- Failed to send header message:
  • Error E7D1001E: Unable to read from file. Error 00000040: The specified network name is no longer available.
    Failed to write out header: The specified network name is no longer available (4194313).
    File transfer failed.
    File error -- Failed to delete file: File not open

Environment

VMware vCenter Converter Standalone 4.0.x
VMware vCenter Converter 4.2.x
VMware vCenter Converter Standalone 5.0.x
VMware vCenter Converter Standalone 4.3.x
VMware vCenter Converter Standalone 5.5.x
VMware vCenter Converter 4.0.x
VMware vCenter Converter 4.1.x

Resolution

Validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Do not skip a step.

Converting a machine can be slow when certain environmental settings have not been checked or have failed. You can take certain steps to validate that your environment is performing as expected.

1. Verify that the speed and duplex settings are correct and consistent between the physical servers, operating systems, network cards, and virtual switches, and that the network switches are working properly. For more information, see Investigating network devices and device settings as a cause of VMware Converter failures (1004615).
   
   
2. Verify that you do not have defective hardware. Defective hardware (such as a defective cable or malfunctioning network switch) can cause issues during conversion. For more information, see Verifying network links (1003724), Verifying the integrity of the physical network adapter on an ESX/ESXi host (1003686), and Testing network connectivity with the ping command (1003486).
   
   
3. If the source server or target server is incurring high amounts of traffic or is resource intensive, performance and the time necessary to perform a conversion can be impacted. For more information, see Converting a physical or virtual machine with VMware Converter takes longer than expected (1038454).
   
   
4. If you are using a security firewall or Stateful Packet Inspecting (SPI) firewall, check firewall alerts and logs to make sure the connection is not being blocked as malicious traffic. Check that the appropriate firewall ports are opened and are not limited to certain bandwidth. For more information, see TCP and UDP Ports required to access vCenter Server, ESXi/ESX hosts, and other network components (1012382).
   

Note: If your issue still exists after trying the steps in this article, file a support request with VMware Support and note this KB Article ID (1038450) in the problem description. For more information, see How to Submit a Support Request.

Additional Information

Testing network connectivity with the ping command
Verifying the integrity of the physical network adapter on an ESX/ESXi host
Verifying network links
Investigating network devices and device settings as a cause of VMware Converter failures
TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components
Converting a physical or virtual machine with VMware Converter takes longer than expected