Results 1 to 4 of 4

Thread: Forcing replication after tombstone cleanup

  1. #1
    Dave Guest

    Forcing replication after tombstone cleanup

    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

  2. #2
    Jorge de Almeida Pinto [MVP - DS] Guest

    Re: Forcing replication after tombstone cleanup

    read this first....
    http://blogs.dirteam.com/blogs/jorge...11/24/153.aspx
    http://blogs.dirteam.com/blogs/jorge...g-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@discussions.microsoft.com> wrote in message
    news:D2A426AF-E6EA-4125-9191-A8AFC80DC75F@microsoft.com...
    > 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



  3. #3
    Dave Guest

    Re: Forcing replication after tombstone cleanup

    Many thanks!

    Using the registry change cracked it. You have saved me a shedload of work
    with this, superb article and website. Thanks very much!

    Cheers!

    Dave
    :o)

    "Jorge de Almeida Pinto [MVP - DS]" wrote:

    > read this first....
    > http://blogs.dirteam.com/blogs/jorge...11/24/153.aspx
    > http://blogs.dirteam.com/blogs/jorge...g-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@discussions.microsoft.com> wrote in message
    > news:D2A426AF-E6EA-4125-9191-A8AFC80DC75F@microsoft.com...
    > > 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

    >
    >


  4. #4
    Jorge de Almeida Pinto [MVP - DS] Guest

    Re: Forcing replication after tombstone cleanup

    be very carefull with Lingering Objects and HOW you get rid of those. Just
    killing the DC (for removal and cleaning AD metadata and repromoting) is
    sometimes much safer than cleaning Lingering objects and reconnecting

    --

    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@discussions.microsoft.com> wrote in message
    news:6499352C-8160-4A34-AA28-2D2C56B6832C@microsoft.com...
    > Many thanks!
    >
    > Using the registry change cracked it. You have saved me a shedload of work
    > with this, superb article and website. Thanks very much!
    >
    > Cheers!
    >
    > Dave
    > :o)
    >
    > "Jorge de Almeida Pinto [MVP - DS]" wrote:
    >
    >> read this first....
    >> http://blogs.dirteam.com/blogs/jorge...11/24/153.aspx
    >> http://blogs.dirteam.com/blogs/jorge...g-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@discussions.microsoft.com> wrote in message
    >> news:D2A426AF-E6EA-4125-9191-A8AFC80DC75F@microsoft.com...
    >> > 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

    >>
    >>



Similar Threads

  1. NTDS Replication: How to remove a replication partner?
    By haritable in forum Small Business Server
    Replies: 3
    Last Post: 10-05-2012, 09:50 PM
  2. Forcing AD Replication in Windows Server 2008
    By Domw001 in forum Active Directory
    Replies: 4
    Last Post: 14-05-2009, 04:10 PM
  3. Forcing Replication
    By Bhuvan in forum Active Directory
    Replies: 3
    Last Post: 07-11-2008, 06:22 PM
  4. Recover or view tombstone.. is possible?
    By Andrea in forum Active Directory
    Replies: 4
    Last Post: 28-08-2008, 06:18 PM
  5. Tombstone error 8614 and garbage error 8606
    By bjude in forum Active Directory
    Replies: 1
    Last Post: 30-03-2007, 05:22 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •