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

vCenter Server services fail to start with error: DB Schema hash mismatch (1031719)

Last Updated: 4/1/2016Categories: TroubleshootingTotal Views: 17000Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Cannot start the VMware vCenter Server service

Starting the VMware vCenter Server service fails

In the event log, you see entries similar to:

Database version id '410' is incompatible with this release of VirtualCenter.
Database version id '501' is incompatible with this release of VirtualCenter.

vCenter Server services fail to start

You see the error:

Windows could not start Virtual center in the Local computer. review system event log. If tis is a non Microsoft-service vendor and refer to service specific vendor error code 2

In the vpxd.log file, you see entries similar to:

YYYY-MM-DDT<time> [04996 info 'utilvpxdVdb'] [VpxdVdb::SetDBType] Logging in to DSN: vcenter with username vcuser
YYYY-MM-DDT<time> [04996 info 'Default'] [VdbSchemaLoader::LookupSchemaFromDB] Loaded schema and index information from DB
YYYY-MM-DDT<time>[04996 info 'utilvpxdDbSchemaHash'] [VpxdDbSchemaHash::GetSchemaFilename]: sqlDir: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\sql\
YYYY-MM-DDT<time>[04996 info 'utilvpxdDbSchemaHash'] [VpxdDbSchemaHash::CheckSchema]: schema file: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\sql\VCDB_mssql.sql
YYYY-MM-DDT<time>[04996 error 'utilvpxdDbSchemaHash'] [VpxdDbSchemaHash::CheckSchema] DB schema hash mismatch
YYYY-MM-DDT<time>[04996 error 'utilvpxdDbSchemaHash'] [VpxdDbSchemaHash::CheckSchema] File: 4ae87f5460fe1cc421f75caf1844f15e
YYYY-MM-DDT<time>[04996 error 'utilvpxdDbSchemaHash'] [VpxdDbSchemaHash::CheckSchema] DB: 189f5786f3b0b59411dec2d8f9411ed9
YYYY-MM-DDT<time>[04996 error 'vpxdvpxdMain'] [Vpxd::ServerApp::Init] Init failed: VpxdDbSchemaHash::CheckSchema()
--> Backtrace:
--> backtrace[00] rip 000000018018aafa
--> backtrace[01] rip 0000000180102568
--> backtrace[02] rip 00000001801038de
--> backtrace[03] rip 000000018008d24b
--> backtrace[04] rip 00000000003e5c2c
--> backtrace[05] rip 0000000000406512
--> backtrace[06] rip 000000014081ca8f
--> backtrace[07] rip 000000014081b3dc
--> backtrace[08] rip 0000000140a3cbdb
--> backtrace[09] rip 000007fefe71a82d
--> backtrace[10] rip 00000000775059ed
--> backtrace[11] rip 00000000779ac541</time></time></time></time></time></time></time></time>

YYYY-MM-DDT<time> [04996 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...</time>

--> backtrace[00] rip 000000018018aafa

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs in one of the cases:

The vCenter Server database was restored with an earlier version that is not compatible with the current running version of vCenter Server, resulting in a database schema mismatch.

During an upgrade of vCenter Server, the database upgrade process failed after modifying the current database schema.

Resolution

To resolve this issue when there is a schema mismatch, restore the correct version of the vCenter Server database associated with the current build of vCenter Server.

To verify if there is a vCenter Server database schema mistmatch:

Connect to the vCenter Server database using the SQL management tool.

Run this query to list the rows in the VPX_Version table in the vCenter Server database:

Select * from VPX_Version

Note the value in the the VERSION_VALUE field.

Open the vpxd.log file and locate the initial header of the file. The header shows the current version of vCenter Server.

For example, the header appears similar to:

Section for VMware VirtualCenter, pid=4472, version=5.1.0, build=1235232, option=Release

Compare the vCenter Server versions noted in Step 3 and Step 4. If the versions do not match, the the vCenter Server database is running an incorrect schema.

To upgrade the database schema to the correct version:

Uninstall vCenter Server.

Restore the vCenter Server database from a backup.

Reinstall vCenter Server using the Use existing database option.

Related Information

Location of vCenter Server log files
vCenter Server 服务无法启动，并出现“DB Schema hash mismatch”错误

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

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

Result 1 of 1

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