VirtualCenter Services Not Starting After Reboot?

[adminatater]

The following two services are not starting on my Windows 2008 x64 server:

• VMware VirtaulCenter Management Webservices

• VMware VirtaulCenter Server

What I find odd is the other VMware services are:

• VMware vCenter Converter Integrated Server

• VMware vCenter Converter Integrated Worker

• VMware vCenter Update Manager Service

I have struct out trying to figure out this problem on my own. Any help you guys can provide would be greatly appreciated.

FYI: I'm connecting to a DB that is not located on this server.

[Troy_Clavell]

any error messages in the event logs? DB is local or remote? You have IIS installed?

[a_p_]

Is vCenter Server installed as a VM or on a physical server?

If physical, check the switch ports for spanning tree.

Are you able to start the services manually after some time?

André

[mittim12 · Accepted solution]

I would definitley check the logs first. They can be found at c:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs . Also might want to look at the last thing to change. Any services using a service account where a password might have changed? Any SSL certificate changes?

If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

[adminatater]

Any error messages in the event logs?

Sorry forgot to post that, when I try to manually start VMware VirtaulCenter Management Webservices I get this in Event Viewer:

Event ID: 1000

Source: VMware VirtaulCenter Server

EventData: Error getting configuration info from the database

DB is local or remote?

-Remote

You have IIS installed?

-No

Is vCenter Server installed as a VM or on a physical server?

-Physical Server

If physical, check the switch ports for spanning tree.

-I'm curious, why?

[Troy_Clavell]

web services are dependent on vCenter Service, so the vCenter Service needs to be started first. However, you are 100% sure there are no port 80 conflicts?

Also, check this registry setting, it should contain your ODBC information

HKLM\SOFTWARE\Wow6432Node\VMware, Inc\VMware VirtualCenter\DB\

if 32bit you won't see the Wow6432Node key

[a_p_]

If physical, check the switch ports for spanning tree.

-I'm curious, why?

With spanning tree enabled it can take up to ~45 sec. until the server has access to the network. Services which need network connection could have issues and timeout.

Set spanning tree to portfast for the server.

André

[adminatater]

Found the problem! It was an expired account used to access the remote DB. I found that out after looking through the vpxd-profiler log under C:\Users\All Users\VMware\VMware VirtualCenter\Logs.

Thanks for all the feedback guys, it really helped to jump start my brain.