The VMware VirtualCenter Server service terminated with service-specific error 2 (0x2)

When trying to connect to vCenter through the vSphere Client, the connection attempt failed with error

vShere Client Error

 After investigations, it was discovered that the vCenter service stopped for no reasonable reason. Revising the VC server’s System Event Log, the next error was logged:

The VMware VirtualCenter Server service terminated with service-specific error 2 (0x2).

Event Log

Cause: You are trying to start the VC service before SQL Service starts.  The VC Service should automatically try to restart on its own after 5 minutes after starting the SQL Service.

Resolution: To avoid this and to ensure when trying to start the VC service that the SQL service will start automatically, follow these steps to configure services’ dependencies:

  1. Obtain the service name for your SQL Service – in Registry Editor, browse to HKLM\System\CurrentControlSet\Services and look for entries starting with MSSQL.  In all likelyhood, yours will be called either MSSQL or MSSQL$SQLEXPRESS (ignore MSSQLServerADHelper).
  2. Now browse to HKLM\System\CurrentControlSet\Services\vpxd
  3. Open the REG_MULTI_SZ value called DependOnService
  4. Add a line called MSSQL$SQLEXPRESS (or whatever value you determined above)
  5. Ensure that the last line in the value is blank

, , ,


What is hostd?

hostd is an app that runs in the Service Console that is responsible for managing most of the operations on the ESX machine.  It knows about all the VMs that are registered on that host, the luns/vmfs volumes visible by the host, what the VMs are doing, etc.  Most all commands or operations come down from VC through it.  ie, powering on a VM, VM vMotion, VM creation, etc.

vpxa also runs on the Service Console and talks to VC.  I believe it acts as an intermediary between VC and hostd. I think it also does some housekeeping on the ESX host, but not as much as hostd.


Leave a comment

A general system error occurred: internal error: vmodl.fault.HostCommunication

 The below error commonly occurs when you try to add or connect an ESX 4.1 host to a vCenter 4

A general system error occurred: internal error: vmodl.fault.HostCommunication

The initial connection will work and the vCenter will start to deploy its agent on the ESX, but afterwards you’ll get this error. In my case the ESX host was trying to  connect to an old retired vCenter 4 which was started by mistake.


Right click on the faulty host and hit connect while connected to the vCenter 4.1 through the VMware vSphere Client.


Leave a comment

Perf Charts service experienced an internal error

I got that error after upgrading my VMware Cluster from vSphere 4 update 2 to vSphere 4.1. Also, I had to migrate my vCenter 4 update 2 (on 32-bit Windows 2003 with MSSQL 2005 installed locally) to vCenter 4.1 (on 64-bit Windows 2008 R2 with a remote MSSQL 2008 R2 Cluster) as vCenter must be install on 64-bit OS.

Anyways, after the upgrade everything went fine escept for some issues like this error:


This error may occure because you are using a custom SQL server database with a custom Java Database Connectivity (JDBC) SQL port

Here are the steps to fix it:

  1. On the vCenter Server system, navigate to: C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter
  2. Open the file.
  3. Comment out the string usevcdb = true.
  4. Ensure that the values for url, driver, and dbtype are as follows or add them (after the “usevcdb = true” line) if they don’t exist:
                      url = jdbc:sqlserver://<hostname>:<port>;integratedSecurity=true
                      driver =
                      dbtype = mssql
  5. Restart the VMware VirtualCenter Management WebServices service.

, ,


Troubleshooting a failed virtual machine conversion task

Conversions sometimes fail no matter how careful you are preparing the server. The failure can occur at various stages in the conversion process; these stages are based on the task bar percent and are estimated values.

  1. Creation of the target virtual machine (VM) (0%-5%)
  2. Preparing to Clone the Disk (5%-6%)
  3. Cloning (6%-95%)
  4. Post-cloning (95%-97%)
  5. Customization/Reconfiguration (97%-99%)
  6. Install Tools/Power On (99%-100%)

Converter creates a detailed log file during the conversion process which will contain exact errors pertaining to why the conversion failed. This log file is located on the server you are converting that is running the Converter agent, and is usually named vmware-converter-0.log and is located in the C:\Windows\temp\vmware-temp directory.

, ,

Leave a comment