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

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Meinolf,

As on all 4 servers has the same events right now. Can I try to restore the
system state backup of one of servers and then move FSMO roles to it and then
demote all other DC and cleanup AD database ? Can I do this?

May be I will look stupid but I don't know this. Can you please also tell me
how to demote DC and cleanup Acitve directory dababase and again how to
promote the same DC?

With best regards,
Hemal

"Meinolf Weber" wrote:

Hello Hemal,

If you have at least one of them on an actual state and it is maybe not tombstoned,
check also the event viewer for the errors, then you can use the functioning
one as the "master", move all FSMO roles to it and then you have to demote
all other DC's and cleanup AD database form all old entries of them and start
promoting them again.

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


Hi Meinolf,

Can you please tell me where should I start to resolve this issue?

Thanks for you help so far...

Hemal

"Hemal" wrote:

Hi Meinolf,

Thanks for your reply. I got the output of netdiag /v on HPserver in
text file as you recommended but as this post has limit of 30000 tax
size and the output is 114496 I may have to send it to you in diff
posts or whatever way you want.

I also have the same problems about the tombstone lifetime on all
other servers. Below is the output of repadmin /showrepl command on
dellserver:

{repadmin running command /showrepl against server localhost

Default-First-Site-Name\DELLSERVER

DC Options: IS_GC

Site Options: (none)

DC object GUID: b8141bfc-46fa-4345-884c-34be3d92f968

DC invocationID: 7a983dc9-2f2c-4189-ae20-23c55bf6c9ef

==== INBOUND NEIGHBORS ======================================

DC=kbgca,DC=local

Default-First-Site-Name\MAINSERVER via RPC

DC object GUID: 220e92ee-bef1-4162-b077-81ff0a346f81

Last attempt @ 2008-10-16 09:30: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.

821 consecutive failure(s).

Last success @ 2008-06-25 10:37:51.

Default-First-Site-Name\IBMSERVER via RPC

DC object GUID: 382cdb4e-7b9c-4a33-a252-4c11bf6117e5

Last attempt @ 2008-10-16 09:31:26 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.

934 consecutive failure(s).

Last success @ 2008-06-25 10:40:08.

Default-First-Site-Name\HPSERVER via RPC

DC object GUID: 009fa382-6fcc-46d1-b3db-7ae24701415e

Last attempt @ 2008-10-16 09:34:23 was successful.

CN=Configuration,DC=kbgca,DC=local

Default-First-Site-Name\IBMSERVER via RPC

DC object GUID: 382cdb4e-7b9c-4a33-a252-4c11bf6117e5

Last attempt @ 2008-10-16 09:26:25 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.

286 consecutive failure(s).

Last success @ 2008-06-25 01:19:57.

Default-First-Site-Name\MAINSERVER via RPC

DC object GUID: 220e92ee-bef1-4162-b077-81ff0a346f81

Last attempt @ 2008-10-16 09:26:48 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.

291 consecutive failure(s).

Last success @ 2008-06-25 01:19:51.

CN=Schema,CN=Configuration,DC=kbgca,DC=local

Default-First-Site-Name\IBMSERVER via RPC

DC object GUID: 382cdb4e-7b9c-4a33-a252-4c11bf6117e5

Last attempt @ 2008-10-16 08:48:50 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.

121 consecutive failure(s).

Last success @ 2008-06-25 01:14:17.

Default-First-Site-Name\MAINSERVER via RPC

DC object GUID: 220e92ee-bef1-4162-b077-81ff0a346f81

Last attempt @ 2008-10-16 08:48:50 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.

121 consecutive failure(s).

Last success @ 2008-06-25 01:14:17.

Source: Default-First-Site-Name\HPSERVER

******* 1 CONSECUTIVE FAILURES since 2008-10-16 09:26:53

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.

Naming Context: CN=Schema,CN=Configuration,DC=kbgca,DC=local

Source: Default-First-Site-Name\HPSERVER

******* WARNING: KCC could not add this REPLICA LINK due to error.

Naming Context: CN=Configuration,DC=kbgca,DC=local

Source: Default-First-Site-Name\HPSERVER

******* WARNING: KCC could not add this REPLICA LINK due to error.

Source: Default-First-Site-Name\MAINSERVER

******* 818 CONSECUTIVE FAILURES since 2008-06-25 10:37:51

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.

Source: Default-First-Site-Name\IBMSERVER

******* 931 CONSECUTIVE FAILURES since 2008-06-25 10:40:08

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.}

I will try to implement the things you suggest for RRAS, DNS.

Let me know.

Best regards,
Hemal



.

Relevant Pages