Troubleshooting issues when vCenter Converter fails during conversion

Products

• VMware

Issue/Introduction

Symptoms:

• When using vCenter Converter, the conversion fails between 2% and 96%.
• The conversion process runs very slowly.
• Conversion takes a long time to complete or does not complete at all.
• You may 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
  • [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:

conversion-converter converter-windows-fails duplicate-ip-address converter-conversion-long converter-conversion-timesout converter-fails converter-fails-96% conversion-slow converter-conversion-slow converter-linux-fails ip-address-conflict dns-conflict

Environment

VMware vCenter Converter Standalone 4.0.x
VMware vCenter Converter 4.1.x
VMware vCenter Converter 4.2.x
VMware vCenter Converter Standalone 5.5.x
VMware vCenter Converter Standalone 5.0.x
VMware vCenter Converter 4.0.x
VMware Converter 3.0.x
VMware vCenter Converter Standalone 4.3.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 often fails when a networking failure happens while the data is being sent from the source to the destination or if a file or volume on the source is inaccessible.

1. Ensure that you do not have any locked files on your source server. This can often be the case when trying to convert a database or mail server. For more information, see Troubleshooting file, volume, and disk access problems during conversion with vCenter Converter (1006859).
2. Verify that you have the correct IP address or that your DNS name is registered on your DNS servers. Having incorrect IP addresses or DNS naming issues can often cause failures. For more information, see Verifying and troubleshooting networking connections that may cause vCenter Converter to fail (1006607)).
3. Ensure that you do not have any IP or DNS conflicts/duplicates, such as another workstation or device with the same IP address or registered DNS name. For more information, see Virtual machine network failure due to duplicate IP addresses (1009143).<?xml:namespace prefix = o />
4. 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 vCenter Converter failures (1004615).
5. 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 a network link (1003724), Verifying the integrity of the physical network adapter (1003686), and Testing network connectivity with the ping command (1003486).

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