LDAP Dynamic Directory Data May Not Be Replicated (264911)


The information in this article applies to:

  • Microsoft Site Server 3.0
This article was previously published under Q264911

SYMPTOMS

When Site Server version 3.0 Lightweight Directory Access Protocol (LDAP) Dynamic Directory is configured to replicate among multiple LDAP servers, if you stop the Site Server LDAP service on a server, dynamic objects that were recently created or modified on that server may not be replicated (and may therefore be lost).

CAUSE

When dynamic data replication is configured among multiple servers, the replication of created or modified objects in the Dynamic Directory is placed in a queue. When the LDAP service is stopped, the outstanding replication requests in the queue are not completed, and any data that has not yet been replicated is lost.

WORKAROUND

Before you shut down an LDAP service:
  1. Stop making modifications to the Dynamic Directory on the server to be stopped.
  2. Wait until the Performance Monitor counter Site Server LDAP Service : Replication Queue Size for the server is 0.
  3. Shut down the service on that server.
NOTE: If the LDAP server is part of a load-balanced environment, you can remove the server from the load balancing service so that the server receives no more client requests, but can still communicate with its replication partners.

STATUS

Microsoft has confirmed that this is a problem in Site Server 3.0.
Modification Type:MajorLast Reviewed:10/21/2000
Keywords:kbprb KB264911
©2002 Microsoft Corporation. All rights reserved.