Event ID: 1863 Source: NTDS Replication

Event ID/Source search

Keyword search

Example: Windows cannot unload your registry file

EvLog Event Log Analyzer

Sample report

Advanced filtering

Direct links to www.eventid.net

Email notifications

Scheduled reporting

Free for subscribers

EventReader Event Viewer

Sample report

Custom views/filters

Servers list, organized in groups

Integration with EventID.Net

Consolidated view for all logs

Free for subscribers

Event ID: 1863 Source: NTDS Replication

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>".

English: Request a translation of the event description in plain English.

Comments:
EventID.Net
This event may be an indication that the Active Directory may contain lingering objects (objects that are deleted from the Active Directory directory service when the domain controller is offline). These can occur if a domain controller does not replicate for an interval of time that is longer than the tombstone lifetime (TSL). See ME910205 for more information about lingering objects and how to remove them.

If you attempt a domain controller demotion and for some reason it fails, ME216498 provides details on how to remove the server manually.
Click if the comment is good!

^{x
6}

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

Feedback: Send comments or solutions - Notify me when updated

Printer friendly