Re: Event id 2042 /2041 (Directory service) + 12292/11 (VSS)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi Meinolf,

Thanks for your reply. I didn't follow the steps in the event id as I was
not sure from where I have to start? Now I will try to follow the links you
sent and try to see if it can fix this NTDS replication message.

Thank you again and I will post the outcome once it will be done.

With best regards,
Hemal

"Meinolf Weber" wrote:

Hello Hemal,

Your biggest problem is this which has to be solved ASAP:
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042
Date: 10/15/2008
Time: 10:18:30 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DELLSERVER
Description:
It has been too long since this machine last replicated with the named
source machine. The time between replications with this source has exceeded
the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two
machine's views of deleted objects may now be different. The source machine
may still have copies of objects that have been deleted (and garbage
collected) on this machine. If they were allowed to replicate, the source
machine might return objects which have already been deleted.
Time of last successful replication:
2008-06-25 01:26:15
Invocation ID of source:
07b0f6c8-f6b8-07b0-0100-000000000000
Name of source:
382cdb4e-7b9c-4a33-a252-4c11bf6117e5._msdcs.kbgca.local
Tombstone lifetime (days):
60


You have a replication problem between your DC's, they have not replicated
over the tombstone lifetime. Did you follow the steps in the event id?

See also here:
http://technet.microsoft.com/en-us/library/cc738415.aspx

http://technet.microsoft.com/en-us/library/cc757610.aspx

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

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


Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042
Date: 10/15/2008
Time: 10:18:30 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DELLSERVER
Description:
It has been too long since this machine last replicated with the named
source machine. The time between replications with this source has
exceeded
the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two
machine's views of deleted objects may now be different. The source
machine
may still have copies of objects that have been deleted (and garbage
collected) on this machine. If they were allowed to replicate, the
source
machine might return objects which have already been deleted.
Time of last successful replication:
2008-06-25 01:26:15



.

Relevant Pages

  • Re: NTDS Replication error 2042, despite increased tombstone lifetime
    ... # Jorge de Almeida Pinto # MVP Windows Server - Directory Services ... The tombstone lifetime was increased to 360 days. ... The error message states that the tombstone lifetime is only 60 days, ... The "Allow Replication With Divergent and Corrupt Partner" registry key ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDS Replication error 2042, despite increased tombstone lifetime
    ... The tombstone lifetime was increased to 360 days. ... After a few months, the server was brought ... The error message states that the tombstone lifetime is only 60 days, ... The "Allow Replication With Divergent and Corrupt Partner" registry key ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDS Replication
    ... This latency is over the Tombstone Lifetime of 60 ... The replication generated an error: ... Starting test: CrossRefValidation ... Domain controllers that do not replicate in a timely manner may ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDS Replication error 2042, despite increased tombstone lifetime
    ... replicated with another DC WITHIN the tombstone lifetime. ... Replication seems to continue succesfully a while after this event has ... Both DCs pass all dcdiag tests. ... The text in the error message also states that the tombstone lifetime ...
    (microsoft.public.windows.server.active_directory)
  • Re: NTDS Replication error 2042, despite increased tombstone lifetime
    ... BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx ... For a couple of AD setups, i've had to increase the tombstone lifetime. ... Event Source: NTDS Replication ... The text in the error message also states that the tombstone lifetime ...
    (microsoft.public.windows.server.active_directory)