Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

"DB schema hash mismatch File" error while upgrading vCenter server and fails with error 1603 (76125)

Last Updated: 1/21/2020Categories: TroubleshootingTotal Views: 6435Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Windows vCenter Server upgrade fails with 1603 error message .

You will see similar log entries as mentioned below

vminst.log
2019-11-05 21:29:48.790-07:00| vcsInstUtil-9451876| I: Leaving function: VM_FinishInstallWithError
2019-11-05 21:46:46.682-07:00| vcsInstUtil-13010631| I: PitCA_MessageBox: Displaying message: "Installation of component VCSServiceManager failed with error code '1603'. Check the logs for more details."
2019-11-05 21:48:53.135-07:00| vcsInstUtil-13010631| I: Entering function: VM_FinishInstallWithError

updateboot.log
2019-11-06T04:46:15.57Z ERROR updateboot Failed to start all services. RC=1. Details:^M
2019-11-06T04:46:15.041Z  Error waiting for service VMwareIdentityMgmtService start. Exit code: 1066 Current State: 1^M^M
Error executing start on service VMwareIdentityMgmtService. Details {^M^M

vpxd.log
2019-11-05T18:29:40.583-07:00 info vpxd[02648] [Originator@6876 sub=ThreadPool] Entering worker thread loop
2019-11-05T18:29:40.583-07:00 info vpxd[06664] [Originator@6876 sub=ThreadPool] Thread enlisted
2019-11-05T18:29:40.583-07:00 info vpxd[06664] [Originator@6876 sub=ThreadPool] Entering worker thread loop
2019-11-05T18:29:41.201-07:00 info vpxd[16376] [Originator@6876 sub=Default] [VdbSchemaLoader::LookupSchemaFromDB] Loaded schema and index information from DB
2019-11-05T18:29:41.403-07:00 info vpxd[10448] [Originator@6876 sub=ThreadPool] Spawning additional worker - allocated: 117, idle: 1
2019-11-05T18:29:41.403-07:00 info vpxd[03100] [Originator@6876 sub=ThreadPool] Thread enlisted
2019-11-05T18:29:41.403-07:00 info vpxd[03100] [Originator@6876 sub=ThreadPool] Entering worker thread loop
2019-11-05T18:29:42.232-07:00 info vpxd[16376] [Originator@6876 sub=vpxdVdb] DB Version set in vpxd.cfg = Microsoft SQL Server 2012 (SP4-GDR) (KB4057116)
2019-11-05T18:29:42.321-07:00 info vpxd[16376] [Originator@6876 sub=DbSchemaHash] [VpxdDbSchemaHash::GetSignatureFilename]: sqlDir: C:\Program Files\VMware\vCenter Server\vpxd\sql\
2019-11-05T18:29:42.321-07:00 info vpxd[16376] [Originator@6876 sub=DbSchemaHash] [VpxdDbSchemaHash::CheckSchema]: signature file: C:\Program Files\VMware\vCenter Server\vpxd\sql\signature_mssql.txt
2019-11-05T18:29:42.346-07:00 error vpxd[16376] [Originator@6876 sub=DbSchemaHash] [VpxdDbSchemaHash::CheckSchema] DB schema hash mismatch File: 4aec34f21815e498c3c79c3a68a32c3c DB: aaceaee476f7596046bb7ec21a8feaf9
2019-11-05T18:29:42.346-07:00 error vpxd[16376] [Originator@6876 sub=Main] Init failed. SystemError: class Vmomi::Fault::SystemError::Exception(Fault cause:
vmodl.fault.SystemError
--> )
--> [context]zKq7AVMEAAAAADV5xgANdnB4ZAAA6qcedm1hY29yZS5kbGwAAKANBgAONQYAOj8CAfVNAHZtb21pLmRsbAABmTUBAkzuIXZweGQuZXhlAALRMyICK6JEAleqRIKrtgoBA/ITAEtFUk5FTDMy
LkRMTAAE9FQBbnRkbGwuZGxsAA==[/context]
2019-11-05T18:29:42.348-07:00 error vpxd[16376] [Originator@6876 sub=Default] Failed to intialize VMware VirtualCenter. Shutting down
2019-11-05T18:29:42.348-07:00 info vpxd[16376] [Originator@6876 sub=SupportMgr] Wrote uptime information19078368711

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.

User ID defined in vCenter database and vpxd.cfg file are different

Resolution

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

Connect to the vCenter Server database.

SQL - Use SQL Management Studio to connect to vCenter Database.

Postgres - Run the below query to connect to VCDB

/opt/vmware/vpostgres/current/bin/psql -d VCDB -U postgres

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

Select * from VPX_Version;

Note the value in 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=4384, version=6.5.0, build=9451637, option=Release

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

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

7. If the versions match, then validate the database_user_id used to login to System DSN (vCenter Database) and match it with the user_id defined in vpxd.cfg file

To change the vCenter Server user ID in vpxd.cfg file, perform the following:

Stop vpxd service.

Navigate to this location,

Windows: C:\ProgramData\VMware\vCenterServer\cfg\vmware-vpx

VCSA: /etc/vmware-vpx/

Take a backup of vpxd.cfg

Open the vpxd.cfg file in a text editor.

Locate the <DB> element and modify the value for <key_2> to reflect the new database user ID.
...
<DB>
<key_2>database_user_id</key2>
<key_3></key_3>
</DB>
...

If you are using Windows Integrated Authentication to connect to the vCenter Server database, remove the value for <key_3>.

Save the vpxd.cfg file.

Click Start, right-click Command Prompt, and select Run as administrator to open a command prompt as an administrator. If its VCSA go to Step 10

Navigate to C:\Program Files\VMware\vCenter Server\vpxd

Run command vpxd -p and update the same DB password twice.

Start vpxd service.

Re-run the installer to perform the upgrade.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
vSAN 健全性サービス - オンライン健全性 – HPE SAS ソリッド ステート ドライブ (76386)

KB
•
由于 /dev/sdc 空间不足，升级到 vRealize Operations Manager 8.0 失败 (75327)

KB
•
Download and Install VMware Fusion (2014097)

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

Related Versions:

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

Take Our Survey

Support Assistant