Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Lingering Object deletion ?

$
0
0

Hi Team,

In my domain I am facing the replication issue and when I looked into the event viewer, found events are getting filled with 1988 replication error.

repadmin /removelingeringobjects ServerName ServerGUID DirectoryPartition /advisory_mode 

i know the above listed one is syntax for removing the lingering object. But I don't know how to use that in an effective way and fill the detail using eventvievwer text, below is the error sample. Please help.

Source domain controller: 

c7100005-939b-475a-a401-1d1ebab0d2a3._msdcs.CORP.SYS.COM 

Object: 

CN=D29715,OU=Workstations,DC=CORP,DC=SYS,DC=COM 

Object GUID: 

7dea3e5a-bdc0-4147-8088-fa9a15ea228f  This event is being logged because the source DC contains a lingering object which does not exist on the local DCs Active Directory Domain Services database.  This replication attempt has been blocked.

 

 The best solution to this problem is to identify and remove all lingering objects in the forest.

 

 

User Action:

 

Remove Lingering Objects:

 

 The action plan to recover from this error can be found at http://support.microsoft.com/?id=314282.

 

 If both the source and destination DCs are Windows Server 2003 DCs, then install the support tools included on the installation CD.  To see which objects would be deleted without actually performing the deletion run "repadmin /removelingeringobjects<Source DC> <Destination DC DSA GUID> <NC> /ADVISORY_MODE". Theeventlogs on the source DC will enumerate all lingering objects.  To remove lingering objects from a source domain controller run "repadmin /removelingeringobjects<Source DC> <Destination DC DSA GUID><NC>".

 

 If either source or destination DC is a Windows 2000 Server DC, then more information on how to remove lingering objects on the source DC can be found at http://support.microsoft.com/?id=314282 or from your Microsoft support personnel.

 

 If you need Active Directory Domain Services replication to function immediately at all costs and don't have time to remove lingering objects, enable loose replication consistency byunsetting the following registry key:

 

Registry Key:

HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Strict Replication Consistency

 

 Replication errors between DCs sharing a common partition can prevent user andcompteracounts, trust relationships, their passwords, security groups, security group memberships and other Active Directory Domain Services configuration data to vary between DCs, affecting the ability to log on, find objects of interest and perform other critical operations. These inconsistencies are resolved once replication errors are resolved.  DCs that fail to inbound replicate deleted objects withintombstone lifetime number of days will remain inconsistent until lingering objects are manually removed by an administrator from each local DC.

 

 Lingering objects may be prevented by ensuring that all domain controllers in the forest are running Active Directory Domain Services, are connected by a spanning tree connection topology and perform inbound replication before Tombstone Live number of days pass.

Thanks , Dev


Viewing all articles
Browse latest Browse all 31638

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596344.js" async> </script>