Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

"Failed to run boot script" error after upgrading from vCenter Server 6.5 to 6.7 (57703)

Last Updated: 7/25/2019Categories: TroubleshootingTotal Views: 8133Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Upgrading from vCenter Server 6.5 to 6.7 fails with the error:

"Failed to run boot script"

In the vminst.log file, you see entries similar to:

2018-07-31 12:42:06.592-05:00| vcsInstUtil-8546234| I: LaunchProcAndMonitorStatus: Launching "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-firstboot-scripts.bat" >> C:\Users\admin\AppData\Local\Temp\vminst-con.log 2>&1"" in "C:\Windows\system32\"
2018-07-31 12:42:06.592-05:00| vcsInstUtil-8546234| I: LaunchProcAndMonitorStatus: Launched process with pid 15744 tid 18212
2018-07-31 12:42:06.592-05:00| vcsInstUtil-8546234| I: Entering function: MonitorStatusFile
2018-07-31 12:42:06.592-05:00| vcsInstUtil-8546234| I: MonitorStatusFile: Status file directory is "C:\ProgramData\VMware\vCenterServer\logs\firstboot\"
2018-07-31 12:42:06.592-05:00| vcsInstUtil-8546234| I: MonitorStatusFile: Monitoring directory "C:\ProgramData\VMware\vCenterServer\logs\firstboot\" for file "fbInstall.json"
2018-07-31 12:42:06.592-05:00| vcsInstUtil-8546234| I: MonitorStatusFile: Started execution of process
2018-07-31 12:42:18.062-05:00| vcsInstUtil-8546234| I: MonitorStatusFile: Other process terminated with 1, exiting
2018-07-31 12:42:18.062-05:00| vcsInstUtil-8546234| I: MonitorStatusFile: Calling status parser one last time
.
2018-07-31 12:42:18.062-05:00| vcsInstUtil-8546234| E: LaunchProcAndMonitorStatus: Failure detected while monitoring status file
.
2018-07-31 12:42:18.062-05:00| vcsInstUtil-8546234| E: RunFirstLastUpdateboot: Failed to run boot script: "C:\Windows\system32\cmd.exe /S /C ""C:\Program Files\VMware\vCenter Server\bin\run-firstboot-scripts.bat" >> C:\Users\admin\AppData\Local\Temp\vminst-con.log 2>&1""

In the vminst-con.log file, you see entries similar to:

[Error 3] The system cannot find the path specified: 'c:\\programdata\\vmware\\vcenterserver\\runtime\\vsphere-client\\server\\workspace\\logbrowser\\.vmwb\\logbrowser\\cache\\0x1.7463f05c93a64p-1\\509820290d57f333403f490dde7316f4\\vc-vcenter-2017-03-23--13.08-15016\\programdata\\vmware\\vcenterserver\\logs\\vsphere-client\\logs/*.*'
.
2018-07-31T17:42:08.311Z  Running command: ['C:\\Windows\\system32\\icacls.exe', 'C:\\ProgramData\\VMware\\vCenterServer', '/grant:r', '*S-1-5-18:(OI)(CI)(F)', '/grant:r', '*S-1-5-32-544:(OI)(CI)(F)', '/inheritance:r', '/L', '/Q']
2018-07-31T17:42:09.702Z  Done running command
2018-07-31T17:42:09.702Z  Running command: ['C:\\Windows\\system32\\icacls.exe', 'C:\\ProgramData\\VMware\\vCenterServer\\*', '/reset', '/T', '/L', '/Q']
2018-07-31T17:42:18.031Z  Done running command
2018-07-31T17:42:18.031Z  Invoked command: ['C:\\Windows\\system32\\icacls.exe', 'C:\\ProgramData\\VMware\\vCenterServer\\*', '/reset', '/T', '/L', '/Q']
2018-07-31T17:42:18.031Z  RC = 3
Stdout = Successfully processed 11682 files; Failed processing 1 files^M
.
.
Stderr = C:\ProgramData\VMware\vCenterServer\runtime\vsphere-client\server\workspace\logbrowser\.vmwb\LogBrowser\cache\0x1.7463f05c93a64p-1\509820290d57f333403f490dde7316f4\vc-vCenter-2017-03-23--13.08-15016\ProgramData\VMware\vCenterServer\logs\vsphere-client\logs\vsphere_client_virgo.log: The system cannot find the path specified.^M
.
Error Code: 1021
2018-07-31T17:42:35.207Z  Running command: ['C:\\Program Files\\VMware\\vCenter Server\\bin\\run-firstboot-scripts.bat', '--action', 'firstboot', '--subaction', 'uninstall', '--logDirectory', 'C:\\ProgramData\\VMware\\vCenterServer\\logs\\uninstall']

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs when upgrade script tries to reset permission using icacls and fails due to the long file path (more than MAXLIMIT 260 letters).

Resolution

To resolve this issue:

It is a best practice to take a snapshot of vCenter Server before performing below steps.

Move all contents of long file path to a temp location.

Note: Upgrade script must remove these files during uninstall phase, if these file are not removed upgrade fails.

For example, move all log-browser cache files from C:\ProgramData\VMware\vCenterServer\runtime\vsphere-client\server\workspace\logbrowser\.vmwb\LogBrowser\cache\ folder to a temp location.

Stop vsphere-client service.

Open the cmd and run the icacls C:\ProgramData\VMware\vCenterServer\runtime\vsphere-client /reset /T /L /Q and ensure it completes without failures.

Note: Run the icacls command as per the file path found in the vminst-con.log.

Start vsphere-client service and upgrade process again.

For more information on starting services, see Search How to stop, start, or restart vCenter Server 6.x services (2109881).

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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:

Related Versions:

Take Our Survey

Support Assistant