Event Type: Error
Event Source: VMware VirtualCenter Server
Event Category: None
Event ID: 1000
Date: 1/24/2008
Time: 9:33:30 AM
User: N/A
Computer: VIRTUAL-CENTER
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....
Somebody help me?
Hiya,
You usually get that type of error when the VC server can't contact the VC database?
Is it on the same server?
If remote - is the DB server up?, can it be pinged?
Is the DB itself up, can you connect manually via the DSN?
Has anything changed?
Is this a new installation or after an upgrade?
Dinny
Yes, the VC is in the same server. I can't up the service VMware Virtual Center Server. It is not a new installation or upgrade.
Is the local DB definitely running?
Not out of space or anything?
No one amended o0r deleted the DSN?
What version of VC?
Check disk space and size of trans log if you are using full recovery model.
Check event viewer for SQL errors and then look in the VC logs for info.
Yes, the DB is running.
The version is VMware VirtualCenter 2.5.0
Is the local database the MSDE or is it an SQL Database?
If it's an SQL 2005 database, the Virtual Center Service Account must be the dbo of the Virtual Center database.
SQL database
If this is SQL 2005, the account you're running the Virtual Center service as must be the actual Databse Owner not just the db_Owner role. If it's 2000 it needs the db_Owner role.
If this is already true, verify the service pack levels required by your SQL version (including the Native Client for 2005).
Hello.
I have the same problem.. Did you find any solution?
Regards
Daniel
Not yet.
have a look at the vpxd logs and also windows event viewer might give you a clue.
here is a nice document for troubleshooting
I have the same issue. If I go in and start the service after the computer boots, it works. It only seems to be failing at startup. Any ideas?