MMS 2.2 SP1 replication stops when more than 64,000 objects exist in a single container (816657)



The information in this article applies to:

  • Microsoft Metadirectory Services 2.2 SP1
  • Microsoft Metadirectory Services 2.2
  • Microsoft Metadirectory Services 2.1

SYMPTOMS

When you use a Microsoft Metadirectory Services (MMS) replication management agent (MA) to replicate data from one MMS server to another, a maximum of 64,000 objects per container, or per organizational unit, can be successfully replicated. If the number of child objects exceeds 64,000 in any single container, replication will stop at 64,000 objects, no error messages will be logged, and replication will go on to the next container object.

RESOLUTION

Hotfix information

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

MMS 2.2 Service Pack 1 is required.

Restart requirement

The MMS service must be stopped before you apply this hotfix. Although it is not required, Microsoft recommends that the MMS server be restarted after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
   03-Jan-2002  21:37  2.2.1300.16       175,104  Cdir_ad.dll      
   20-May-2002  19:01  2.2.1300.26     1,015,296  Cdir_exe.exe     
   31-Jan-2003  19:12  2.2.1300.38     1,031,680  Cdir_ldp.exe     
   06-Feb-2003  00:19  2.2.1300.39     1,018,368  Cdir_ln.exe      
   20-May-2002  19:01  2.2.1300.26     1,060,864  Cdir_nt.exe      
   20-May-2002  19:01  2.2.1300.26       998,400  Cdir_nw.exe      
   20-May-2002  19:01  2.2.1300.26       987,648  Cdir_vns.exe     
   03-Mar-2003  20:04  2.2.1300.41       964,096  Importt.exe      
   20-Sep-2001  21:41  2.2.1300.10        26,624  Ldapschema.dll   
   11-Mar-2003  00:47  2.2.1300.43     1,039,872  Replica.exe      
   01-Aug-2001  20:17                        834  Updoid.bat
   22-Apr-2002  14:04  2.2.1300.21     1,030,656  Viacompact.exe   
   03-Mar-2003  20:04  2.2.1300.41     1,266,176  Viaserver.exe    
   25-Sep-2002  22:09  2.2.1300.33         7,168  Zoid.exe         
   25-Sep-2002  22:09  2.2.1300.33       997,888  Zscript.exe      

STATUS

This behavior is by design.

MORE INFORMATION

This hotfix has been tested by using the Replicate a zone from another LDAP server feature. The new limit of 128,000 child objects in a single container was verified. To reproduce this behavior, follow these steps:
  1. Install an original released version of MMS 2.2 SP1 on a server. This version will be known as "MMSSupplier." Configure the naming context to be O=Sales,dc=contoso,dc=com.
  2. Install an original released version of MMS 2.2 SP1 on another server. This version will be known as "MMSConsumer." Configure the naming context to be O=Sales,dc=nwtraders,dc=com.
  3. On MMSSupplier, use Compass to log on as the administrator.
  4. Create an organizational unit (OU) structure below the naming context. Label the OU "Test OU."
  5. Create more than 70,000 person objects below the OU=Test OU,O=Sales,dc=contoso,dc=com container. Use any method that is convenient, such as the Ldifde command, a modified version of the MMS Tutorial MA, or an MA that is connected to an external folder of sufficient size. The 70,000 person objects must be flat.
  6. On MMSConsumer, use Compass to log on as the administrator.
  7. On MMSconsumer, create a replication MA, and then configure the MA to replicate the OU from the supplier. (The MA may be configured to log on anonymously, but that option is not relevant to this procedure.)
  8. Create a matching replication agreement on the supplier.
  9. On MMSConsumer, run the replication MA.
  10. Examine the log files. The files will look similar to the following examples:
    MMS REPLICATION LOG: Mon Feb 24 10:37:19 2003
    Agreement: [o=Server1,ma=Replication Agreements,DsaName=MMSHost,ou=Applications,dc=contoso,dc=com]
    
    Replicating [ou=Server1,o=Organization] from 169.254.170.44+389
    Attempt[0] to open socket for [169.254.170.44+389]
    Login as [MMS2]
    
    Attempt V3 bind
    [1]-Shadow updated [ou=Server1,o=Organization]
    [1]-Timestamp matched [cn=Recipients,ou=Server1,o=Organization]
    [*] A local ENTRY [zcSubEntryName=Security Subentry,ou=Server1,o=Organization]
    [*] A local ENTRY [zcSubEntryName=Shared Data,ou=Server1,o=Organization]
    [2]-Timestamp matched [CN=Employee100 + rdn=EMP100,cn=Recipients,ou=Server1,o=Organization]
    [3]-Timestamp matched [CN=Employee101 + rdn=EMP101,cn=Recipients,ou=Server1,o=Organization]
    [4]-Timestamp matched [CN=Employee102 + rdn=EMP102,cn=Recipients,ou=Server1,o=Organization]
    
    (etc etc etc)
    
    [63991]-Timestamp matched [CN=Employee64089 + rdn=EMP64089,cn=Recipients,ou=Server1,o=Organization]
    [63992]-Timestamp matched [CN=Employee64090 + rdn=EMP64090,cn=Recipients,ou=Server1,o=Organization]
    [63993]-New replica [CN=Employee64091 + rdn=EMP60891,cn=Recipients,ou=Server1,o=Organization]
    [63994]-New replica [CN=Employee64092 + rdn=EMP64092,cn=Recipients,ou=Server1,o=Organization]
    [63995]-New replica [CN=Employee64093 + rdn=EMP64093,cn=Recipients,ou=Server1,o=Organization]
    [63996]-New replica [CN=Employee64094 + rdn=EMP64094,cn=Recipients,ou=Server1,o=Organization]
    [63997]-New replica [CN=Employee64095 + rdn=EMP64095,cn=Recipients,ou=Server1,o=Organization]
    [63998]-New replica [CN=Employee64096 + rdn=EMP64096,cn=Recipients,ou=Server1,o=Organization]
    [63999]-New replica [CN=Employee64097 + rdn=EMP64097,cn=Recipients,ou=Server1,o=Organization]
    
    >>> Processed 64000 records
    
    [64000]-New replica [CN=Employee64098 + rdn=EMP64098,cn=Recipients,ou=Server1,o=Organization]
    [64001]-New replica [CN=Employee64099 + rdn=EMP64099,cn=Recipients,ou=Server1,o=Organization]
    [64002]-New replica [CN=Employee64100 + rdn=EMP64100,cn=Recipients,ou=Server1,o=Organization]
    
    >>> Summary for [ou=Server1,o=Organization]
    
        Total replicas: 64002
        New replicas: 9
        Replica updated: 1
        Replica unchanged: 63992
        Replica removed: 9
        Local entries encountered: 2
    
    
    Replica exits 0
    Preparing for termination at Mon Feb 24 10:42:14 2003
    
    
    
  11. Log out of Compass, and then stop the MMS Server service on MMSconsumer. This hotfix is required only on MMSConsumer. It is not required on MMSsupplier.
  12. Back up MMSConsumer, and then apply this hotfix.
  13. Restart the MMS Server service on MMSconsumer.
  14. Rerun the same replication MA. The MMS Server service will record that the first 64,002 objects are unchanged, but the service will add all the missing objects.
  15. Examine the log files. The files will look similar to the following examples:
    MMS REPLICATION LOG: Mon Feb 24 10:37:19 2003
    Agreement: [o=Server1,ma=Replication Agreements,DsaName=MMSHost,ou=Applications,dc=contoso,dc=com]
    
    Replicating [ou=Server1,o=Organization] from 169.254.170.44+389
    Attempt[0] to open socket for [169.254.170.44+389]
    Login as [MMS2]
    
    Attempt V3 bind
    [1]-Shadow updated [ou=Server1,o=Organization]
    [1]-Timestamp matched [cn=Recipients,ou=Server1,o=Organization]
    [*] A local ENTRY [zcSubEntryName=Security Subentry,ou=Server1,o=Organization]
    [*] A local ENTRY [zcSubEntryName=Shared Data,ou=Server1,o=Organization]
    [2]-Timestamp matched [CN=Employee100 + rdn=EMP100,cn=Recipients,ou=Server1,o=Organization]
    [3]-Timestamp matched [CN=Employee101 + rdn=EMP101,cn=Recipients,ou=Server1,o=Organization]
    [4]-Timestamp matched [CN=Employee102 + rdn=EMP102,cn=Recipients,ou=Server1,o=Organization]
    
    (etc etc etc)
    
    [63991]-Timestamp matched [CN=Employee64089 + rdn=EMP64089,cn=Recipients,ou=Server1,o=Organization]
    [63992]-Timestamp matched [CN=Employee64090 + rdn=EMP64090,cn=Recipients,ou=Server1,o=Organization]
    [63993]-Timestamp matched [CN=Employee64091 + rdn=EMP60891,cn=Recipients,ou=Server1,o=Organization]
    [63994]-Timestamp matched [CN=Employee64092 + rdn=EMP64092,cn=Recipients,ou=Server1,o=Organization]
    [63995]-Timestamp matched [CN=Employee64093 + rdn=EMP64093,cn=Recipients,ou=Server1,o=Organization]
    [63996]-Timestamp matched [CN=Employee64094 + rdn=EMP64094,cn=Recipients,ou=Server1,o=Organization]
    [63997]-Timestamp matched [CN=Employee64095 + rdn=EMP64095,cn=Recipients,ou=Server1,o=Organization]
    [63998]-Timestamp matched [CN=Employee64096 + rdn=EMP64096,cn=Recipients,ou=Server1,o=Organization]
    [63999]-Timestamp matched [CN=Employee64097 + rdn=EMP64097,cn=Recipients,ou=Server1,o=Organization]
    
    >>> Processed 64000 records
    
    [64000]-Timestamp matched [CN=Employee64098 + rdn=EMP64098,cn=Recipients,ou=Server1,o=Organization]
    [64001]-Timestamp matched [CN=Employee64099 + rdn=EMP64099,cn=Recipients,ou=Server1,o=Organization]
    [64002]-Timestamp matched [CN=Employee64100 + rdn=EMP64100,cn=Recipients,ou=Server1,o=Organization]
    [64003]-New replica [CN=Employee64101 + rdn=EMP64101,cn=Recipients,ou=Server1,o=Organization]
    [64004]-New replica [CN=Employee64102 + rdn=EMP64102,cn=Recipients,ou=Server1,o=Organization]
    [64005]-New replica [CN=Employee64103 + rdn=EMP64103,cn=Recipients,ou=Server1,o=Organization]
    
    (etc etc etc)
    
    [87879]-New replica [CN=Employee87977 + rdn=EMP87977,cn=Recipients,ou=Server1,o=Organization]
    [87880]-New replica [CN=Employee87978 + rdn=EMP87978,cn=Recipients,ou=Server1,o=Organization]
    [87881]-New replica [CN=Employee87979 + rdn=EMP87979,cn=Recipients,ou=Server1,o=Organization]
    [87882]-New replica [CN=Employee87980 + rdn=EMP87980,cn=Recipients,ou=Server1,o=Organization]
    
    >>> Summary for [ou=Server1,o=Organization]
    
        Total replicas: 87882
        New replicas: 9
        Replica updated: 0
        Replica unchanged: 63992
        Replica removed: 0
        Local entries encountered: 2
    
    
    Replica exits 0
    Preparing for termination at Mon Feb 26 17:42:14 2003
    
    
    

Modification Type:MinorLast Reviewed:9/30/2005
Keywords:kbHotfixServer kbQFE kbQFE kbBug kbfix kbMMS220preSP2fix kbprb KB816657 kbAudITPRO