Description:
Event Source:NTDS KCC
Event Category:Knowledge Consistency Checker
Event ID:1925
Date:3/24/2005
Time:9:15:46 AM
User:NT AUTHORITY\ANONYMOUS LOGON
Computer:DC3
Description:
The attempt to establish a replication link for the following
writable directory partition failed.
Directory partition:
CN=Configuration,DC=contoso,DC=com
Source domain controller:
CN=NTDS Settings,CN=DC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=contoso,DC=com
Source domain controller address:
f8786828-ecf5-4b7d-ad12-8ab60178f7cd._msdcs.contoso.com
Intersite transport (if any):
This domain controller will be unable to replicate with the
source domain controller until this problem is corrected.
User Action
Verify if the source domain controller is accessible or
network connectivity is available.
Additional Data
Error value:
8524 The DSA operation is unable to proceed because of a DNS
lookup failure.
Solution :
Proceed with DNS testing as described in "Event ID 2087: DNS lookup failure caused replication to fail."
***
- Error code: 1396 - See 939820 for a hotfix applicable to Microsoft Windows Server 2003.
- Error code: 8439 - See 948925.
- Error code: 5 (Error code 5) - See 938702.
- Error code: 1727 (Error code 1727) - See 911799.
***
This is a generic message saying that the replication failed for the specified reason. The useful information is the one found in the "Additional data" as it provides a clue about the reason why the replication failed. Of course, another important detail is the actual partition that failed to replicate. As a result, any attempt to troubleshoot this problem should consider the specific error code, not just the event id itself.
***
Error 1908 (Could not find the domain controller for this domain.) - The "Event ID 1925: Attempt to establish a replication link failed due to connectivity problem" link provides suggestions on how to troubleshoot this connectivity problem.
Error 8524 The DSA operation is unable to proceed because of a DNS lookup failure. - Proceed with DNS testing as described in the "Event ID 2087: DNS lookup failure caused replication to fail." link.
This error can also occur if there is a missing or corrupted SYSVOL folder on the destination DC that this DC is trying to replicate to. First do a <CMD> net share to see if the SYSVOL shares are present. If you don't see the SYSVOL shares or you get errors, see article 257338 for help in tracking down this problem.
This signifies errors between site replication. This is normally attributed to DNS configuration errors.
Posts
