Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Cannot start the vCenter Server service after migrating the db to a new server (1020836)

Last Updated: 4/10/2017Categories: TroubleshootingTotal Views: 50915Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

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 specified
2012-09-12T00:27:22.119-07:00 [05988 error 'Default'] Error getting configuration info from the database
2012-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 information
2012-09-12T00:27:22.119-07:00 [05988 error 'Default'] Alert:false@ d:/build/ob/bora-623373/bora/vpx/vpxd/util/vpxdVdb.cpp:408

Cause

This issue can occur if the vCenter Server registry settings for its ODBC connection was not updated to reflect the change in ODBC configuration.

Resolution

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).

Related Information

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 services
vCenter Server installation fails with ODBC and DSN errors
Starting VMware VirtualCenter Server service when using SQL authentication fails with the error: Login Failure, Failed to connect to database
データベースを新しいサーバに移行した後に vCenter Server サービスを開始することができない
在将数据库迁移到新服务器后无法启动 vCenter Server 服务

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant