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

Firstboot Failed during Install, Deployment, Upgrade, or Migration in vCenter Server and vCenter Server Appliance 6.7 (55746)

Last Updated: 2/4/2021Categories: TroubleshootingTotal Views: 49736Language:
Chinese (Simplified)English

29 like this article

Subscribe to get an email
newsletter with new updates

29 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

Firstboot fails during Install/Deployment, Upgrade or Migration.

In the firstbootStatus.json file, you see that one of these services failed to configure or start during firstboot:

"failedSteps": "cmfirstboot"

"failedSteps": "analytics_firstboot"

"failedSteps": "vpxd_firstboot"

"failedSteps": "pschealth-firstboot”

"failedSteps": "sms_spbm_firstboot"

"failedSteps": "vmafd-firstboot"

"failedSteps": "vapi_firstboot"

"failedSteps": "mgmt-firstboot"

"failedSteps": "scafirstboot"

"failedSteps": "updatemgr-firstboot"

"failedSteps": "ngc_firstboot"

"failedSteps": "vmidentity-firstboot"

Cause

The vCenter Server firstboot framework was introduced in vSphere 6.0 and is responsible for configuring services after a vCenter Server install, upgrade, or migration. The firstboot framework is common to both vCenter Server on Windows and the vCenter Server Appliance. The firstboot process occurs during stage 2 of a vCenter Server Appliance deployment. If a single service fails to configure or start during the firstboot process, vCenter Server will fail to install, upgrade, or migrate.

This issue may occur due to these issues:

Time Synchronization Issues

Time inconsistencies in vSphere can cause firstboot to fail at different services depending on where time is not accurate and when the time is synchronized. Issues most commonly happen when the target ESXi host for the destination vCenter Server Appliance is not synchronized with NTP. Issue can also happen if the destination vCenter Server Appliance migrates to an ESXi host with different time due to fully automated DRS.

DNS Issues

Incorrect or missing DNS configurations will cause services in firstboot to fail.

Authentication/Password or Permissions Issues

Certain passwords may cause vSphere upgrade failures, as can unexpected permissions in the vCenter database.

Certificate Issues

Some certificate configurations may cause issues due to certificate standards, key requirements, etc.

Resolution

To resolve this issue:

Issue

Resolution

Time Synchronization Issues

Firstboot fails when upgrading vCenter Server Appliance 6.7 due to time synchronization issue (57085)

DNS Issues

Firstboot fails when upgrading vCenter Server Appliance 6.7 with no DNS records (57126)

Authentication/Password or Permissions Issues

Firstboot fails due to Authentication/Password or Permissions when installing or upgrading or migrating in vCenter Server and vCenter Server Appliance 6.7 (55891)

Certificate Issues

The SSL certificate of STS service cannot be verified', 'KeyUsage does not allow key encipherment' error during vCenter Server Appliance 6.7 Upgrade (56352)

Analytics Service registration with Component Manager failed''SSL CERTIFICATE_VERIFY_FAILED' while upgrading vCenter server from 6.x to 6.7 firstboot fails (67198)

Other Issues

vCenter Server Appliance 6.7 Migration Fails During Firstboot - vCenter Authentication Proxy Firstboot Failed - "Exception: Could not register as vCenter extension" (55864)

vCenter Server 6.7 on Windows Upgrade Fails During Firstboot - VMware HTTP Reverse Proxy Firstboot Failed - "Failed to register VMware HTTP Reverse Proxy service with SCA" (56490)

vCenter Server 6.7 Upgrade Fails During Firstboot - VMware Service Control Agent Firstboot Failed - "Entry with name serviceId: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx not found" (58534)

Upgrade of Windows vCenter Server 6.5 to 6.7 fails with the error "Failed to register Auto Deploy" (55076)

vCenter Server 6.7 upgrade fails with the error: "Failed to check the status of VMware Directory Service" (54724)

Windows vCenter Server upgrade from 6.5 to 6.7 fails if RSA is configured, with VMIdentity firstboot error "VMware Identity Service bootstrap failed" (55627)

Detect and update duplicate names of Distributed Virtual Switches and Distributed Virtual Portgroups before upgrading vCenter Server (2147547)

vCenter Server 6.x Installation on Windows fails with Error: "Failed to generate VirtualCenter symmetric encryption key" (55781)

If this article didn’t solve your issue:

Ask for help here : Click for VMware Communities

Related Information

It is also possible to determine which error message was sent to the UI from the /var/log/firstboot/fbInstall.json file.

For example:
In the /var/log/firstboot/fbInstall.json file, you see entries:

"problemId": null, --> This will show up as the "Error" in the UI
"detail": [
{
"translatable": "The installation of vCenter Server failed due to an internal error.",
"resolution": { --> This will show up as the "Resolution" in the UI
"translatable": "This is an unrecoverable error, please retry install. If you encounter this error again, please search for these symptoms in the VMware Knowledge Base for any known issues and possible resolutions. If none can be found, collect a support bundle and open a support request.",

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server Appliance 6.0.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant