I am having an issue with VC randomly shutting down and not restarting which requires me to manual start the service on the server. This happens ever time I reboot the server and randomly about once or twice a week if I have not rebooted the server. Below is the entries reported to the event log on the server.
Event Type: Error
Event Source: VMware VirtualCenter Server
Event Category: None
Event ID: 1000
Date: 5/18/2007
Time: 11:24:05 AM
User: N/A
Computer:
Description:
The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Failed to intialize VMware VirtualCenter. Shutting down....
Event Type: Information
Event Source: Application Error
Event Category: (100)
Event ID: 1004
Date: 5/18/2007
Time: 11:33:01 AM
User: N/A
Computer:
Description:
Reporting queued error: faulting application vpxd.exe, version 4.0.2.40644, faulting module kernel32.dll, version 5.2.3790.2756, fault address 0x00015e02.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 76 70 78 ure vpx
0018: 64 2e 65 78 65 20 34 2e d.exe 4.
0020: 30 2e 32 2e 34 30 36 34 0.2.4064
0028: 34 20 69 6e 20 6b 65 72 4 in ker
0030: 6e 65 6c 33 32 2e 64 6c nel32.dl
0038: 6c 20 35 2e 32 2e 33 37 l 5.2.37
0040: 39 30 2e 32 37 35 36 20 90.2756
0048: 61 74 20 6f 66 66 73 65 at offse
0050: 74 20 30 30 30 31 35 65 t 00015e
0058: 30 32 02
Event Type: Information
Event Source: VMware VirtualCenter Server
Event Category: None
Event ID: 1000
Date: 5/18/2007
Time: 11:33:27 AM
User: N/A
Computer:
Description:
The description for Event ID ( 1000 ) in Source ( VMware VirtualCenter Server ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Starting VMware VirtualCenter 2.0.1 build-40644.
Check the vpxd logs as they will likely give a better indication as to what's going on. Look for ODBC errors (indicating connectivity to database issues) or other errors that might indicate why.
This is almost always database related. If you are running Patch2 it supposedly has better support for lost database connectivity. You can also go into the properties for the Service and change the Recovery tab from Take No Action to Restart Service.
I had a similar problem prior to applying patch 2. The transacation log was filling up (known issue) and causing VC to shut down. It was working great then just stopped. Not sure what the trigger was. You may want to check the size of your tranaction log if you have not already applied patch 2. Just a thought.