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

VMware VirtualCenter Server service fails to start with the vpxd.log error: ODBC error: (28000) (1017688)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 47129Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

If you experience an ungraceful shutdown of the database (for example, because of a power outage), you may experience these symptoms:

The VMware VirtualCenter Server service fails to start.

ODBC connection to the database tests successfully with the specified user.

The vpxd.log file (located at C:\Documents and Settings\All Users\Application Data\VMware\VirtualCenter\logs) contains entries similar to:

[02896 error 'App'] ODBC error: (28000) - [Microsoft][SQL Native Client][SQL Server]Login failed for user 'vmware_user'.
[02896 error 'App'] Error getting configuration info from the database
[02896 error 'App'] [Vpxd::ServerApp::Init] Init failed: VpxdVdb::InitVdb::GetInstance(), false, false)
[02896 error 'App'] Failed to intialize VMware VirtualCenter. Shutting down...
[02896 info 'App'] Forcing shutdown of VMware VirtualCenter now

Cause

This is a rare issue that occurs if a password is corrupted by an ungraceful shutdown (for example, due to a power outage). With a graceful shutdown, Windows saves everything that was in cache to disk, but when an operating system shuts down unexpectedly, settings can be lost or corrupted. The password can get corrupted if the registry is being accessed at the time of the outage.

This issue occurs even if:

The integrity of the database has been verified.

The SQL permissions have been verified and set properly.

The connection information (including password) is present and correct in the registry key:

32-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VirtualCenter\DB

64-bit operating systems: HKEY_LOCAL_MACHINE\SOFTWARE\wow6432node\VMware, Inc.\VMware VirtualCenter\DB

Resolution

To resolve this issue, you must change the password.

To change the password:

Open a command prompt. For more information, see Opening a command or shell prompt (1003892).

Change to the directory containing the VMware VirtualCenter Server service executable vpxd.exe (typically located at C:\Program Files\VMware\Infrastructure\VirtualCenter Server). If vpxd.exe is not at that path:

Click Start > Run, type services.msc, and click OK.

Right-click the VMware VirtualCenter Server Service and click Properties. The path to vpxd.exe is on the General tab.

When you have verified the location of vpxd.exe, run this command in the appropriate directory to change the password in the registry:

vpxd -p

To start the VMware VirtualCenter Server service, right-click VMware VirtualCenter Server service and click Start.

Related Information

Note: With vCenter Server 4.1, the vCenter Server system must have a 64-bit DSN. Using a 32-bit DSN on vCenter Server 4.1 may result in a similar issue outlined in the above symptoms. For more information, see the ESX and vCenter Server Installation Guide for vCenter Server 4.1.

For related information, see Starting VMware VirtualCenter Server service when using SQL authentication fails with the error: Login Failure, Failed to connect to database (2015824).

Opening a command or shell prompt
Starting VMware VirtualCenter Server service when using SQL authentication fails with the error: Login Failure, Failed to connect to database
VMware VirtualCenter Server サービスが次のエラーで起動に失敗する： ODBC error: (28000)
VMware VirtualCenter Server 服务启动失败，并显示 vpxd.log 错误：ODBC 错误: (28000)

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
•
将 ESXi 主机添加到 vCenter Server 清单失败并出现错误： 在 vCenter Server 上为对象调用“datacenter.queryconnectioninfo”失败 (1027672)

KB
•
Download and Install VMware Fusion (2014097)

KB
•
vCenter Server インベントリへの ESXi ホストの追加が次のエラーで失敗する：vCenter Server のオブジェクトに対する呼び出し「datacenter.queryconnectioninfo」に失敗しました (Call "datacenter.queryconnectioninfo" for object on vCenter Server failed) (1027672)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Heartbeat

VMware vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Heartbeat 6.7.x

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

VMware vCenter Server 5.x - View

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.1 Extended Support

VMware vCenter Server 5.0.x

VMware vCenter Server 5.0 Beta

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

view all

Take Our Survey

Support Assistant