Master Data Services configuration manager fails to start due to some ACL problem - by Dmitry Mashkov [MSFT]

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 635251 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 1/9/2011 7:33:27 AM
Access Restriction Public

Description

When starting Master Data Services configuration manager fails to start with:

---------------------------
Unexpected Error
---------------------------
An unexpected error occurred: 

This access control list is not in canonical form and therefore cannot be modified..
---------------------------
Abort   Retry   Ignore   
---------------------------

This error is meaningless. If you think this is a problem - at least tell WHICH access list is "this".
Sign in to post a comment.
Posted by Dmitry Mashkov [MSFT] on 1/11/2011 at 9:57 PM
No, I did not reinstall. I did not even reboot the machine. Not sure what changed.
Posted by Microsoft on 1/11/2011 at 4:13 PM
This is the first report of the error with MDS that I could find.

If you have reinstalled, I guess there is not much we can do to figure out which key caused it the first time. If other people hit this or if it gets votes we'll investigate further.

For now I will close the item as no-repro.

Thank you for taking the time to report the issue!
Jason Howell
Sr. Escalation Engineer
Microsoft SQL Server Support
Posted by Dmitry Mashkov [MSFT] on 1/11/2011 at 10:52 AM
It did not reproduce on the subsequent run.
It is not a sysprepped machine - it is a clean physical workstation, non-domain joined.
Posted by Microsoft on 1/10/2011 at 4:38 PM
Hi Dmitry,

Thank you for submitting this connect item. We will look into the error you provided.
Error "This access control list is not in canonical form and therefore cannot be modified.."

So you are seeing this error as a popup in MDS Configuration Manager when it won't start.

Sorry the error is not very clear of the cause of the issue.

The cause is likely to be the tool newsid or sysprep - Did you sysprep the virtual machine?
This error has been caused in other products if you use the NewSID tool to change the security identifier (SID) of the computer or virtual machine.

We could run the Process Monitor tool to observe which registry key it is failing on.
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
Download the tool
Run the tool
Add an Include Filter for Process Name = MDSConfigTool.exe
It will start capturing
Now repro the failure in Configuration Manager
When the error occurs, switch back to the Process Monitor and stop the Capture (Control+E or magnifying glass icon).
You can review the results (bottom up) for any errors in the registry reads.
If you don't spot it right away, feel free zip and upload the file here.


Two prior products have documented the steps taken to workaround this. Are you flexible to experiment to see if any of these methods helps?

KB 942517 - http://support.microsoft.com/kb/942517
Two methods offered -
1. reset the local security policy database from the template.
2. Manually repair the registry key (but we don't know which key it is just yet).

KB 916893 - http://support.microsoft.com/kb/916893
Method 3.. you can change the computer into a workgroup, and add it back to the domain.
2. Join the computer to a workgroup, and then remove the computer account from the domain.
3. Use the System Preparation tool (Sysprep.exe) to reset the SID of the computer.
4. Restart the computer, and then rejoin the computer to the domain.

Thanks!
Jason Howell
Sr. Escalation Engineer
Microsoft SQL Server Support