| Event Id | 2042 |
| Source | NTDS Replication |
| 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 machines 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: <date> <time> Invocation ID of source: <ID> Name of source: <source name> Tombstone lifetime (days): <number> The replication operation has failed. |
| Event Information | According to Microsoft: USER ACTION: Determine which of the two machines was disconnected from the forest and is now out of date. You have three options: 1. Demote or reinstall the machine(s) that were disconnected. 2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication. 3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection. Registry Key: HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner This information from some newsgroups may help you: ------------------------------------------------------------------------------ This error can occur if the DC has been offline for more than 60 days, has not replicated with another DC for more than 60 days or if the time on your servers is not set correctly. This server has therefore passed the tombstone lifetime of 60 days and will need to be reinstalled. You should try running dcpromo with the /forceremoval switch and then do a metadata cleanup on AD to remove all traces of that DC. Once this is done, it can be re-promoted if desired. Fore more information follow the links given below. |
| Reference Links | How to remove data in Active Directory after an unsuccessful domain controller demotion Useful shelf life of a system-state backup of Active Directory Domain controllers do not demote gracefully when you use the Active Directory Installation Wizard to force demotion in Windows Server 2003 and in Windows 2000 Server Event ID 2042: It has been too long since this machine replicated |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.