Re: NTDS Replication error 2042, despite increased tombstone lifetime



make a screenshot of the value and the event ID and post it

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Sune T. Tougaard" <sunemaster@xxxxxxxxx> wrote in message
news:1160038490.964021.16480@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks Jorge,

Sorry for the long posts, and I will investigate further per your
recommendations.

But just to make sure that i understand this correctly, and that i have
actually explained myself properly...

In this particular case, there are only two domain controllers in the
domain.
The tombstone lifetime was increased to 360 days.
This change was verified on both domain controllers, and they were
allowed to replicate for some days after the change.

Then one of the DCs was disconnected from the network and shipped to a
remote location.
After a few months (no where near 360 days), the server was brought
back online at the remote location, and they were allowed to replicate
once again, after a few DC account problems.
No 2042 error messages.

Then after a while (weeks) with replication between the servers, the
second DC was disconnected and shipped to the remote location.

After a few months (no where near 360 days), the second server was
brought back online, and gave the error message that i mention below,
right after being powered on.

What confuses me is this:
The error message states that the tombstone lifetime is only 60 days,
even though i increased it 360 days.
Checking the lifetime on the servers now, still shows the 360 days, so
where does the 60 days come from.

What IS the tombstone lifetime now?
If i cannot "trust" the 360 days setting that i made, then what else do
i have to do to get the system to believe me when i increase it?

Is the error message wrong in stating the 60 days, and can i therefore
disregard it?
The error message also states that replicaiton is stopped, but that
does not seem to be the case.
The "Allow Replication With Divergent and Corrupt Partner" registry key
is NOT set on any of the DCs.

Does the tombstone lifetime setting only apply to newly created objects
after the change, or everything?
I would guess, everything, but then, why the error message?

As said, I will investigate this, but would still like clarification on
the issue.

Thanks for your help and comments.
I really do appreciate your efforts.

--
/Sune



Jorge de Almeida Pinto [MVP - DS] wrote:
if you get that message, that means one of more DCs (in general) has not
replicated with another DC WITHIN the tombstone lifetime. Yes, it does
not
automatically mean you have lingering object, but chances are VERY HIGH
you
do have them.

Better investigate this!

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Sune T. Tougaard" <sunemaster@xxxxxxxxx> wrote in message
news:1159964046.111294.61220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks guys,

However, all of these articles discuss what to do when you experience
lingering objects (and why) or exceed the tombstone lifetime (or both,
of course).
Great articles, by the way.

That, however, is NOT my issue.
I do NOT see lingering objects (i think).
I did NOT exceed the tombstone lifetime, as this was increased to 360
days before disconnecting the DC.
Replication seems to continue succesfully a while after this event has
been logged.

At least replmon says that all replications occured succesfully.

Both DCs pass all dcdiag tests.

Reading the articles, the only thing i can think of is that the clocks
may have been skewed after one of the DCs had been disconnected for a
couple of months, but certainly not more than 360 days.

Therefore my questions:
- Should i worry about the error message?
- Even with the increased tombstone lifetime?

Comments?

Thanks.

--
/Sune


Jorge de Almeida Pinto [MVP - DS] wrote:
see:
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

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no
rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Sune T. Tougaard" <sunemaster@xxxxxxxxx> wrote in message
news:1159437655.072367.17960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi All,

Have seen this a couple of times, and would like to have some
comments
on the issue.

For a couple of AD setups, i've had to increase the tombstone
lifetime.
Doing this, has made a few issues show up.

What i believe that i have seen, is that, even if the tombstone
lifetime is increased to 360 days, the error:

Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042

Appears when a DC is reconnected after being disconnected more than
60
days.
The text in the error message also states that the tombstone
lifetime
is only 60 days, even though i checked all domain controllers for
the
increased lifetime before disconnecting.

The first time i saw it, i forced it to replicate with the registry
key
"Allow Replication With Divergent and Corrupt Partner".

The second time, i had a little more patience, and apparently it
seems
that replication picks up where it left as it's supposed to, and not
stopping replication as the error message states.

Is this expected behavior?
I think that the error message (the checking logic behind it) should
take into account, the increased tombstone lifetime.

Should i worry about the error message? Even with the increased
tombstone lifetime?

Comments?

Thanks.

--
/Sune





.