The following table lists the common events that may indicate a problem with Active Directory replication, and the root causes and solutions.
Table: Events That May Indicate a Problem with Active Directory Replication
| Event or Symptom | Root Cause | Solution |
|---|---|---|
|
Net Logon Event ID 5805 |
A computer account failed to authenticate, which is usually caused by either multiple instances of the same computer name, or the computer name has not replicated to every domain controller. |
If you do not find multiple instances of the computer name, verify that replication is functioning for the domain that contains the computer account. |
|
NTDS Event ID 1083 |
A duplicate object is present in the Active Directory of the replication partner of the local domain controller, so updating it is impossible. |
|
|
NTDS Event ID 1265 |
Replication failed for the reason stated in the message text. |
Use Repadmin.exe to further identify the problem. If the event message indicates a DNS lookup failure or the RPC server is unavailable, see, "Common Events and Symptoms that Indicate DNS Problems" in Troubleshoot DNS Problems Related to Active Directory. If the event message indicates that the target account name is incorrect, troubleshoot Globally Unique Identifier (GUID) discrepancies. If the event message indicates a time difference between the client and server, synchronize replication from the primary domain controller (PDC) emulator. |
|
NTDS Event ID 1311 |
This error occurs when the replication configuration information in Active Directory Sites and Services does not accurately reflect the physical topology of the network. |
Troubleshoot NTDS event ID 1311. |
|
NTDS Event ID 1388 |
This error is usually generated by a lingering object which resulted from disconnecting a domain controller for too long. |
If the domain controller does not also function as a global catalog server, see Object-Related Problems. |
|
NTDS Event ID 1645 |
This error occurs over an existing replication link when the GUID of the NTDS Settings object of a replication partner does not match the GUID defined in the Service Principal Name (SPN) attributes of the computer object of this replication partner. |
Troubleshoot GUID discrepancies. |
|
SceCli event ID 1202 |
A user account in one or more Group Policy objects (GPOs) cannot be resolved to a security identifier (SID). This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights Assignment or Restricted Groups branch of a GPO. |
Troubleshoot SceCli event ID |
Using Repadmin to Identify Replication Problems
To identify Active Directory replication problems, you use the repadmin /showreps command. For more information about using this tool, see the TechNet article Repadmin Overview.