Re: Forcing replication after tombstone cleanup
- From: "Jorge de Almeida Pinto [MVP - DS]" <SubstituteThisWithMyFullNameSeparatedByDots@xxxxxxxxx>
- Date: Wed, 11 Jun 2008 18:42:56 +0200
read this first....
http://blogs.dirteam.com/blogs/jorge/archive/2005/11/24/153.aspx
http://blogs.dirteam.com/blogs/jorge/archive/2006/05/08/Lingering-objects.aspx
after reading... what are your questions tha remain?
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Identity & Access - Directory Services #
BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test ANY suggestion in a test environment before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Dave" <Dave@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:D2A426AF-E6EA-4125-9191-A8AFC80DC75F@xxxxxxxxxxxxxxxx
Hi all,
Does anyone have any experience of getting site replication working again
once two DC's have exceeded their tombstone life?
I have inherited a network where the replication was a real mess and several
servers were not replicating properly. I have set this all up now and got
everything working except for one site as it had been disconnected so long it
had exceeded it's tombstone life and so would not replicate. All servers are
running 2003.
I have run repadmin /removelingeringobjects to sync the two AD's again and
have got replication working one way, ie, from HQ to Site1 however I can't
get it to replicate the other way. I get;
"The following error occurred during the attempt to synchronize naming
content siteaddress.co.uk from domain controller SITE1 to domain controller
HQ:
The naming context is in the process of being removed or is not replicated
from the specified server."
Also if I run repadmin /showreps I get:
"Source: Site\Server
******* 1 CONSECUTIVE FAILURES since 2008-06-11 15:18:02
Last error: 8614 (0x21a6):
Can't retrieve message string 8614 (0x21a6), error 1815."
Error 8614 appears to be linked to the tombstone life so even though I have
run repadmin /removelingeringobjects it still will not play ball.
I tried the registry key HKLM\System\CurrentControlSet\NTDS\Parameters\Allow
Replication With Divergent and Corrupt Partner, but that didn't allow it to
work either.
Anyone got any idea how I force replication in this case? I am happy there
are no lingering objects remaining so I don't believe there should be an
issue with these replicating again if only I could get it to happen.
Many thanks
Dave
.
- Follow-Ups:
- Prev by Date: Re: Active Direcory and Domain name
- Next by Date: Re: GPO to Disable a Computer at a Future Date
- Previous by thread: Home directory - Windows\system folders appear?
- Next by thread: Re: Forcing replication after tombstone cleanup
- Index(es):
Relevant Pages
|
