|
|
|
Question : Tombstone Active Directory Issue
|
|
Eventviewer Report as follows
Event Type: Error
Event Source: NTDS Replication
Event Category: Replication
Event ID: 2042
Date: 2/07/2004
Time: 10:53:23 AM
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: xxxxxxxxx
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 machine's 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:
2003-11-01 04:45:58
Invocation ID of source:
0591f6cc-f6bc-0591-c00c-bf04e05d7e04
Name of source:
feb6c0e4-5474-4c65-be0f-81e4ed147cf1._msdcs.yyyyyyyyyyyyyy.local
Tombstone lifetime (days):
0
The replication operation has failed.
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
Surely there is another way besides re-installing server 2003 to resolve this error message. Has anyone used option 2 or 3? Any help would be appreciated.
Thanks,
John J.
|
Answer : Tombstone Active Directory Issue
|
|
|
|
|
|
|
|
|
|
