locked
Event iD 1864: repadmin /showrepl is OK but unable to replicate directory partitions RRS feed

  • Question

  • hi all, I have two Domain Controllers (w2008 core, running W2008 functional level) in a child domain called test.domain.com and the parent domain is domain.com.  About 3 weeks ago, I begin receiving the following error (see below for full error message) on Directory partitions: CN=Configuration,DC=domain,DC=com;, CN=Schema,CN=Configuration,DC=domain,DC=com,DC=ForestDnsZones,DC=domain,DC=com,DC=domain,DC=com

    When I run repadmin /showrepl on both domain controllers in test.domain.com, it checks back clean.  I'm at a lost on why its not able to replicate even though repadmin /showrepl is good...any ideas where I can look to resolve this issue?


    Log Name:      Directory Service
    Source:        Microsoft-Windows-ActiveDirectory_DomainService
    Date:          6/16/2009 3:00:17 PM
    Event ID:      1864
    Task Category: Replication
    Level:         Error
    Keywords:      Classic
    User:          ANONYMOUS LOGON
    Computer:      DC1
    Description:
    This is the replication status for the following directory partition on this directory server.
     
    Directory partition:
    CN=Configuration,DC=domain,DC=com
     
    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:
    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
     
    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>".
    Wednesday, June 17, 2009 12:12 AM

Answers

  • I resolved the issue.

    if I run repadmin /test:replication  , I could see the troubled domain controller.

    I should be good now, thanks everyone for your responses.
    • Marked as answer by clay28 Thursday, June 18, 2009 8:09 PM
    Thursday, June 18, 2009 8:09 PM

All replies

  • Have you checked the replication between the two domains?

    Can you post the output of

    repadmin /showrepl *

    hth
    Marcin
    Wednesday, June 17, 2009 12:43 AM
  • Hello,

    additional to the repadmin /showrepl please post an unedited dcdiag /v from both DCs.
    Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
    Wednesday, June 17, 2009 9:08 AM
  • thanks for your responses.  its going to take me time to prune those two outputs.  give me a day or two and I try to post it all.  repadmin /showrepl * is going to be big.
    • Marked as answer by clay28 Thursday, June 18, 2009 8:08 PM
    • Unmarked as answer by clay28 Thursday, June 18, 2009 8:08 PM
    Wednesday, June 17, 2009 11:47 PM
  • I resolved the issue.

    if I run repadmin /test:replication  , I could see the troubled domain controller.

    I should be good now, thanks everyone for your responses.
    • Marked as answer by clay28 Thursday, June 18, 2009 8:09 PM
    Thursday, June 18, 2009 8:09 PM
  • It should be DCDIAG /test:replication instead. There isn't such command as repadmin /test:replication.
    Friday, November 23, 2012 8:06 AM
  • ...and you are missing an 's', it is:

    dcdiag /test:replications

    • Proposed as answer by A.Hultgren Monday, June 1, 2020 6:37 AM
    Monday, April 21, 2014 1:04 PM