Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 1864 Source: ActiveDirectory_DomainService
This is the replication status for the following directory partition on this directory server.
This directory server has not recently received replication information from a number of directory servers. The count of directory servers is shown divided into the following intervals.
More than 24 hours:
More than a week:
More than one month:
More than two months:
More than a tombstone lifetime:
Tombstone lifetime (days):
Directory servers that do not replicate in a timely manner may encounter errors. They may miss password changes and be unable to authenticate. A DC that has not replicated in a tombstone lifetime may have missed the deletion of some objects and may be automatically blocked from future replication until it is reconciled.
To identify the directory servers by name use the dcdiag.exe tool.
You can also use the support tool repadmin.exe to display the replication latencies of the directory servers. The command is "repadmin /showvector /latency <partition-dn>".
|English: Request a translation of the event description in plain English.|
From a support forum:
I have two Domain Controllers (Windows 2008 core, running Windows 2008 functional level) in a child domain called test.domain.com and the parent domain is domain.com. I was getting this message. Running repadmin /showrepl on both domain controllers did not reveal any problem. However, once I used:
I could see the troubled domain controller and I was able to fix it. See T776210 on how to verify replication with other domain controllers.
If this is caused by a failed DC, see EV100515 (Delete Failed DCs from Active Directory).
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated