Hi,
To resolve this issue, add a dependency to the VirtualCenter service so that it starts only after the necessary services have started.
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).