vCenter Converter fails to import machine at 1%

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:va

• You are attempting to import a physical machine into your virtual infrastructure using the vCenter Converter Plugin or vCenter Converter Standalone
• The conversion fails at 1% with the message
  
  An error occurred
   
• The converter server logs show the following errors:
  
  Unexpected exception: converter.fault.clonefault
  (converter.fault.CloneFault) {
  dynamicType = <unset>,
  faultCause = (vmodl.MethodFault) null,
  description = "Unknown exception",
  msg = "",
   
• The converter agent log from the source machine (may be found under the "bundles" directory in the Converter logs directory on the vCenter Server) shows the error:
  
  [#12] [01540 warning 'App'] [,0] [NFC ERROR] NfcNewAuthdConnectionEx: Failed to connect to peer. Error: Host address lookup for server <hostname> failed: No such host is known
  
  where <hostname> is the name of an ESX/ESXi host.
  
  Note: The converter agent log is located in C:\Application Data\VMware\VMware Converter Enterprise\Logs\vmware-converter-agent.log.

Environment

VMware vCenter Converter Standalone 5.0.x
VMware vCenter Converter Standalone 4.3.x
VMware vCenter Converter 4.2.x

Cause

This issue occurs if the source machine being converted is unable to resolve the hostname of the ESX/ESXi host, as can happen if you do not use a DNS server configured for the source machine.

Resolution

To resolve this issue, add the IP address and hostname in the hosts file.

Notes:

• If the source machine is Linux , the hosts files is located in: /etc/hosts
• If the source machine is Windows, the hosts file is located in: \windows\system32\drivers\etc\hosts

Example: A hosts file might look similar to:

127.0.0.1 localhost.localdomain localhost
10.16.23.89 target-esx

Additional Information

You may experience similar symptoms if port 902 is blocked by a firewall.

Required VMware vCenter Converter ports
vCenter Converter でマシンのインポートが 1% で失敗する