Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

While migrating from a Windows vCenter Server to a 6.5 vCenter Appliance, one or more services fail to start. (55630)

Last Updated: 8/16/2018Categories: TroubleshootingTotal Views: 5128Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

While migrating from a Windows vCenter to a 6.5 vSphere Appliance one or more services fail to start during the second phase of the process.

Cause

This can occur when the Windows vCenter relies on host file entries to resolve the FQDN of multiple ESXi hosts rather than forward & reverse DNS records. The host file entries from the source vCenter are not imported until after the firstboot process has completed.

The VPXD process then tries to start during firstboot but as it is unable to resolve the FQDN of the ESXi hosts, the delay can cause the VPXD service to appear unresponsive to services which depend on it.

The resulting timeout or failure of the dependant services which cause the Phase 2 to be declared a failure.

Resolution

VMware is currently investigating a permanent solution for this issue.

Workaround

To workaround this issue perform one of the following steps.

Ensure all ESXi hosts which are going to be managed by the vCenter have a valid forward & reverse DNS record.

Test and confirm that all records are working by using nslookup.

OR.

After the initial Phase 1 has completed connected to the new vCenter Server Appliance and manually add the FQDN for the ESXi hosts to the /etc/hosts file.

Complete the Phase 2 process.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

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

KB
•
「エラー：vCenter Server の CA 証明書が検証されていません。停止しています (Error: vCenter CA certificate not verified. Stopping)」というメッセージが 5.5 から 6.x への vCenter Server 移行中に表示される (2148075)

KB
•
升级 vCenter Server 6.x 时出现错误“从源 vCenter Server 获取数据时出现问题 ” (56246)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant