Neal Waterstreet

MDSERR400038

by Leave a Comment

I had just finished deploying a model between environments and tried to validate when I got this message:

MDSERR400038|Unpublished business rules exist. Apply the business rules before running Business Rules or Validation again.

The error message on this one is pretty straightforward. I had a list of business rules to publish and tried to set them all as active with a SQL update instead of using Master Data Manager. It didn’t work. I updated the business rules manually and was then able to process the model.

MDS: Issue with upgrading server

by Leave a Comment

We recently upgraded a clustered server to MDS 2016. I went to go verify the upgrade and ran into this strange error when viewing all of the entities:

After troubleshooting for a while, the cause became painfully obvious. It turned out that I needed to clear the cache in IE since it still had the previous 2012 version in cache.

I hope this saves someone some time.

MDS: Problem with user access

by Leave a Comment

Last week there was a problem with user access after a migration between environments. Members of one of the AD groups that had been granted access were not able to access the website or by the MDS Add-in for Excel.

First, I checked the security settings and there was no problem with the configuration. Everything looked OK with each of the security sections. I then added one of the users manually to check if it was a problem with the AD group itself. The user was able to access the model and modify data successfully. The AD group name was spelled correctly, but the scope was set to “Global” instead of “Universal”. Once the AD group was updated all of the users were able to access MDS.

References:

https://technet.microsoft.com/en-us/library/cc755692(v=ws.10).aspx

 

MDS Error “300008: The supplied entity is not valid.”

by Leave a Comment

I got an email the other day that someone was getting an error on one of the lower MDS environments. I logged into Master Data Manager and got this message:

It appeared to be impacting all of the models and entities in the repository. The subscription views were available and data was there, but at this point the entities were all read-only.

I then got this message:

“The operating system returned error 21(The device is not ready.) to SQL Server during a read at offset 0x… in file ‘T:\MSSQL\DATA\tempdb.mdf’. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.”

Luckily this was easily resolved. There was something wrong with the tempdb and the SQL Server instance needed to be restarted. MDS was working correctly once the server was brought back up.