解决:VMware VirtualCenter服务开机不能自动启动方法
转自:http://symcafee.blog.163.com/blog/static/37662047201057115744349/
最近Windows2003 server + VI4 update1 环境突然工作不正常, VC4开机后无法连接,经检查是VC的计算机出现故障。由于VC server 启动依赖SQL 2005,而本机的SQL 服务貌似启动较慢,查实VMware解决方法如下:
VMware 官方原文:http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007669
照着下面提示将SQLserver与VCserver 建立依赖关系,验证成功。
VMware VirtualCenter service does not start automatically after reboot
Symptoms
-
VirtualCenter 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
Purpose
Resolution
- SQL Services
- ADAM Services (when using linked mode in vCenter Server 4.0)
-
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.
PS:此文章为转帖。此方法适用于3.5或4.0的vCenter Server服务无法自动问题。
1. 此问题主要原因是数据库相关服务启动较慢,导致VC Server服务无法启动
2. 解决就是建立相关服务依赖,通过注册表建立,注意数据库服务名字别写错了,要看数据库服务属性里的“服务名称”。