Error Getting Configuration Info From The Database Vcenter 5.5
· February 19, 2014 I had to change user name and password for vCenter DB DSN entry. After change vCenter service fails to start. In a vCenter logs there was an entry pointing on problems with authentication to vCenter database because old user name and password was used for it, see part of the log below. Of course, like in 99,9 % of https://kb.vmware.com/kb/2015824 Windows application at least part of configuration is kept in Windows registry . 2014-02-19T10:59:06.957+01:00 [05260 info 'utilvpxdVdb'] Registry Item DB 5 value is '50' 2014-02-19T10:59:06.958+01:00 [05260 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: vCS-DB with username ap-vcs 2014-02-19T10:59:06.972+01:00 [05260 error 'utilvpxdVdb'] [VpxdVdb::SetDBType]: Login failure - retrying once... 2014-02-19T10:59:06.972+01:00 [05260 error http://vmwaremine.com/2014/02/19/vcenter-fails-to-start-after-dsn-changes/ 'utilvpxdVdb'] [VpxdVdb::SetDBType] Failed to connect to database: . Retry attempt: 1 ... 2014-02-19T10:59:08.900+01:00 [07364 warning 'VpxProfiler' opID=SWI-174b3a7b] VpxUtil_InvokeWithOpId [TotalTime] took 12000 ms 2014-02-19T10:59:08.900+01:00 [05676 info 'ThreadPool'] Thread enlisted 2014-02-19T10:59:16.972+01:00 [05260 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: vCS-DB with username ap-vcs 2014-02-19T10:59:16.985+01:00 [05260 error 'utilvpxdVdb'] [VpxdVdb::SetDBType] Encountered login error. Subsequent connection attempt failed: 28000 2014-02-19T10:59:16.985+01:00 [05260 error 'utilvpxdVdb'] [VpxdVdb::SetDBType] Aborting after 1 retries. 2014-02-19T10:59:16.985+01:00 [05260 error 'Default'] Error getting configuration info from the database 2014-02-19T10:59:16.985+01:00 [05260 warning 'vpxdvpxdMain'] Database not initialized. Nothing to unlock 2014-02-19T10:59:16.985+01:00 [05260 info 'Default'] Forcing shutdown of VMware VirtualCenter now 123456789101112 2014-02-19T10:59:06.957+01:00 [05260 info 'utilvpxdVdb'] Registry Item DB 5 value is '50'2014-02-19T10:59:06.958+01:00 [05260 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: vCS-DB with username ap-vcs2014-02-19T10:59:06.972+01:00 [05260 error 'utilvpxdVdb'] [VpxdVdb::SetDBType]: Login failure - retrying once...2014-02-19T10:59:06.972+01:00 [05260 error 'utilvpxdVdb'] [VpxdVdb::SetDBType] Failed to connect to database: .Retry attempt: 1 ...2014-02-19T10:59:08.900+01:00 [07364 warning 'VpxProfiler' opID=SWI-174b3a7b] VpxUtil_InvokeWithOpId [TotalTime] took 12000 ms2014-02-19T10:59:08.900+01
somehow the vCenter service lost its connection to the SQL Server 2005 Express database that we are using and it would not start. After some http://virtirl.com/?p=52 poking around, the vCenter log (C:\Documents and Settings\All Users\Application Data\VMware\VMware VirtualCenter\Logs\vpxd-*.log) https://cyruslab.net/2013/05/07/troubleshoot-vmware-virtualcenter-server-service-cannot-start-automatically-and-manually/ contained these telling lines: [2010-09-15 09:14:55.354 03728 info ‘App'] [Vpxd::ServerApp::Init:759] Calling: VpxdVdb::Init(Vdb::GetInstance(), false, false) [2010-09-15 09:14:55.354 03728 error ‘App'] ODBC error: (IM002) - [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified [2010-09-15 09:14:55.354 03728 error ‘App'] Error getting configuration info from the error getting database [2010-09-15 09:14:55.354 03728 error ‘App'] [Vpxd::ServerApp::Init] Init failed: VpxdVdb::Init(Vdb::GetInstance(), false, false) [2010-09-15 09:14:55.354 03728 error ‘App'] Failed to intialize VMware VirtualCenter. Shutting down… [2010-09-15 09:14:55.354 03728 info ‘App'] Forcing shutdown of VMware VirtualCenter now Poking around the VMware Knowledge Base, I found the article 1003928: Troubleshooting the database data source used by VirtualCenter Server which mentions the registry error getting configuration key "HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter\DB". The value for the key "1" was blank, meaning no DSN was specified. I changed the value to our System DSN "vcenter". Next I opened up odbcad32 to actually look at the "vcenter" System DSN but could not open it because the SQL Native Client 10.0 driver was missing! I downloaded it from the Microsoft SQL Server 2008 Feature Pack, August 2008 and installed it and then was able to open the DSN. I found that the "Server" field was simply set to "localhost" and when I tried to test the connection, it timed out. I looked at the old ViewComposer DSN and it had a server and instance specified - "VIEW45-VC\SQLEXP_VIM". I put this in the "vcenter" DSN and then with integrated Windows authentication, I was able to change the default database to "VIM_VCDB" and test the connection and it succeeded. I saved the DSN and attempted to start the vCenter service. This time it started and stayed running and the logs looked good. VMware KB wins again! 30,
cannot start automatically andmanually Posted on May 7, 2013 by cyruslab Problem An user forgot the domain user password for SQL and Vcenter server; reset the password of the domain users. Unable to login to vcenter server with vsphere client, vsphere client said connection fail despite correct domain user credential was used to login. Finding the clues to the cause 1. From vcenter server (vc.cyruslab.local), two services were not started namely VMware VirtualCenter Server and VMware VirtualCenter Management Webservices (This service can only be started after VirtualCenter server is started). These services should start automatically after successfully login to the domain. 2. User attempted to start the VMware VirtualCenter Server manually, however encountered an error that the services could not be started because of failed logon. Right click VMware VirtualCenter Server service and choose properties. Click on Log On tab and manually type in the new password. Do the same for this service. User then happily tried to start VirtualCenter Server again, however encountered another error:
Windows could not start the VMware VirtualCenter Server on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 2.
3. vc.cyruslab.local was Windows 2008 R2 SP1 64-bit OS, user checked vxpd.log from the path C:\ProgramData\VMware\VMware VirtualCenter\Logs, found the following messages Section for VMware VirtualCenter, pid=2316, version=4.1.0, build=build-258902, option=Release [2013-05-07 00:18:33.023 02692 info 'App'] Current working directory: C:\Windows\system32 [2013-05-07 00:18:33.023 02692 info 'App'] Log path: C:\ProgramData\VMware\VMware VirtualCenter\Logs [2013-05-07 00:18:33.023 02692 info 'App'] Initializing SSL [2013-05-07 00:18:33.023 02692 info 'Libs'] Using system libcrypto, version 9080CF [2013-05-07 00:18:34.645 02692 info 'App'] Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000 [2013-05-07 00:18:34.661 02692 info 'App'] Starting VMware VirtualCenter 4.1.0 build-258902 [2013-05-07