I have search the site for similar issue but doesn't seem to resolve the issue I'm facing with.
I'm running VC 2.0.1 on W2k3 SP2 connected to an Oracle database on another server. But I keep getting the following error even when I manually try to restart the service. Can someone please help me.
Event Type: Error
Event Source: VMware VirtualCenter Server
Event Category: None
Event ID: 1000
Date: 2/28/2008
Time:
User:
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....
The service started and then stopped?
Looking on the Oracle log we can see the oracle user account connecting to the database then disconnecting when the service fails?
I've tried a repair of the Virtual Centre installation.
Thanks Matt
To add the vpxd.log states the following:
Log for VMware VirtualCenter, pid=4400, version=2.0.1, build=build-32042, option=Release, section=2
Current working directory: C:\WINDOWS\system32
Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
NFC connection accept timeout: 180000 milliseconds
NFC request timeout: 180000 milliseconds
NFC read timeout: 60000 milliseconds
NFC write timeout: 600000 milliseconds
Starting VMware VirtualCenter 2.0.1 build-32042
Enabled low-frag process heap.
Locale subsystem initialized from C:\Program Files\VMware\VMware VirtualCenter 2.0\locale/ with default locale en.
Ignoring unknown entry from DB: task.interval
Found host with invalid parent. Removed </vpx/host/#26/>
VmdbCtxGet: Failed to get /vpx/host/#26/_private/managedObjImpl/ (Null cross reference)
Failed to initialize: vmodl.fault.ManagedObjectNotFound
Failed to intialize VMware VirtualCenter. Shutting down...
and another log
Log for VMware VirtualCenter, pid=1740, version=2.0.1, build=build-32042, option=Release, section=2
Current working directory: C:\WINDOWS\system32
Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000
NFC connection accept timeout: 180000 milliseconds
NFC request timeout: 180000 milliseconds
NFC read timeout: 60000 milliseconds
NFC write timeout: 600000 milliseconds
Starting VMware VirtualCenter 2.0.1 build-32042
Enabled low-frag process heap.
Locale subsystem initialized from C:\Program Files\VMware\VMware VirtualCenter 2.0\locale/ with default locale en.
Ignoring unknown entry from DB: task.interval
Found host with invalid parent. Removed </vpx/host/#26/>
VmdbCtxGet: Failed to get /vpx/host/#26/_private/managedObjImpl/ (Null cross reference)
Failed to initialize: vmodl.fault.ManagedObjectNotFound
Failed to intialize VMware VirtualCenter. Shutting down...
have you verified the status of the virtual centre database, is it available?
Looks like something went wrong with the data in the database itself... I would recover to a known good backup (of the database) if one is available and start VC up again.
VC 2.0.1 had a couple of nasty issues, mostly related to database performance (not aware of any data corruption issues per se.) Once you get things backup and running again, I'd suggest you upgrade to VC 2.0.2 Update 2. (Note: do NOT perform the upgrade until your 2.0.1 installation is back up and running properly again.)
Thanks for the replies. Just to give you an update. I've run a virtual centre repair and reset the database and the service started up without any problems so it does look like a database problem. I've just asked one of our Oracle DBA's to run a database restore from a last known good backup.
Hi,
Just an update. Our DBA's didn't have a successful Oracle database backup so I've reinstalled virtual centre creating a new blank database, upgraded to 2.0.2 update 3 and rebuilt new HA clusters. Quite a bit of work but everything is up and running again.
Marked as answered because the new blank database has solved the issue.