Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
After migrating/moving the vCenter Server database to new location, you may experience these symptoms: You cannot start the VirtualCenter Server Service. In the vpxd.log file, you see entries similar to:[2010-04-19 14:25:36.995 04976 info 'App'] [Vpxd::ServerApp::Init:758] Calling: VpxdCertificate_Load(gDB, CERTIFICATE_VMDBPATH ) [2010-04-19 14:25:36.995 04976 info 'App'] [Vpxd::ServerApp::Init:759] Calling: VpxdVdb::Init(Vdb::GetInstance(), false, false) [2010-04-19 14:25:36.995 04976 error 'App'] ODBC error: (IM002) - [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified [2010-04-19 14:25:36.995 04976 error 'App'] Error getting configuration info from the database [2010-04-19 14:25:37.011 04976 error 'App'] [Vpxd::ServerApp::Init] Init failed: VpxdVdb::Init(Vdb::GetInstance(), false, false)2012-09-12T00:27:22.119-07:00 [05988 error 'Default'] [VpxdVdb::SetDBType]: Database error: ODBC error: (IM002) - [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified2012-09-12T00:27:22.119-07:00 [05988 error 'Default'] Error getting configuration info from the database2012-09-12T00:27:22.119-07:00 [05988 error 'Default'] [Vpxd::ServerApp::Init] Init failed: VpxdVdb::Init(VpxdVdb::GetVcVdbInstId(), false, false, NULL)2012-09-12T00:27:22.119-07:00 [05988 error 'Default'] Failed to initialize VMware VirtualCenter. Shutting down...2012-09-12T00:27:22.119-07:00 [05988 info 'Default'] Wrote uptime information2012-09-12T00:27:22.119-07:00 [05988 error 'Default'] Alert:false@ d:/build/ob/bora-623373/bora/vpx/vpxd/util/vpxdVdb.cpp:408
This issue can occur if the vCenter Server registry settings for its ODBC connection was not updated to reflect the change in ODBC configuration.
To resolve this issue: Ensure that the ODBC System DSN connection is updated and that a test connection is successful. For more information, see Viewing and modifying the database server and/or database used by VirtualCenter (Microsoft SQL) in vCenter Server installation fails with ODBC and DNS errors (1003928). Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 256986.Navigate to the HKLM\SOFTWARE\Wow6432Node\VMware, Inc\VMware VirtualCenter\DB\1 registry key.Notes: In vCenter Server 5.x, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter\DB\1. For 64-bit versions of Windows, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VirtualCenter\DB\1.Ensure that the key contains the correct DSN. If the registry contains an incorrect DSN, backup the registry and then update the DSN. Restart the VMware VirtualCenter Server service. For more information, see Stopping, starting, or restarting vCenter services (1003895).Note: You may have to reset the encrypted password found in the registry. For more information, see the Reset the encrypted password found in the registry section in Starting VMware VirtualCenter Server service when using SQL authentication fails with the error: Login Failure, Failed to connect to database (2015824).
If issue persists, see vCenter Server installation fails with ODBC and DNS errors (1003928) for further troubleshooting. How to stop, start, or restart vCenter Server servicesvCenter Server installation fails with ODBC and DSN errorsStarting VMware VirtualCenter Server service when using SQL authentication fails with the error: Login Failure, Failed to connect to databaseデータベースを新しいサーバに移行した後に vCenter Server サービスを開始することができない在将数据库迁移到新服务器后无法启动 vCenter Server 服务