XADM: Directory Replication Occurs Five Minutes After Startup

Last reviewed: February 12, 1998
Article ID: Q175545
The information in this article applies to:
  • Microsoft Exchange Server versions 4.0 and 5.0

SYMPTOMS

Five minutes after restarting the Microsoft Exchange Directory Service, directory replication requests are sent to other Microsoft Exchange Sites. The replication requests can be sent outside of scheduled times on the Directory Replication connectors.

CAUSE

When the Directory Service starts, it searches the Directory for objects that have a property indicating that they should be synchronized at startup. All naming contexts are created with this property set so the Directory Service sends a request for updates at startup for each of them. Since directory replication between Sites is messaging based, the Directory Services waits five minutes for the Microsoft Exchange Message Transfer Agent (MTA) to start before submitting the update requests.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. A supported fix is now available, but has not been fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Microsoft has confirmed this to be a problem in Microsoft Exchange Server, version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

MORE INFORMATION

Microsoft has added a new registry value to the Microsoft Exchange Directory Service that allows a Microsoft Exchange administrator the option of having the Directory Service ignore the synchronize at startup property for naming contexts that are message based (this implies replication requests to Sites). The Directory Service will still send synchronization requests during the scheduled replication times as configured on the Directory Replication Connectors.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

To enable this feature, perform the following steps after applying the new files from Microsoft.

  1. Run Registry Editor (Regedt32.exe).

  2. Go to the following key in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services \MSExchangeDS\Parameters

  3. On the Edit menu, click Add Value and use the following entry (note the spaces carefully).

          Value Name: Replicator inter site sync at startup
          Data Type:  REG_DWORD
    
          Value:      0
    
    

  4. Exit the Registry Editor and restart the Directory Service for the change to take effect.

Setting this value to 0 will prevent the Directory Service from sending directory replication requests to other Sites at startup. To restore the default behavior, either delete the registry value or set it to a value of 1 and restart the Directory Service.


Additional query words: unplanned unscheduled Directory Replication backlog
dirrep
Keywords : kbbug4.00 kbbug5.00 kbfix5.00.sp2 XADM
Version : WinNT:4.0,5.0
Platform : winnt
Issue type : kbbug
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 12, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.