最近Windows2003 server + VI4 update1 环境突然工作不正常， VC4开机后无法连接，经检查是VC的计算机出现故障。由于VC server 启动依赖SQL 2005，而本机的SQL 服务貌似启动较慢，查实VMware解决方法如下：
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.
This
issue may occur if the VirtualCenter Server service starts before one
of the services it depends on. The VirtualCenter Server service is
dependent on the following services:
- SQL Services
- ADAM Services (when using linked mode in vCenter Server 4.0)
To
resolve this issue, add a dependency to the VirtualCenter service so
that it only starts after the necessary services have started.
Note :
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.
To create a service dependency:
-
Click Start > Run.
-
Type services.msc and press Enter.
-
Locate any services that VirtualCenter requires. For example, SQLEXP_VIM or ADAM_VCMSDS.
-
Open the service properties and note the Service Name. For example, MSSQL$SQLEXP_VIM .
-
In the Run dialog, type Regedit.exe and press Enter. Browse 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 Regedit.
- Go back to the Services window and open the service properties for the service identified in step 3.
- On the Dependencies tab, verify the VMware VirtualCenter service is listed as depending on the service.
- Repeat steps 3 to 9 for any services that VirtualCenter requires.