When to troubleshoot Active Directory replication event ID 2042?
This article helps you troubleshoot Active Directory replication Event ID 2042. If a domain controller has not replicated with its partner for longer than a tombstone lifetime, it is possible that a lingering object problem exists on one or both domain controllers.
How long does it take for NTDs settings to be restored?
By default, NTDS Settings objects that are deleted are revived automatically for a period of 14 days. Therefore, if you do not remove server metadata (use Ntdsutil or the script mentioned previously to perform metadata cleanup), the server metadata is reinstated in the directory, which prompts replication attempts to occur.
When to restart replication after divergent replication event?
Domain controllers will normally stop replicating with any partner that is deemed to be engaged in divergent replication. After you remove all lingering objects, you can restart replication on the domain controller that logged the event by editing the registry. Restart replication only after you have removed all lingering objects.
When is event ID 2042 logged in directory service event log?
When the condition that causes Event ID 2042 to be logged occurs, inbound replication with the source partner is stopped on the destination domain controller and Event ID 2042 is logged in the Directory Service event log.
What are the eventids for domain controller replication errors?
EventID: 0x00001796 esently being used between clients and this server. This event occurs once per b oot of the server on the first time a client uses NTLM with this server. An error event occurred. EventID: 0xC0001B61 ceworks Agent Shell Service service to connect. A warning event occurred. EventID: 0x000727AA
When does a domain controller stop replicating with a partner?
When a partner domain controller is discovered to be passing older changes, the changes from the partner are deemed to be “divergent.” The partner is said to be engaged in “divergent replication.” Domain controllers will normally stop replicating with any partner that is deemed to be engaged in divergent replication.
Where are SYSVOL folders not replicating across domain controllers?
After checking the event viewer I am across several logs that seemed a bit concerning to me. The DFS Replication service initialized SYSVOL at local path C:\\Windows\\SYSVOL\\domain and is waiting to perform initial replication.