Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1170
  • Last Modified:

event id 1864 ntds replication

I am getting this error on my domain controller.

Event Type:      Error
Event Source:      NTDS Replication
Event Category:      Replication
Event ID:      1864
Date:            4/20/2009
Time:            5:52:41 PM
User:            NT AUTHORITY\ANONYMOUS LOGON
Computer:      NASNDC01
Description:
This is the replication status for the following directory partition on the local domain controller.
 
Directory partition:
CN=Schema,CN=Configuration,DC=universalleaf,DC=com
 
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:
1
More than a week:
1
More than one month:
0
More than two months:
0
More than a tombstone lifetime:
0
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>".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
0
ruizsae1
Asked:
ruizsae1
1 Solution
 
mail2prabirCommented:
more concern is the reason a DC has not replicated in over 60 days. You've either got a network probelm (surely you'd know about this), have two DCs each side of a firewall (you should check the logs, the KCC/ ISTG will be logging loads of warnings) or, more than likely, you've got DNS problems.

You'll need to run the following tests and read through the results thouraghly (all performed from the command prompt):

dcdiag /v /e /c
netdiag /v

also check the Directory Services logs on all your DCs and run replmon.exe (Replication Monitor) to see what's going on.

in case one of the server invloved in replication is indeed uncleanly removed, clean the associated metadata using ntdsutil command.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now