|
| |||||||||
| Tags: 1864, ntds, replication |
Sponsored Links
New DC problem with event log NTDS Replication error 1864
Active Directory
 |
| | Thread Tools | Search this Thread |
|
| |||||||||
| Tags: 1864, ntds, replication |
|
| | Thread Tools | Search this Thread |
|
#1
20-01-2010
| |||
| |||
| Re: New DC problem with event log NTDS Replication error 1864
The GC is the DC MIS(192.168.1.1), and the WINS proxy is set to No. MIS: 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.  |
|
#2
20-01-2010
| |||
| |||
| Re: New DC problem with event log NTDS Replication error 1864
Hello Jason, What it M00S for a machine? Is that one removed from the domain some time ago? Check with the following article the AD database and cleanup old DCs from the domain: http://support.microsoft.com/kb/555846/en-us Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > The GC is the DC MIS(192.168.1.1), and the WINS proxy is set to No. > > MIS: > > 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. > |
|
#3
20-01-2010
| |||
| |||
| Re: New DC problem with event log NTDS Replication error 1864
"Jason Huang" <JasonHuang8888@hotmail.com> wrote in message news:uzvj8FbmKHA.5520@TK2MSFTNGP06.phx.gbl... > The GC is the DC MIS(192.168.1.1), and the WINS proxy is set to No. > > MIS: > > > 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. > > > > As Meinolf indicated, M00S has to be removed from the AD database. I also suggest to promote another DC into the v00s.mycom.com domain, and make it a GC. Ace |
|
#4
21-01-2010
| |||
| |||
| Re: New DC problem with event log NTDS Replication error 1864
The M00S is a Win2003 stand alone server, it was domoted long time ago. Thanks for your guys' help, I just deleted and cleaned the m00domain few minutes ago. It still has the result 8418 (0x20e2): 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. |
|
#5
21-01-2010
| |||
| |||
| Re: New DC problem with event log NTDS Replication error 1864
Hello Jason, Please check the following article: http://support.microsoft.com/kb/825782 http://support.microsoft.com/kb/307323 Are all DCs using SP2 and the latest available patches? Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > The M00S is a Win2003 stand alone server, it was domoted long time > ago. > Thanks for your guys' help, I just deleted and cleaned the m00domain > few > minutes ago. > It still has the result 8418 (0x20e2): > 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. > |
|
#6
21-01-2010
| |||
| |||
| New DC problem with event log NTDS Replication error 1864
You may also want to review below, this may assist as well. http://support.microsoft.com/kb/838179 -- Paul Bergson MVP - Directory Services MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, 2003, 2000 (Early Achiever), NT4 Microsoft's Thrive IT Pro of the Month - June 2009 http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message news:6cb2911dca108cc689833ea57c4@msnews.microsoft.com... > Hello Jason, > > Please check the following article: > http://support.microsoft.com/kb/825782 > > http://support.microsoft.com/kb/307323 > > Are all DCs using SP2 and the latest available patches? > > Best regards > > Meinolf Weber > Disclaimer: This posting is provided "AS IS" with no warranties, and > confers no rights. > ** Please do NOT email, only reply to Newsgroups > ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm > >> The M00S is a Win2003 stand alone server, it was domoted long time >> ago. >> Thanks for your guys' help, I just deleted and cleaned the m00domain >> few >> minutes ago. >> It still has the result 8418 (0x20e2): >> 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. >> > > |
|
|
| Thread Tools | Search this Thread |
| |
Similar Threads for: "New DC problem with event log NTDS Replication error 1864" | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Replication error on new DC after demoting old DC (Event 1411 Source:NTDS Replication) | Zaur Bahramov | Active Directory | 10 | 01-06-2008 05:14 PM |
| NTDS Rplication Event 1864 | Dennis | Active Directory | 10 | 26-11-2007 08:35 PM |
| event id error 1791 ntds replication | Junaid Mahomed | Active Directory | 2 | 13-04-2007 07:30 PM |
| Re: NTDS Rplication Event 1864 | Jorge de Almeida Pinto [MVP - DS] | Active Directory | 0 | 19-01-2007 12:44 AM |
| NTDS Replication, Event ID: 1864 | Edwin Delgado | Windows Server Help | 0 | 04-12-2005 07:34 AM |
