The Repadmin.exe tool does not report existing lingering objects in Windows Server 2003

Article translations Article translations
Article ID: 948071 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

In Windows Server 2003, the Repadmin.exe tool does not report existing lingering objects. You may experience one or more of the following symptoms when you use the Repadmin.exe tool to identify or to remove lingering objects:
  • The Repadmin.exe tool reports that 0 (zero) objects were identified when you run the Repadmin /removelingeringobjects /advisory_mode command to identify lingering objects.

    When this problem occurs, you may receive an informational message that resembles the following:

    Event Type: Information
    Event Source: NTDS Replication
    Event Category: Replication
    Event ID: 1942
    Description:
    Active Directory has completed the verification of lingering objects on the local domain controller in advisory mode. All objects on this domain controller have had their existence verified on the following source domain controller.

    Source domain controller:
    GUID.domain
    Number of objects examined and verified:
    0

    Objects that have been deleted and garbage collected on the source domain controller yet still exist on this domain controller have been listed in past event log entries. To permanently delete the lingering objects, restart this procedure without using the advisory mode option.

  • The Repadmin.exe tool reports that 0 (zero) objects were removed when you run the Repadmin /removelingeringobjects command.

    When this problem occurs, you may receive an informational message that resembles the following:

    Event Type: Information
    Event Source: NTDS Replication
    Event Category: Replication
    Event ID: 1939
    Description:
    Active Directory has completed the removal of lingering objects on the local domain controller. All objects on this domain controller have had their existence verified on the following source domain controller.

    Source domain controller:
    GUID.domain
    Number of objects deleted:
    0

    Objects that were deleted and garbage collected on the source domain controller yet existed on the local domain controller were deleted from the local domain controller. Past event log entries list these deleted objects.

CAUSE

To make sure that differences that are caused by replication latency are not considered lingering objects, a filtering mechanism compares the object metadata of each suspect object to the originating domain controller’s up-to-dateness vector. If the originating domain controller is not in the up-to-dateness vector for the partition that is being examined, the filtering mechanism cannot determine the state of the object, and it is not included in the clean-up actions that are performed by repadmin. Domain controllers are added to the UTD of partners only after a complete replication cycle. Domain controllers that were demoted before completing a replication cycle with a partner could cause the domain controller’s invocation ID to be absent from the up-to-dateness vector.

WORKAROUND

To work around this problem, identify and then delete the lingering objects. For more information about how to identify and delete lingering objects, click the following article number to view the article in the Microsoft Knowledge Base:

314282 Lingering objects may remain after you bring an out-of-date global catalog server back online

MORE INFORMATION

For more information about the up-to-dateness vector, visit the following Microsoft Web site:
http://technet2.microsoft.com/windowsserver/en/library/1465d773-b763-45ec-b971-c23cdc27400e1033.mspx?mfr=true

Properties

Article ID: 948071 - Last Review: April 15, 2008 - Revision: 2.0
APPLIES TO
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
Keywords: 
kbactivedirectory kbtshoot kbprb KB948071

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com