Neal Waterstreet

MDS Error: “200085: The attribute cannot be saved. The input mask is not valid.”

by Leave a Comment

During a recent deployment, I received an error that I’d never seen before. It’s always fun to get these.

“200085: The attribute cannot be saved. The input mask is not valid.”

My initial thought was that someone had modified an attribute and created a conflict. The model was new and sparsely populated, so I was able to view the data. It didn’t appear to be data related.

It turned out to be a custom input mask was not included in the deployment. The mask was created in a lower environment but never migrated. Once that update was made the deployment completed successfully.

 

The product version and database version are not compatible.

by Leave a Comment

This isn’t a very comforting message the first time you see it:

It’s pretty simple to resolve though. The problem is that the MDS application (product) and repository (database) are on different versions and the repository needs to be upgraded. This is usually the result of a service pack being deployed to SQL Server.

1. RDP to the MDS application server and select “Master Data Services Configuration Manager”.

2. In the Configuration Manager, select “Database Configuration” on the left.

3.  You should see the error below in the the Database Configuration window.

 

 

 

4. Select “Upgrade Database…”.

5. Select “Next”.

6. Depending on the size of the repository, this may run for several minutes.

7. When the upgrade is complete, there will be a “Success” message under “Status”. Click “Finish”.

8. Your repository upgrade is complete.

SYSERR229

by Leave a Comment

SYSERR229|The EXECUTE permission was denied on the object ‘IdList’

Recently I ran into this error while validating a model on a new instance. I checked the SQL accounts that MDS is running under and one of them was incorrect. The ‘mds_schema_user’ no longer had lost access to the ‘mdm’ schema. I granted the account ownership of the schema the model was able to validate normally.

MDSERR310029

by Leave a Comment

MDSERR310029|The status of the specified batch is not valid.

This error occurs when using the entity-based staging process (leaf tables). If multiple entries of the same BatchTag value are executed concurrently, this error can appear. It can happen in the same entity or different entities or models.

The best solution I’ve found is to update mdm.tblStgBatch and set the status_id for the BatchTag to completed. You can then update the BatchTag name in the leaf and reset the ImportStatus_ID back to 0 and reprocess the batch.

An alternative is to append a timestamp to the BatchTag to make it unique. That should keep this from happening.

Credit on this to James Serra, who has a good post on this error, and to Microsoft.