• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 23066
  • Last Modified:

How do you fix AD Replication when a server has exceeded the Tombstone lifetime?

Recently, I just turned 2 of my 3 domain controller servers back on after being off for quite a while.  Each one is configured to replicate AD from one to another one.  However when the replication process is started I get a exceeded tombstone lifetime error.  The error says: "The AD cannot replicate with this server because the lifetime since the last replication with this server has exceeded the tombstone liftime."
How do I change this so that all three will replicate correctly?  Is it a matter of changing the tombstone lifetime or is there a way that I can re-sync all of my servers with my primary domain controller?  I did try the command repadmin /replicate and other switches and also the command dcdiag.  Those did not help, they only pretty much gave me the same information that I am giving you.

If anyone has any suggestions I would love to hear them.  Thanks!
0
GFCU
Asked:
GFCU
  • 7
  • 4
  • 2
  • +2
1 Solution
 
Jay_Jay70Commented:
from everything i have seen, you are stuck, you are going to have to kill those DC's and then clean the rest of your AD.....and then rebuild them and bring them back in...
0
 
MSE-dwellsCommented:
There is a way to resolve this by tweaking each DC such that it ignores the tombstone lifetime.  I really don't advise it though since it will result in any number of inconsistencies in the forest that are oftentimes much more difficult to remedy than your current situation.  Assuming the DCs you mention are indeed limited in number (you said 2 or 3 and that qualifies and they have been turned off vs. used at some other location and therefore in possession of valid data), I'd suggest you run -

DCpromo /forceremoval

... on each recently-switched-on-DC in turn and then repromote the resulting non-domain affiliated server back into the forest (this, of course, assumes other DCs remain from which to source any and all partitions/domains within your forest).

Note - increasing your tombstone lifetime won't help here.

PS - in case you missed it, you posted in the MS-DOS forum :0)
0
Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

 
GFCUAuthor Commented:
Does this still stand true for the Windows Server 2003 operating system too?  and not just the server 2000 os?
0
 
MSE-dwellsCommented:
Does what stand-true?
0
 
GFCUAuthor Commented:
My question is, does this apply also to the server 2003 operating system.  not just the server 2000 os.
0
 
GFCUAuthor Commented:
The section named "Correct Response to Any Outdated Server Running Windows 2000 Server" is the section that is relevent to me.  The only thing is that I am running Windows Server 2003, NOT Windows Server 2000.
0
 
Jay_Jay70Commented:
same rules apply
0
 
MSE-dwellsCommented:
Nod, everything applies.  In fact, it's more applicable to 2003 than to 2000.
0
 
GFCUAuthor Commented:
Either way, this is correct for this version???
0
 
MSE-dwellsCommented:
Yes.
0
 
GFCUAuthor Commented:
Thanks for the info, this is a work in progress.  I will keep you updated.  Thanks!
0
 
GFCUAuthor Commented:
I reloaded a new server with ad and started replication from new.  Thanks for the help.
0
 
prointegCommented:
Windows 2003 Domain controllers (4)
Date&Time got whacked out by VMware's network time service changing domain controller date & time settings to different times and months.  Don't ask but I've now seen this happen at 4 client sites running ESX 3.5 with MS domain controllers.

The servers got completely out of sync and replication halted... of course.

I had to rebuilt the security connection between one domain controller and PDC emulator using netdom reset password utility but I think the real fix was setting the registry entry using the article below that "Allow Replication With Divergent and Corrupt Partner".

I ran repadmin to remove lingering objects which wasn't too hard once you grasped the syntax.  Just use repadmin /showrepl to find the GUID and directory partition object.  Mine was: CN=Configuration,DC=yourmomma,DC=com

Reboot the domain controllers and try a manual replication using AD sites & services MMC tool.

Good luck and I hope maybe I can spark some ideas you weren't seeing at first.

Someday someone will right an AD repair tool for windows that dows all this but until then....

Adam
Professional Integrations LLC
www.professionalintegrations.com



http://technet2.microsoft.com/windowsserver/en/library/4f504103-1a16-41e1-853a-c68b77bf3f7e1033.mspx?mfr=true
0

Featured Post

Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

  • 7
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now