It Has Been Too Long Since This Machine Replicated

IT Problem

Had this issue yesterday with a client even though the server had only been in a week or two. Its your standard issue where your domain controller has lost contact with other /  another domain controller and as its been so long its passed the tombstone date so it will not replicate without intervention.In the event logs you will most likely see the errors below.

Event ID 2042:
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

and

Event ID 2089:

This directory partition has not been backed up since at least the following number of days.
We need to get replication running across the controllers again, the quickest way is with a simple reg entry on the effected servers.

IT Solution

OK so lets say you have two dc`s like I did, you need to do the following to them.

1. First we need to run regedit.

1. Browse  to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
   

1. In the right hand details pane, create or edit the registry DWORD key  that says: Allow Replication With Divergent and Corrupt Partner
   In the details pane, right-click Allow Replication With Divergent and Corrupt Partner, then modify it.
   The value yu need to enter is 1,then click OK. This allows the DC`s to replicate.

1. Now go to active directory sites and services, browse down to Default First Site Nme > Servers>Your Server Name>NTDS Settings , right click the connectors on both servers and replicate.You should now see a message saying replication has been successful

1. How long since a user last logged into server
2. Disable / Enable AD Replication
3. SBS2008 Server, Active Directory Fails, No users can connect – Trend WBS