Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vCenter Converter fails to import machine at 1% (1034292)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 58771Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Symptoms

If you fail to connect an ESXi host to vCenter Server with an error faultcause = (vmodl.methodfault) null see  Remediating an ESX host fails with the error: A general system error occurred: Invalid argument.

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.

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

Related Information

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

Required VMware vCenter Converter ports
vCenter Converter でマシンのインポートが 1% で失敗する
vCenter Converter 导入计算机进行到 1% 时失败

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Converter Standalone

VMware vCenter Converter

Related Versions:

VMware vCenter Converter Standalone 5.0.x

VMware vCenter Converter Standalone 4.3.x

VMware vCenter Converter 4.2.x

Take Our Survey

Support Assistant