This article has been archived. It is offered "as is" and will no longer be updated.
The semantic database analysis checker that is included with the Ntdsutil.exe tool may not be able to fix a mangled subref. In this scenario, Active Directory replication may fail, and event messages that are similar to the following may be logged in the Directory Service event log:
Event Type: Warning Event Source: NTDS KCC Event Category: Knowledge Consistency Checker Event ID: 1265 Date: Date Time: Time User: N/A Computer: Computer_Name Description: The attempt to establish a replication link with parameters
Event Type: Error Event Source: NTDS Replication Event Category: Replication Event ID: 1645 Date: Date Time: Time User: Everyone Computer: Computer_Name Description: The Directory Service received a failure while trying to perform an authenticated RPC call to another Domain Controller. The failure is that the desired Service Principal Name (SPN) is not registered on the target server. The server being contacted is 339ca0d9-7dd7-4e15-bbee-1998387e4634._msdcs. name.com. The SPN being used is E3514235-4B06-11D1-AB04-00C04FC2DCD2/339ca0d9-7dd7-4e15-bbee-1998387e4634/eas CNF:3311d1ff-608f-411c-97dc-56d221e04bab.parent.root.com@eas CNF:3311d1ff-608f-411c-97dc-56d221e04bab.parent.name.com.
Please verify that the names of the target server and domain are correct. Please also verify that the SPN is registered on the computer account object for the target server on the KDC servicing the request. If the target server has been recently promoted, it will be necessary for knowledge of this computer's identity to replicate to the KDC before this computer can be authenticated.
When you try resolve this problem by using the semantic database analysis checker that is included with Ntdsutil, you cannot resolve the problem, and you may receive a message that is similar to the following:
ntdsutil: sem d a semantic checker: go fix Fixup mode is turned on Opening DIT database... Done.
Fixing conflict mangled name: eas CNF:3311d1ff-608f-411c-97dc-56d221e04bab Fixing by rename with structural collision.
Could not update "datatable" table: key already exists Error<8000ffff>: failed to fix mangled dn eas. Retrying.
***Manual intervention required*** Error <0>: non mangled name isn't a phantom (1) There is an object holding the non mangled name DC=child,DC=parent,DC=root,DC=com. The object must be removed or renamed before the mangled name may be corrected. DBG: Rolling back transaction due to error 80004005. Can't fix Mangled NC Error.
To resolve this problem, install this hotfix on the domain controller that has the name-mangled object, restart the computer in Dsrepair mode, and then run the Ntdsutil go fix command to use the semantic database analysis checker on the Ntds.dit database. In Dsrepair mode, clients may receive an "Access denied" error message if they try to access DFS Root or DFS Link information on the computer. The generation of the error message is by design. This hotfix includes a new version of Ntdsutil.
Note To start the domain controller in Dsrepair mode, press F8 during the startup process, and then select Directory Service Restore Mode in the Advanced Options menu.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
No prerequisites are required.
You must restart your computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.