Adding Multiple Databases to Same PartitionID Corrupts Database (188366)

SYMPTOMS

If you use the "PMAdmin add DBServer" command and add more than one database to the same partitionID, the Membership Database LDAP configuration may become corrupted. When you try to restart your LDAP instance, the following Windows NT System Event error messages from the LDAPSVC service may occur:

2501 - The server failed due to a runtime error. Error description is: GetLastError()=0 : DS DIT Load Cache failed.

2600 - Dynamic replication for the Site Server LDAP Service failed due to an initialization error. Verify the configuration. Error description is: GetLastError()=0 : Dit Cache Load Failed.

2500 - The server failed to start due to an initialization error. Verify the configuration. Error description is: GetLastError()=0 : CacheLoad.

481 - Site Server LDAP Service cannot initialize the following object: GetLastError()=-2146893792 : Init LdapExtension.

CAUSE

PMAdmin does not check for previous configurations of the partitionID. This allows multiple configurations to be inserted into the Membership Database for the same partitionID. The LDAP service fails to start, because this is an invalid setup.

RESOLUTION

To resolve this problem, apply the next Site Server 3.0 service pack. SP1 contains a fix to the PMAdmin command that checks for previous configurations and disallows multiple configurations for the same partitionID.

STATUS

Microsoft has confirmed this to be a problem in Site Server version 3.0. This problem was corrected in the latest Microsoft Site Server version 3.0 U.S. Service Pack. For information about obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):