Failure Occurs When Using a Large Number of Containers or Groups

ID: Q193447

The information in this article applies to:

Microsoft Content Management, included with:
- Microsoft Site Server version 3.0

SYMPTOMS

Site Server may fail when attempting to utilize a large number of containers or groups.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Site Server 3.0 service pack.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/support/supportnet/default.asp

The English version of this fix should have the following file attributes or later:


   Date     Time     Size    File name           Platform
   -------------------------------------------------------
   08/28/98  12:23p    3,968 980827a_Readme.htm  (x86)
   08/25/98  03:40p  200,880 Dscomobj.dll
   07/02/98  02:27p      913 Eula.txt
   08/25/98  03:39p   65,984 Ilsdb.dll
   08/25/98  03:39p   46,912 Ldapacl.dll
   08/25/98  03:39p   81,632 Ldapdb.dll
   08/25/98  03:39p  227,648 Ldapsvc.dll
   08/25/98  12:08p  676,560 Mbrmgmt.dll
   08/26/98  03:46p   18,674 MCIS2UPD.SQL
   08/26/98  03:46p  108,650 OBJSP.SQL
   08/25/98  03:39p  272,656 Storedb.dll
   08/26/98  02:32p   64,080 Ipdate.exe
   08/28/98  12:13p    3,339 Update.inf

NOTE: If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

ARTICLE-ID: Q154871
TITLE: Determining If Your Product Is Eligible for No-Charge Technical Support

STATUS

Microsoft has confirmed this to be a problem in Site Server version 3.0.

MORE INFORMATION

Site Server 3.0 SP1 needs to be installed prior to this hotfix.

The service pack will overwrite hotfixes #980807a and #980813a. Installation of this hotfix will reapply both overwritten hotfixes.

For future reference, this file will be installed to <rootdrive>:\980827a_readme.htm

Additional setup required:

This fix requires additional database configuration. A SQL Server script Mcis2upd.sql has been provided to assist in this step. You must run this script against every existing SQL Server database supporting an updated hotfix Site Server Personalization and Membership Lightweight Directory Access Protocol (LDAP) Service instance. You must run this script before updating the LDAP servers with the hotfix. This script is a superset of the one that shipped with Microsoft Commercial Internet System 2.0 and subsequent service packs.

To run this script, perform the following steps:

Copy Mcis2upd.sql from the <siteserver>\bin\p&m directory to a location accessible from your SQL Server computer.

On the Start menu of the SQL Server computer, point to Programs, point to Microsoft SQL Server 6.5, and then click SQL Enterprise Manager.

Click the plus sign (+) next to the name of the SQL Server computer that is hosting the Membership Directory, click the plus sign (+) next to Databases, and then click the Membership Directory database.

On the Tools menu, click SQL Query Tool.

In the Query window, click the Load SQL Query icon. In the Open File dialog box, open Mcis2upd.sql from the location where it was copied to in step 1. The Mcis2upd.sql script is loaded into the Query window.

Click the Execute Query icon.

NOTE: The script may display a warning on your partitioned databases. You can safely ignore the following warning:


   Invalid object name 'DsTimestamp'

Additional query words: hotfix hot fix qfe quick fix engineering patch

Keywords : prodsitesrv3 prodCM
Version : WINNT:3.0
Platform : winnt
Issue type : kbbug