Recently some SQL Server instances at a client were upgraded to the latest cumulative update of SQL Server 2012 service pack 1. The reason for this update was the added functionality to create Power View reports on top of Analysis Services Multidimensional. However, one of the instances also has Master Data Services (MDS) installed and after the update we couldn't connect to the Master Data Manage anymore using the browser. There were two separate issues that had to be solved.
Somehow some permissions were lost during the upgrade, leading to the following error screen when trying to connect:
For once, the error message is crystal clear: Cannot read configuration file due to insufficient permissions. It even details the location of the web.config file. All we have to do now is add the local account MDS_ServiceAccounts if it isn't added yet and give this account read permission on the config file.
This should get rid of the internal error message.
MDS Database needs an upgrade
Unfortunately our problems weren't over, as we were now greeted with another error screen when trying to connect.
MDS now complains the database version (meaning SQL Server) has a more recent version than the client (which is MDS itself). Let's take a look at the MDS Server Configuration Manager to see what is going on. Make sure you open the Configuration Manager using admin privileges. We can immediately see that something is wrong at the welcome screen:
It looks like no SQL Server database has been configured, while this was the case before the upgrade. Let's go to the database configuration tab.
Hmm, this looks pretty empty. Click on Select Database... and configure your MDS database in the prompt.
The result already looks much better, except the error in bright red of course.
This error says the database needs to be upgraded. Right next to it is a button called Upgrade Database so it seems obvious we'll click that one. This will start a wizard which will guide you through the upgrade process. Hit Next until the upgrading begins. The wizard will fire off some scripts against the database to get it to consistent version.
Once the wizard has finished, everything looks OK in the configuration screen:
Now we can connect back to the Master Data Manager using the browser or Excel (if you have the plug-in installed).