Article ID: 919633 - Last Review: October 9, 2011 - Revision: 2.0

You may receive an error message when you try to run the DFS Management snap-in on a Windows Server 2003 R2-based computer

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

Expand all | Collapse all

SYMPTOMS

When you try to run the DFS Management snap-in on a Microsoft Windows Server 2003 R2-based computer, you may experience one of the following symptoms:

When you try to click Add Replication Groups to Display, you receive the following error message in the DFS Management snap-in:
MMC has detected an error in a snap-in and will unload it
* Report this error, and then shutdown mmc
* Unload snap-in and continue running unhandled exception in managed code snap-in FX: {671ee405-c969-49f9-ad1b-65e96b3b9910}
Exception has been thrown by the target of an invocation
When you try to run the New Replication Group Wizard, you receive the following error message:
The Security Descriptor on Active Directory Object: CN=DFSR-GlobalSettings,Cn=system,DC=DomainComponent,DC=DomainComponent is invalid. The security Descriptor is invalid
The Security Descriptor cannot be deserialized
The Binary form of an ACE object is invalid
Parameter name: BinaryForm

Note The data continues to replicate for groups that are already created even after you receive the error message.

Back to the top

CAUSE

This problem may occur when there is corrupted access control entry (ACE) in the Active Directory object.

Back to the top

To resolve this problem, install the hotfix that is discussed in Microsoft Knowledge Base article 928569. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

928569 (http://support.microsoft.com/kb/928569/ ) FIX: The first CLR thread pool worker thread is never initialized for COM+ in an ASP.NET Web application that is configured to run under the .NET Framework 2.0

Back to the top

WORKAROUND

To work around this problem, use one of the following methods:

Try to set the Security to Schema defaults by using the following command:
DSAcls.exe "CN=DFSR-GlobalSettings,Cn=system,DC=<Domain Component>,DC=DomainComponent" /S/T
Use the ADSI Edit MMC snap-in to turn off security inheritance on the object and to delete one access control entry at a time. Then, retest the DFS Management snap-in.

Back to the top