Synchronization of the ADMA Is Stopped and Not All Objects Are Processed (304038)


The information in this article applies to:

  • Microsoft Metadirectory Services 2.2
  • Microsoft Metadirectory Services 2.2 SP1
This article was previously published under Q304038

SYMPTOMS

When you run the Active Directory management agent (ADMA), the ADMA may stop processing objects prematurely. When this occurs, the ADMA does not process all of the objects.

CAUSE

There is a setting on the Operational Settings tab in the ADMA that causes import deletions not to be processed after a defined threshold is met. The default setting for Microsoft Metadirectory Services (MMS) 2.2 Service Pack 1 (SP1) is 100. The default setting of 100 is used to stop the processing before many objects are deleted in case of a mistake.

RESOLUTION

You can use a higher setting if there will be many legitimate deletions inbound from Active Directory. You can set the value to a higher number, or you can set the value to 0. Setting the value to 0 turns off this functionality. If you set the value to 0 there is no restriction on the number of deletions that are processed. To disable the limit on the number of deletions that are processed by the ADMA:
  1. Click the ADMA.
  2. Click Operate MA.
  3. Click Operational Settings.
  4. In the Abort the synchronization process if 100 consecutive deletions are encountered box, change the value to 0.

STATUS

This behavior is by design.
Modification Type:MajorLast Reviewed:5/28/2003
Keywords:kbenv kbprb KB304038
©2002 Microsoft Corporation. All rights reserved.