Results 1 to 7 of 7

Thread: NTDS Rplication Event 1864

  1. #1
    Join Date
    Jan 2005

    NTDS Rplication Event 1864


    We are running an Active Directory Domain with 7 DCs. From couple of days due to some unknown reason I keep getting NTDS Replication 1864 events. When we ran REPADMIN command, I found the following:

    b056d440-a755-488c-a013-244f994abd60 @ USN 16573 @ Time 2006-06-02
    93c84682-3247-4b59-a733-981ba5e97ef5 @ USN 13051 @ Time 2006-06-02
    corp\LostAndFoundConfig @ USN 12394 @ Time 2006-06-02
    Oakdale\HAUPDC01 @ USN 1586733 @ Time 2007-01-17
    Oakdale\ERODC01 @ USN 913426 @ Time 2007-01-17
    Oakdale\GRDC01 @ USN 3362295 @ Time 2007-01-17
    Oakdale\PCDC01 @ USN 1428596 @ Time 2007-01-17
    Oakdale\IT_PS @ USN 1538576 @ Time 2007-01-17
    Oakdale\CRODC01 @ USN 5598983 @ Time 2007-01-17
    Oakdale\OAKDC02 @ USN 1681252 @ Time 2007-01-17
    I tried searching some solution for this on Google as well as on Technet but dint found anything working . So can anyone of you please help me out of this?

  2. #2
    Join Date
    Sep 2005

    RE: NTDS Rplication Event 1864

    I’m sure that your first two entries are not creating the problem because they are gone since long ago from AD. So you don’t need to do anything for them. The only culprit entry I can see there is the following one:
    corp\LostAndFoundConfig @ USN 12394 @ Time 2006-06-02

    As it is showing up as a reference to lost and found container in output of /showvector. I haven’t seen this before. I think your NTDS settings object are in lost and found container under configuration partition. Also your repadmin is analyzing the parent of that object as lostandfounfconfig rather than original parent which was the servername. What you can do is use adsiedit and open the configuration container and expand the 'lostandfoundconfig' container. Once done, you will find an NTDS settings object from the long since departed DC. In case you want to know what DC this used to be for, then look at the lastknownparent attribute.

    Hope it helps.

  3. #3
    Join Date
    Jan 2005

    RE: NTDS Rplication Event 1864

    Thanks for the help friend. As you suggested i checked the container and found the object. I saw the lastknown attribute was not set hence i deleted the same. However i'm not able to dint out what exactly is kicking off the replication that causes those errors. I think they occur somewhere at midnight hence i'll check them later.

    As far as other 2 entries are concerned i would like to know whether they will coincide with server's 2 deleted entries which is showing up in repmon? If yes, then how can delete them as well?

  4. #4
    Join Date
    Jan 2005

    RE: NTDS Rplication Event 1864

    Hey the problem exists still in the event log. I can still see Event ID 1864. Also when i checked the repadmin /showve, again those 3 entries are visible.

    Any other ideas or suggestions? What to do now?

  5. #5
    Join Date
    Jul 2004

    RE: NTDS Rplication Event 1864

    you can force repl by running

    repadmin /syncall /A /e /P

  6. #6
    Join Date
    Jan 2005

    RE: NTDS Rplication Event 1864


    Thanks for your help. It is/was greatly appreciated.


  7. #7
    Join Date
    Nov 2007

    Error Log 1925

    The attempt to establish a replication link for the following writable directory partition failed.

    Directory partition:
    CN=Configuration,DC=hosur,DC=tvsmotor,DC=co,DC=in Source domain controller:
    CN=NTDS Settings,CN=TVSMINDO,CN=Servers,CN=Default-First Site-Name,CN=Sites,CN=Configuration,DC=hosur,DC=tvsmotor,DC=co,DC=in
    Source domain controller address: Intersite transport (if any):

    This domain controller will be unable to replicate with the source domain controller until this problem is corrected.

    User Action
    Verify if the source domain controller is accessible or network connectivity is available.

    Additional Data

Similar Threads

  1. Event ID 1168 NTDS General
    By hatred in forum Active Directory
    Replies: 4
    Last Post: 17-01-2014, 10:36 AM
  2. New DC problem with event log NTDS Replication error 1864
    By Elettra in forum Active Directory
    Replies: 4
    Last Post: 21-01-2010, 02:34 PM
  3. Warning NTDS ISAM Event ID 507 and Event id 508
    By Tahseen Shahzad in forum Active Directory
    Replies: 7
    Last Post: 27-04-2009, 12:28 AM
  4. NTDS Replication, Event ID: 1864
    By Edwin Delgado in forum Windows Server Help
    Replies: 0
    Last Post: 04-12-2005, 07:34 AM
  5. event ID: 1083 and 1955 ntds replication
    By pain112 in forum Active Directory
    Replies: 8
    Last Post: 16-09-2005, 02:44 AM

Tags for this Thread


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
Page generated in 1,696,374,325.30282 seconds with 17 queries