Error message when you run an LDAP script that queries for Active Directory information after you bind to a Windows Server 2003-based domain controller: "Error 3021 No Record Found"

After you bind to a Microsoft Windows Server 2003-based domain controller, you run a Lightweight Directory Access Protocol (LDAP) script to query for information in the Active Directory directory service. However, the query fails, and you receive the following error message on the LDAP client:Additionally, the following events are logged in the Directory Service log on the domain controller.

Event ID: 1138

Event Type: Information
Event Source: NTDS LDAP
Event Category: LDAP Interface
Event ID: 1138
Date: Date
Time: Time
Computer: Computer
Description:
Internal event: Function ldap_search entered.

Event ID: 1173

Event Type: Warning
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1173
Date: Date
Time: Time
Computer: Computer
Description:
Internal event: Active Directory has encountered the following exception and associated parameters.

Exception:e0010003
Parameter:0
Additional Data
Error value:0
Internal ID:2101c64

Event ID: 1481

Event Type: Error
Event Source: NTDS General
Event Category: Internal Processing
Event ID: 1481
Date: Date
Time: Time
Computer: Computer
Description:
Internal error: The operation on the object failed.

Additional Data
Error value:
7 00000008: SysErr: DSID-00000000, problem 12 (Not enough space), data 8446

Event ID: 1535Event ID: 1139

Event Type: Information
Event Source: NTDS LDAP
Event Category: LDAP Interface
Event ID: 1139
Date: Date
Time: Time
Computer: Computer
Description:
Internal event: Function ldap_search completed with an elapsed time of Number ms.

This problem occurs if the following conditions are true:

• The LDAP script contains an LDAP filter.
• The LDAP filter is very long and contains many "AND" clauses and "OR" clauses.

Note The same query runs successfully if you bind to a Microsoft Windows 2000-based domain controller.

This problem occurs because Windows Server 2003 introduced an optimizer for LDAP filters. The optimizer analyzes the LDAP filter that is sent to the domain controller. Then, the optimizer tries to remove redundant "AND" clauses and "OR" clauses. If the LDAP filter contains many "AND" clauses and "OR" clauses, this optimization requires lots of memory. Therefore, the optimization fails.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Windows Server 2003 with Service Pack 2, Itanium-based versions

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with Service Pack 1, Itanium-based versions

To work around this problem, use a smaller LDAP filter in the LDAP script.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

To log the events that are mentioned in the "Symptoms" section in the Directory Service log, you must configure Active Directory diagnostic event logging on the domain controller. To do this, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics
3. In the details pane, right-click the 16 LDAP Interface Events entry, and then click Modify.
4. In the Value data box, type 3, and then click OK.
5. Exit Registry Editor.

For more information about how to configure Active Directory diagnostic event logging, click the following article number to view the article in the Microsoft Knowledge Base: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: