Resolving SQL Server Master Data Services (MDS) Patching Errors

By: Svetlana Golovko | Comments (4) | Related: > Master Data Services

Problem

We installed a Cumulative Update on the SQL Server where we have Master Data Services (MDS) installed, but after this patch was applied users are getting errors in the MDS application. How can we resolve this issue?

Solution

MDS has two main components - a Web Application and a database (that could be on the same or on a remote SQL Server).

When you patch a server hosting the MDS Web Application with an SQL Server update and if you have not completed the upgrade sequence users may get this error in the MDS Web Application on client side:

"The client version is incompatible with the database version. Ask your administrator to upgrade the client components, the database component, or both. Run the Master Data Services Configuration Manager on the server for more information.".

If we run MDS Configuration Manager on the MDS server we will see this error:

"The database requires an upgrade. You cannot change system settings until the database is upgraded.".

To fix the error you need to upgrade the database (click on the "Upgrade Database" button).

How to avoid user frustration and errors?

You can not really get rid of these errors if you miss the database upgrade step, but with good planning and established procedures you can improve the user experience.

Make sure that the following is part of you SQL Servers patching procedures.

If you have MDS installed on a server that is scheduled for patching:

Find out where the MDS database is and make sure that you create a backup before patching any MDS components
Patch the server where the MDS feature is installed
Run the MDS Configuration Manager, connect to the database (or databases if you have multiple MDS instances configured on your server)
Upgrade database using MDS Configuration Manager:
- Upgrade Database Wizard will start:
- Click "Next":
- Review the database connection and click "Next". (Note, that the wizard says that the new database will be created. It will not create the new database. The database will be upgraded).
- Review the upgrade status and click "Finish":

The MDS is now fully updated and no errors will be displayed.

Next Steps

Read all MDS tips here.
Make sure you have MDS patching procedures and follow them.
Learn more about Master Data Manager Application here.
Check out the Microsoft MDS resources.

About the author

Svetlana Golovko is a DBA with 13 years of the IT experience (including SQL Server and Oracle) with main focus on performance.

This author pledges the content of this article is based on professional experience and not AI generated.

View all my tips

Comments For This Article

Friday, August 4, 2023 - 6:25:37 AM - Desh Deepak	Back To Top (91464)
We are using SQL server 2019 Master data service configuration manager , When we did Database upgrade then we found database objects have impacted after database upgrade , Any fix for this please , Do we need to execute any patches or some thing else ??

Thursday, June 13, 2019 - 5:57:42 PM - Svetlana Golovko

Hi Sazan,

It looks like this is a known bug that probably don't have a fix yet. See this thread with response from Microsoft: https://social.msdn.microsoft.com/Forums/en-US/042515ac-fbfd-4150-b722-337f762c65dc/help-mds-is-broken-after-update-to-sql-2012-sp4?forum=sqlmds

Thanks,

Svetlana

Thursday, June 13, 2019 - 6:14:23 AM - sazan

Hi,

I have done all the steps mentioned in this article, but after the database upgrade, I get the below error:

Microsoft.MasterDataServices.Configuration.ConfigurationException: Unable to locate the embedded resource. ---> System.IO.FileNotFoundException: Unable to locate the embedded resource.
at Microsoft.MasterDataServices.Configuration.DatabaseUtilities.UpgradeMasterDataServicesDatabase(SqlConnection connection, String databaseName, Collection`1& businessRuleExclusionWarnings)
at Microsoft.MasterDataServices.Configuration.Commands.UpdateMasterDataServicesDatabase.InternalProcessRecord()
at Microsoft.MasterDataServices.Configuration.Commands.ConfigurationCmdlet.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
6060

Monday, January 23, 2017 - 1:25:44 AM - Rajukumar

Hi Svetlana Golovko,

Thanks for the blog it really helps us to resolve the issue.

However, I have a couple of questions on it.

Please provide your thought on below points whenever you get free time.

1) When we performs database migration through configuration manager, what exactly it does? Will it make any structural changes in the database?

2) Will it impact any data changes in the database tables?

Thanks in Advance.

Regards,

Rajukumar