Collection of errors and tricks for Master Data Service 2017

I've met a few errors recently during setting up SQL Server 2016 & 2017 Master Data Services. Although all have been resolved eventually some of them are quite gotchas, and it's good to document for a record.

#1 error -
Permission error on MDS installation folder. Sometimes it's very strange that you already successfully installed the product but got access denied when checking components. To fix this problem login in under an admin account and grab the folder ownership. Then assign permissions and make sure they are inherited from parent.

 

 

#2 error -
Unable to access MDM (Master Data Manager) web site due to version mismatch. This usually happens when you install SQL Server and MDS asynchronously. For example, I installed SQL Server 2017 RTM with MDS, followed by an upgrade of Cumulative Update 8. Later on I had to uninstall and reinstall MDS from scratch but forgot to apply CU8. This error is straight forward once you open MDS Configuration Manager, it will tell you to upgrade. To do that just hit the "Upgrade Database" button on the right side to let the wizard self finish.

#3 error -
MDM slowness or simply Runtime error. When I assigned group permissions on MDM the web site just hung upon mouse clicks. Meanwhile CPU usage soared to above 50%. I checked IIS Manager and saw MDS app pool was waiting for extended time. If I restarted IIS it got back to normal but with a couple of mouse click the slowness reoccurred. However user activities didn't seem to be affected too much. Eventually the hanging web page would throw a runtime error. See below. The solution - again, what I did to match up versions in #2 fix the slowness as well.

#4 error -
800703fa error. Some say try not to login using MDS service account. But I fixed it by following Microsoft KB article https://blogs.msdn.microsoft.com/dsnotes/2016/03/01/com-intermittent-error-800703fa-illegal-operation-attempted-on-a-registry-key/

 

#5 error -
MDM web site is online but user got access denied errors. Out of the box MDS does not allow users to access until they are granted functional permissions, i.e. explorer, system admin, integration admin, version control admin, and super user, etc.

 

#6 error -
Package deployment failed due to folder access problem as in #1. Just add MDS service account to Configuration folder and assign read/write permissions.