Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
event id: 1863 and 1864
- Thread starter murrayw
- Start date
Event ID: 1863
Source NTDS Replication
Type Error
Description This is the replication status for the following directory partition on the local domain controller.
Directory partition:
DC=ForestDnsZonesDC=atlDC=local
The local domain controller has not received replication information from a number of domain controllers within the configured latency interval.
Latency Interval (Hours): <value>
Number of domain controllers in all sites: <value>
Number of domain controllers in this site: <value>
The latency interval can be modified with the following registry key.
Registry Key: "HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator" latency error interval (hours)
To identify the domain controllers by name install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".
______________________________________________
Event ID: 1864
Source NTDS Replication
Type Error
Description This is the replication status for the following directory partition on the local domain controller.
Directory partition: CN=Schema,CN=Configuration,DC=uu,DC=local
The local domain controller has not recently received replication information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals.
More than 24 hours: <value>
More than a week: <value>
More than one month: <value>
More than two months: <value>
More than a tombstone lifetime: <value>
Tombstone lifetime (days): 60
Domain controllers that do not replicate in a timely manner may encounter errors. It 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 domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".
_
From a newsgroup post: "This error can occur if the DC has been offline for more than 60 days, has not replicated with another DC for more than 60 days or if the time on your servers is not set correctly. This server has therefore passed the tombstone lifetime of 60 days and will need to be reinstalled. You should try running dcpromo with the /forceremoval switch and then do a metadata cleanup on AD to remove all traces of that DC. Once this is done, it can be re-promoted if desired. See Q216993 for details on the Active Directory backup useful life.
See Q332199 for details on running the “dcpromo /forceremoval” command.
See Q216498 for details on how to remove data in Active Directory after an unsuccessful domain controller demotion".
courtesy of
are both on same subnet, both in same site?
has anything happened to one or other of your DCs?
ARE they replicating?
Aftertaf
if its not broken, fix it anyway - with luck you might break it and have an excuse
Source NTDS Replication
Type Error
Description This is the replication status for the following directory partition on the local domain controller.
Directory partition:
DC=ForestDnsZonesDC=atlDC=local
The local domain controller has not received replication information from a number of domain controllers within the configured latency interval.
Latency Interval (Hours): <value>
Number of domain controllers in all sites: <value>
Number of domain controllers in this site: <value>
The latency interval can be modified with the following registry key.
Registry Key: "HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Replicator" latency error interval (hours)
To identify the domain controllers by name install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".
______________________________________________
Event ID: 1864
Source NTDS Replication
Type Error
Description This is the replication status for the following directory partition on the local domain controller.
Directory partition: CN=Schema,CN=Configuration,DC=uu,DC=local
The local domain controller has not recently received replication information from a number of domain controllers. The count of domain controllers is shown, divided into the following intervals.
More than 24 hours: <value>
More than a week: <value>
More than one month: <value>
More than two months: <value>
More than a tombstone lifetime: <value>
Tombstone lifetime (days): 60
Domain controllers that do not replicate in a timely manner may encounter errors. It 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 domain controllers by name, install the support tools included on the installation CD and run dcdiag.exe. You can also use the support tool repadmin.exe to display the replication latencies of the domain controllers in the forest. The command is "repadmin /showvector /latency <partition-dn>".
_
From a newsgroup post: "This error can occur if the DC has been offline for more than 60 days, has not replicated with another DC for more than 60 days or if the time on your servers is not set correctly. This server has therefore passed the tombstone lifetime of 60 days and will need to be reinstalled. You should try running dcpromo with the /forceremoval switch and then do a metadata cleanup on AD to remove all traces of that DC. Once this is done, it can be re-promoted if desired. See Q216993 for details on the Active Directory backup useful life.
See Q332199 for details on running the “dcpromo /forceremoval” command.
See Q216498 for details on how to remove data in Active Directory after an unsuccessful domain controller demotion".
courtesy of
are both on same subnet, both in same site?
has anything happened to one or other of your DCs?
ARE they replicating?
Aftertaf
if its not broken, fix it anyway - with luck you might break it and have an excuse
- Status
Similar threads
