Is this a fresh install? Usually when you can not start the Virtual Cneter Service it is because of database communications - what type of datavase are you using? The error indicates it can not connect to your SQL Express database - without the VC Service running you will not be able to connect to VC
What is your ODBC entry pointing to? Maybe it's pointing to the wrong DB.
It needs to be setup using the 2005 Native driver if you have SQL2005.
nd to add to Mike the ODBC connector needs to be a system DSN -
Yes, I am using SQL 2005 running in other Windows 2003 server. It isn't a new installation.
From your error message, your connection is failing to the db. As the others have stated, verify your DSN is pointing to the correct db. It could be that your password for the user you are using to connect with has expired. Verify the user you are using from virtual center can log in using sql management studio. If a password needs to be updated, do that. Then, to update the vc password, log on to the vc windows server, open a dos prompt. Cd to the virtual center install folder, and run vpxd -p. This will allow you to update the password for virtual center. The, try restart the service. If the service does not start. Go back to the dos window, and type vpxd -s. This will load vc in command line console mode and should show you any error it encounters. Post that here.
I had the same issue with VC service failing to start. The ODBC / DSN connection worked fine. The error in the Windows Event log was pretty vague:
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 most-recent vpxd-log file had the same errors with missing table vpx_dual in it:
2008-07-08 08:36:05.089 'App' 3332 errorVdb::LockRepositoryHelper Missing table vpx_dual 2008-07-08 08:36:05.089 'App' 3332 errorFailed to intialize VMware VirtualCenter.
2008-07-08 08:36:05.089 'App' 3332 infoForcing shutdown of VMware VirtualCenter now
The table did exist in the SQL Server database. Changing the password w/ vpxd -p still wouldn't let the service start. We opened a SR w/ VMware and ended up having to do a repair install of Virtual Center.
Previously he was running VC 2.5.0 build-64192 and we were able to go to the later release and just told it to use the existing database during the repair install. Everything came up fine after that.
I just had this problem. It was an issue with the SQL Express database. The System ODBC System DSN for VMware VirtualCenter had the default database pointing to master. Changed to VIM_VCDB and was able to start the VIrtualCenter service.
I had the same issue:
Vdb::LockRepositoryHelper Missing table vpx_dual
Out scenario was such:
- I have upgraded VC 2.5 U1 to VC 2.5U3, the database was on SQL Server 2000
- we have migrated the VCDB to SQL Server 2005 SP2
- the DSN was properly reconfigured
- VC said it couldn't be started because of the missing vpx_dual
The cause might be: the VC 2.5 U3 db upgrade scriptwhich behaves differently on SQL 2000 and 2005
We ended up with Repair-ing the installation, which reinitialized the database (it was cleared).
We had the same problem: after migrating to SQL2005, the service didnt
come up; after repair inst. (it did NOT ask whether to re-initialize DB
during repair inst!), the DB was empty.
Finally found it: the sql user's default schema has to be the same as
it was in sql2000 OR the schema of the imported DB has to be changed to reflect the new user's schema. Check the DB Table, the string before the first dot
is the schema the user has to use accessing the DB.
hope that helps...