Article ID: 826353
Article Last Modified on 2/21/2007
APPLIES TO
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows 2000 Advanced Server
SYMPTOMS
When you try to run a Lightweight Directory Access Protocol (LDAP) query, you may receive a "0xc0000221" Stop error, and the LDAP server may stop responding.
CAUSE
This problem may occur when the LDAP query contains too many filters.
RESOLUTION
Hotfix Information
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone 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.
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.
Date Time Version Size File name ----------------------------------------------------------- 15-Aug-2003 07:21 5.0.2195.6748 124,688 Adsldp.dll 15-Aug-2003 07:21 5.0.2195.6748 132,368 Adsldpc.dll 15-Aug-2003 07:21 5.0.2195.6748 63,760 Adsmsext.dll 15-Aug-2003 07:21 5.0.2195.6800 381,712 Advapi32.dll 15-Aug-2003 07:21 5.0.2195.6753 69,392 Browser.dll 15-Aug-2003 07:21 5.0.2195.6680 134,928 Dnsapi.dll 15-Aug-2003 07:21 5.0.2195.6780 96,528 Dnsrslvr.dll 15-Aug-2003 07:21 5.0.2195.6753 47,376 Eventlog.dll 15-Aug-2003 07:21 5.0.2195.6759 148,240 Kdcsvc.dll 18-Jun-2003 02:43 5.0.2195.6758 205,072 Kerberos.dll 26-Mar-2003 06:37 5.0.2195.6695 71,888 Ksecdd.sys 01-Aug-2003 02:40 5.0.2195.6797 509,712 Lsasrv.dll 01-Aug-2003 02:40 5.0.2195.6797 33,552 Lsass.exe 17-Jul-2003 08:13 5.0.2195.6786 109,840 Msv1_0.dll 15-Aug-2003 07:21 5.0.2195.6601 311,568 Netapi32.dll 15-Aug-2003 07:21 5.0.2195.6791 361,232 Netlogon.dll 15-Aug-2003 07:21 5.0.2195.6804 931,600 Ntdsa.dll 15-Aug-2003 07:21 5.0.2195.6742 392,464 Samsrv.dll 15-Aug-2003 07:21 5.0.2195.6737 131,344 Scecli.dll 15-Aug-2003 07:21 5.0.2195.6737 306,448 Scesrv.dll 14-Aug-2003 03:58 5.0.2195.6801 5,232,128 Sp3res.dll 14-Jul-2003 10:31 5.3.18.6 6,656 Spmsg.dll 14-Jul-2003 10:31 5.3.18.6 100,352 Spuninst.exe 15-Aug-2003 07:21 5.0.2195.6601 51,472 W32time.dll 15-Aug-2002 22:32 5.0.2195.6601 57,104 W32tm.exe 15-Aug-2003 07:21 5.0.2195.6741 126,224 Wldap32.dll 14-Jul-2003 10:31 5.3.18.6 22,016 Spcustom.dll
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
MORE INFORMATION
For additional information about how hotfix packages are named, click the following article number to view the article in the Microsoft Knowledge Base:
816915 New Naming Schema for Microsoft Windows Hotfix Packages
Keywords: kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp5fix KB826353
