The VMware VirtualCenter Server service terminated unexpectedly

After rebooting the VMware VirtualCenter (VC) server, i was unable to logon using the VI-client in VC. In the Windows event log the following  Error is listed:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date:  25-9-2008
Time:  13:39:58
User:  N/A
Computer: VC1
The VMware VirtualCenter Server service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 300000 milliseconds: Restart the service.

For more information, see Help and Support Center at

It seems that the VC server service is started before the SQL 2005 service is started. The solution is the delay the VirtualCenter service from starting till the Microsoft SQL 2005 service is started. Microsoft has a KB article “How to delay loading of specific services”.

I did the following:

Open the regedit.exe and browse to the HKLM\SYSTEM\CurrentControlSet\Services\MSSQLSERVER (for MS SQL 2005 standard). So you know the name of the service.


Browse to HKLM\SYSTEM\CurrentControlSet\Services\vpxd and open the DependOnService property


Add the name MSSQLSERVER to this multi-string. Ensure that the last line is empty.


Close the Registry Editor and restart the VirtualCenter server and test if it VMware VirtualCenter service starts.


Enable SSH for VMware ESX 3i

There is a hack to enable SSH for VMware ESX 3i. After reading the VMTN forum. Here is the procedure to enable SSH

– Boot ESXi  and wait till the till"loaded

– Press ALT-F1, you see the console screen

– Type unsupported and press ENTER

– Enter the root password

– Enter the following command vi /etc/inetd.conf

– Search for the #SSH row

– Remove the # from the SSH row

– Save the config by entering :wq!

– Type ps | grep inetd on the console

– Send a hangup signal by using the following command kill -s HUP <PID>

Open now your favorite SSH client (for example Putty) and SSH to the VMware 3i server.