1311 — NTDS KCC |
The replication configuration information in Active Directory does not accurately reflect the physical topology of the network. |
Fixing Replication Topology Problems (Event ID 1311) |
1388 — NTDS Replication |
Strict replication consistency is not in effect, and a lingering object has been replicated to the domain controller. |
Fixing Replication Lingering Object Problems (Event IDs 1388, 1988, 2042) |
1925 — NTDS KCC |
The attempt to establish a replication link for a writable directory partition failed. This event can have different causes, depending on the error. |
Fixing Replication Connectivity Problems (Event ID 1925)
Fixing Replication DNS Lookup Problems (Event IDs 1925, 2087, 2088) |
1988 — NTDS Replication |
The local domain controller has attempted to replicate an object from a source domain controller that is not present on the local domain controller because it may have been deleted and already garbage-collected. Replication will not proceed for this directory partition with this partner until the situation is resolved. |
Fixing Replication Lingering Object Problems (Event IDs 1388, 1988, 2042) |
2042 — NTDS Replication |
Replication has not occurred with this partner for a tombstone lifetime, and replication cannot proceed. |
Fixing Replication Lingering Object Problems (Event IDs 1388, 1988, 2042) |
2087 — NTDS Replication |
Active Directory could not resolve the DNS host name of the source domain controller to an Internet Protocol (IP) address, and replication failed. |
Fixing Replication DNS Lookup Problems (Event IDs 1925, 2087, 2088) |
2088 — NTDS Replication |
Active Directory could not resolve the DNS host name of the source domain controller to an IP address, but replication succeeded. |
Fixing Replication DNS Lookup Problems (Event IDs 1925, 2087, 2088) |
2095 — NTDS Replication |
Update sequence number (USN) rollback has occurred and replication has been stopped. This error indicates an improper Active Directory restore, possibly of a virtual machine file (.vhd). |
For an explanation of this problem and recommendations for solutions, see Running Domain Controllers in Virtual Server 2005 on the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=38330). |
5805 — Net Logon |
A machine account failed to authenticate, which is usually caused by either multiple instances of the same computer name or the computer name not replicating to every domain controller. |
Fixing Replication Security Problems |