Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Active Directory
New DC problem with event log NTDS Replication error 1864 New DC problem with event log NTDS Replication error 1864
Become a Member!
Forgot your username/password?
Tags Active Topics RSS Search Mark Forums Read SiteMap

Tags: , ,

Sponsored Links


New DC problem with event log NTDS Replication error 1864

Active Directory


Reply
 
Thread Tools Search this Thread
  #1  
Old 20-01-2010
Member
  
Join Date: Apr 2005
Posts: 71
Re: New DC problem with event log NTDS Replication error 1864
Sponsored Links
As my title says itself, the Event Viewer of my Windows Server is showing up “error 1864”. It keeps on generating the same. I don’t know why. It started three days ago. The GC is the DC MIS(192.168.1.1), and the WINS proxy is set to No. Here is the detailed list:

Quote:
repadmin running command /showrepl against server localhost

Default-First-Site-Name\MIS
DC Options: IS_GC
Site Options: (none)
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e

==== INBOUND NEIGHBORS ======================================

DC=MyCom,DC=com
Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-20 17:03:14 was successful.

CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 16:55:08 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper
33165 consecutive failure(s).
Last success @ 1983-06-18 18:17:20.
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-20 16:55:08 was delayed for a normal reason,
result 8418 (0x20e2):
The replication operation failed because of a schema mismatch between
the servers involved

Last success @ 2010-01-19 10:55:12.
Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-20 16:55:08 was successful.



CN=Schema,CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-20 16:55:08 was successful.
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 16:55:08 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper

15968 consecutive failure(s).
Last success @ 1983-06-18 17:47:59.
Default-First-Site-Name\SUN via RPC

DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-20 16:55:08 was successful.


DC=m00domain,DC=MyCom,DC=com
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 16:55:08 failed, result 1256 (0x4e8):
The remote system is not available. For information about
network troubleshooting, see Windows Help.

18280 consecutive failure(s).
Last success @ 1983-06-18 17:52:27.


DC=V00Domain,DC=MyCom,DC=com
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-20 16:55:08 was delayed for a normal reason,
result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved

Last success @ 2010-01-19 10:55:12.

Source: Default-First-Site-Name\M00S

******* 33165 CONSECUTIVE FAILURES since 1983-06-18 18:17:20

Last error: 1256 (0x4e8):

The remote system is not available. For information about
network troubleshooting, see Windows Help.


SUN:


repadmin running command /showrepl against server localhost



Default-First-Site-Name\SUN
DC Options: (none)
Site Options: (none)
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
DC invocationID: 33b94c6f-8a5a-4ad5-9890-cb2336edb937


==== INBOUND NEIGHBORS ======================================



DC=MyCom,DC=com

Default-First-Site-Name\MIS via RPC

DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 17:12:22 was successful.


CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\MIS via RPC
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 16:49:14 was successful.


CN=Schema,CN=Configuration,DC=MyCom,DC=com

Default-First-Site-Name\MIS via RPC
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 16:49:14 was successful.
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-20 16:49:14 was successful.



Source: Default-First-Site-Name\V00S

******* 1 CONSECUTIVE FAILURES since 2010-01-20 17:09:15

Last error: 8418 (0x20e2):
The replication operation failed because of a schema mismatch
between
the servers involved


Naming Context: CN=Configuration,DC=MyCom,DC=com
Source: Default-First-Site-Name\V00S

******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: Default-First-Site-Name\M00S

******* 56 CONSECUTIVE FAILURES since 2010-01-20 03:24:10

Last error: 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper


Naming Context: CN=Schema,CN=Configuration,DC=MyCom,DC=com
Source: Default-First-Site-Name\M00S

******* WARNING: KCC could not add this REPLICA LINK due to error.


Naming Context: CN=Configuration,DC=MyCom,DC=com
Source: Default-First-Site-Name\M00S

******* WARNING: KCC could not add this REPLICA LINK due to error.




V00S:
repadmin running command /showrepl against server localhost

Default-First-Site-Name\V00S
DC Options: (none)
Site Options: (none)
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
DC invocationID: 69bbf530-7664-4463-90d0-718a1e676213


==== INBOUND NEIGHBORS ======================================


CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 08:59:52 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint maper
100930 consecutive failure(s).
Last success @ 2005-04-25 16:26:28.
Default-First-Site-Name\MIS via RPC
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 09:15:38 failed, result 8614 (0x21a6):
The Active Directory cannot replicate with this server because the time
since the last replication with this server has exceeded the tombstone
lifetime.

39408 consecutive failure(s).

Last success @ 2005-04-26 13:49:25.

CN=Schema,CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\M00S via RPC
DC object GUID: 9060e0a7-7848-4af0-937d-368030aa96c6
Last attempt @ 2010-01-20 08:59:52 failed, result 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper
39347 consecutive failure(s).
Last success @ 2005-04-25 15:54:14.
Default-First-Site-Name\MIS via RPC
DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
Last attempt @ 2010-01-20 08:59:52 failed, result 8614 (0x21a6):


The Active Directory cannot replicate with this server because the time
since the last replication with this server has exceeded the tombstone
lifetime.
39341 consecutive failure(s).
Last success @ 2005-04-26 12:53:57.


Source: Default-First-Site-Name\M00S

******* 100930 CONSECUTIVE FAILURES since 2005-04-25 16:26:28

Last error: 1753 (0x6d9):
There are no more endpoints available from the endpoint mapper


Source: Default-First-Site-Name\MIS
******* 39408 CONSECUTIVE FAILURES since 2005-04-26 13:49:25
Last error: 8614 (0x21a6):
The Active Directory cannot replicate with this server because the time
since the last replication with this server has exceeded the tombstone
lifetime.

Reply With Quote
  #2  
Old 20-01-2010
Member
  
Join Date: Sep 2004
Posts: 133
Re: New DC problem with event log NTDS Replication error 1864
First of all i'm not able understand what exactly is M00S for a machine? Was it removed from your Domain earlier sometime?

Until you reply, i found an KB Article which will help you to remove completely orphaned Domain Controller and checking AD database. Have a look here.
http://support.microsoft.com/kb/555846/en-us
Reply With Quote
  #3  
Old 20-01-2010
Member
  
Join Date: Jul 2004
Posts: 135
Re: New DC problem with event log NTDS Replication error 1864
Even i think the M00S has to be removed from your AD database. Apart from the suggestions provided in that knowledge base you should also try promoting another Domain Controller into the v00s.mycom.com domain, and make it a GC.

It will help you out for sure.
Reply With Quote
  #4  
Old 21-01-2010
Member
  
Join Date: Apr 2005
Posts: 71
Re: New DC problem with event log NTDS Replication error 1864
I really appreciate all your helps guys. Yes, the M00S which is Win2003 stand alone server was removed about a year ago. I wasn't aware it is going to impact so much. Anyways, i have just deleted and cleaned the m00domain but still it is showing up an error "8418 (0x20e2)"

Quote:
The replication operation failed because of a schema mismatch between
the servers involved.

repadmin running command /showrepl against server localhost

Default-First-Site-Name\MIS
DC Options: IS_GC
Site Options: (none)

DC object GUID: 79a17049-d367-4f70-a060-9c199120ac3e
DC invocationID: 79a17049-d367-4f70-a060-9c199120ac3e


==== INBOUND NEIGHBORS ======================================


DC=etc,DC=org,DC=tw

Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-21 16:41:35 was successful.

CN=Configuration,DC=MyCom,DC=com
Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-21 16:41:28 was delayed for a normal reason,
result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved.

Last success @ 2010-01-19 10:55:12.
Default-First-Site-Name\SUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-21 16:45:51 was successful.


CN=Schema,CN=Configuration,DC=MyCom,DC=com

Default-First-Site-Name\V00S via RPC
DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-21 15:55:08 was successful.
Default-First-Site-Name\ETCSUN via RPC
DC object GUID: 6f2367b5-20a6-4038-843e-495979755925
Last attempt @ 2010-01-21 15:55:08 was successful.


DC=V00Domain,DC=MyCom,DC=com
Default-First-Site-Name\V00S via RPC

DC object GUID: 478c54c3-eb44-41e5-97d6-2011679a7e48
Last attempt @ 2010-01-21 16:42:02 was delayed for a normal reason,
result 8418 (0x20e2):

The replication operation failed because of a schema mismatch between
the servers involved.

Last success @ 2010-01-19 10:55:12.

Now what?
Reply With Quote
  #5  
Old 21-01-2010
Viceman's Avatar
Member
  
Join Date: Oct 2004
Posts: 1,339
Re: New DC problem with event log NTDS Replication error 1864
You need this. Just follow the solutions provided in both of these Microsoft Articles:

Replication of the Partial Attribute Set on a Global Catalog Server Does Not Complete: http://support.microsoft.com/kb/825782

And

Active Directory replication delayed when indexed attributes rebuilt during schema upgrade: http://support.microsoft.com/kb/307323
Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Active Directory

« Multiple domain controllers on same network, are all the same?    AD health check and cleanup »

Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "New DC problem with event log NTDS Replication error 1864"
Thread Thread Starter Forum Replies Last Post
NTDS Replication Event ID 1083/1955 and account lockouts Vic Active Directory 4 14-05-2009 02:20 PM
NTDS Rplication Event 1864 Ain'tSoBad Active Directory 6 26-11-2007 11:23 AM
NTDS Replication event 2023 error 8589 Mr Major Thorburn Active Directory 28 26-05-2006 02:37 PM
NTDS Replication, Event ID: 1864 Edwin Delgado Windows Server Help 0 04-12-2005 06:34 AM
event ID: 1083 and 1955 ntds replication pain112 Active Directory 8 16-09-2005 02:44 AM


All times are GMT +5.5. The time now is 10:46 PM.

Contact Us - TechArena - Privacy Statement -