VMware
 

Knowledge Base

Search the Knowledge Base:
Products:
Search In:
 

VMware VirtualCenter service does not start automatically after reboot

Symptoms

  • VirtualCenter service does not start after reboot
  • VMware Infrastructure Client cannot connect to VirtualCenter
  • You are using Microsoft SQL Server or SQL Express
  • VirtualCenter Server service can be started manually with no problems

Purpose

In some cases a race condition can occur and VirtualCenter starts before the SQL database it depends on.
 
This article provides steps to prevent the race condition from occurring.

Resolution

Adding a dependency to the VirtualCenter service so that it waits for SQL Express remedies this.
 
To create a service dependency:
  1. Click Start > Run.
  2. Type services.msc and press Enter.
  3. Locate the SQL instance for VirtualCenter. For example, SQL Server (SQLEXP_VIM).
  4. Open the SQL Express instance and note the Service Name. For example, MSSQL$SQLEXP_VIM .
  5. In the Run dialog, type Regedit.exe and press Enter. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd
  6. Double-click the DependOnService key and add the Service name using the name identified in step 4.
  7. Close Regedit.
  8. Go back to the Services Panel and open the SQL Server properties.
  9. On the Dependencies tab, verify the VMware VirtualCenter service is listed as depending on the SQL service instance.

Feedback

Rating: 1 - Lowest 2 3 4 5 - Highest (12 Ratings)   

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (2000 or fewer characters)
Submit
Rating: 1 - Lowest 2 3 4 5 - Highest (12 Ratings)   
Actions
  • KB Article: 1007669
  • Updated: Nov 12, 2009
  • Products:
    VMware VirtualCenter
  • Product Versions:
    VMware VirtualCenter 2.0.x
    VMware VirtualCenter 2.5.x
    VMware vCenter Server 4.0.x