I had this issue a couple of weeks ago. When the VirtualCenter server starts-up the service doesn’t start-up automatically. After a bit of troubleshooting and googling I found the below:

It would be incredibly annoying to have to manually start the VirtualCenter service each time your server boots. Luckily there is an easy fix — make the VirtualCenter service depend on the Microsoft SQL service.

In short find the registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd and edit the DependsOnService property. Add two entries to this REG_SZ_MULTI value:

MSSQL$SQLEXP_VIM

Save the changes. Now the next time the server boots the VirtualCenter service will not attempt to start until the Microsoft SQL service and SQL Server Agent service come online, sparing you of those annoying errors in the event log and having to restart the service manually.

After making the above changes I rebooted the server and once it was up I tried to connect to the VC using the VIC but it still didn’t want to connect. After checking the services I saw that the VC service didn’t start-up again. I checked the event logs and found the below error getting logged:

Log Name: System
Source: Service Control Manager Eventlog Provider
Event ID: 7024
Message: The VMware VirtualCenter Server service terminated with service-specific error 2 (0x2)

After some investigation I found out that you need to disable IIS on the VC server as it conflicts with Apache (They both try to run on Port 80). After disabling the IIS service under services.msc (World Wide Web Publishing Service) I rebooted the server again and this time the VirtualCenter Server service started automatically.

Hope that helps some of you find the solution quicker.

Advertisements