event id 1864 ntds replication

Posted on 2009-04-21
Last Modified: 2013-12-05
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
Computer:      NASNDC01
This is the replication status for the following directory partition on the local domain controller.
Directory partition:
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:
More than a week:
More than one month:
More than two months:
More than a tombstone lifetime:
Tombstone lifetime (days):
 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
Question by:ruizsae1
    1 Comment
    LVL 5

    Accepted Solution

    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.

    Featured Post

    Want to promote your upcoming event?

    Is your company attending an event or exhibiting at a trade show soon? Are you speaking at a conference? Spread the word by using a promotional banner in your email signature. This will ensure your organization’s most important contacts are in the know.

    Join & Write a Comment

    Have you considered what group policies are backwards and forwards compatible? Windows Active Directory servers and clients use group policy templates to deploy sets of policies within your domain. But, there is a catch to deploying policies. The…
    When you upgrade from Windows 8 to 8.1 or to Windows 10 or if you are like me you are on the Insider Program you may find yourself with many 450MB recovery partitions.  With a traditional disk that may not be a problem but with relatively smaller SS…
    This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
    Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

    728 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now