Could not start the vmware virtualcenter server service on local computer. Error 1053: The service did not respond to the start or control request in a timely fashion.

[AndyGK]

Good afternoon.

We've seemed to develop a problem with one of our servers running Virtual Center that prevents us from logging in with VSphere.

Windows gives the following error:

Windows could not start the vmware virtualcenter server service on local computer. Error 1053: The service did not respond to the start or control request in a timely fashion.

I checked our app log for errors, and this is what I found:

ODBC error: (08001) - [SQL Native Client]TCP Provider: Timeout error .

Error getting configuration info from the database

• Init failed: VpxdVdb::Init(Vdb::GetInstance(), false, false)*

• Failed to intialize VMware VirtualCenter. Shutting down...*

Forcing shutdown of VMware VirtualCenter now

Any idea what might be causing our issue?

I saw a discussion from last year about this where the user was asked to post his error log, but he never did. So I thought I'd give it a shot.

Thanks!

[a_p_]

Does this happen only after a reboot?

Can you start the vCenter service manually?

Please read http://kb.vmware.com/kb/1007669

If this does not help, please describe your setup. Local or remote SQL server, OS 32 or 64 bit, vCenter version, is this a new setup, ...

André

[AndyGK]

The service will not start up if I attempt to do it manually.

SQL server is 2005, and run locally.

OS is Windows 2003 R2, 64 bit, SP2

vCenter version is 4.0.0.10021

It's been working fine for us for several months, issue just started happening last week. Our other vCenter is working fine still.

[HughBorg707]

Also make sure you don't have other IIS services running (possibly inadvertently). If there is a port confilict it can keep vCenter Server from starting as well.

Hugh

http://www.1zero1.net

[AndyGK]

Sadly, no IIS services on the machine.

[Stevester]

Good Evening Everyone,

Has anyone resolved this issue? I am having the same problem?

Thanks

Stevester

[donanobispacem]

Do a netstat -anb and see what port sqlserver service is listening on.

Under normal circumstances, it should be 1433.

If it is different, someone has changed it somtime since the previous reboot or service restart, and the reboot revealed the issue now.

If so, use SQL Server Configuration Manager to change the port back to 1433, restart the service, and then attempt to start the vCenter services again.