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

Skip to main content

My Subscriptions

Loading

Knowledge Base

VMware VirtualCenter Server service does not start automatically after reboot (1007669)

Last Updated: 9/3/2015Categories: TroubleshootingTotal Views: 172257Language:
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

VirtualCenter Server service does not start after reboot

VMware Infrastructure (VI) Client cannot connect to VirtualCenter

You are using Microsoft SQL Server or SQL Express

VirtualCenter Server service can be started manually with no problems

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

ODBC error: (08001) - [Microsoft][SQL Native Client]Named Pipes Provider: Could not open a connection to SQL Server [2].

Purpose

In some cases, a race condition can occur when the VirtualCenter Server service starts before the SQL database service it depends on is started.

This article provides steps to prevent the race condition from occurring.

Cause

This issue may occur if the VirtualCenter Server service starts before one of the services on which it is dependent. The VirtualCenter Server service is dependent on the following services:

SQL Services

ADAM Services (when using linked mode in vCenter Server 4.x)

Resolution

To resolve this issue, add a dependency to the VirtualCenter service so that it starts only after the necessary services have started.

This solution assumes that the database server and the SQL server reside on the same machine. If the SQL server is on a different physical machine, you must ensure that the SQL server is functioning before attempting to start the VirtualCenter service.

In addition this same procedure can be used on any service that experiences this issue such as vCenter Server Webservices.

Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.

To create a service dependency:

Click Start > Run, type services.msc and press Enter.

Locate any services that vCenter Server requires. For example, SQLEXP_VIM, ADAM_VCMSDS, or ADAM_VMwareVCMSDS.

Note: Service names are different in SQL Express and full SQL implementations. For example, the service name in SQL Express is SQLEXP_VIM and in full SQL implementations, it is MSSQLSERVER.

Open the service properties and note the service name. For example, MSSQL$SQLEXP_VIM.

Click Start > Run, type regedit, and click OK. The Registry Editor window opens.

Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd.

Double-click the DependOnService key and add the Service name using the name identified in Step 4.

Close the Registry Editor window.

In the Services window, open the service properties for the service identified in Step 3.

In the Dependencies tab, ensure that the VMware VirtualCenter service is listed as depending on the service.

Repeat Steps 3 to 9 for any services that VirtualCenter requires.

If you are running Windows 2008 you can set the VMware VirtualCenter Server service to startup type Automatic (Delay) as follows:

Click Start > Run, type services.msc, and click OK.

Right-click on the VMware VirtualCenter Server service and click Properties.

Change the startup type from Automatic to Automatic (Delay).

Notes:

For more information on the DependOnService key, see the Microsoft article 193888.

If the VMware SSL Certificate Automation Tool is being used, changing the service dependencies may impact the tool. The VMware SSL Certificate Automation Tool needs to be able to start and stop specific services.

Check and modify the startup type every time after a vCenter Server upgrade is carried out, as the startup may get reset to the default startup type of Automatic.

Note: The preceding links were correct as of April 25, 2011. If you find a link is broken, provide a feedback and a VMware employee will update the link.

Related Information

There are differences in the way SQL 2005 and SQL 2008 handle the startup and the database readiness. SQL 2005 gives the database access immediately after the start up free for access (the method is FastRecovery), whereas SQL 2008 refuses to take connections until it finished with the Checking the databases, which can take up to 1 Minute.

For more information about Recovery Performance in SQL Server, see the Microsoft article http://msdn.microsoft.com/en-us/library/ms189262%28SQL.100%29.aspx.

Note: The preceding link was correct as of April 25, 2011. If you find the link is broken, provide feedback and a VMware employee will update the link.

再起動後に VMware vCenter Server サービスが自動的に開始されない
VMware VirtualCenter Server 服务在重新引导之后不会自动启动

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)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant