LDAP queries fail for large result sets after security update MS08-003 is applied on a Windows Server 2003-based computer

Consider the following scenario:

• The Active Directory directory service or the Active Directory Application Mode (ADAM) directory service is hosted on a Windows Server 2003-based computer.
• Security update MS08-003 is applied on the Windows Server 2003-based computer.
  
  For more information about security update MS08-003, click the following article number to view the article in the Microsoft Knowledge Base:
  943484  (http://support.microsoft.com/kb/943484/ ) MS08-003: Description of the security update for Active Directory in Windows 2000 Server and in Windows Server 2003: February 12, 2008
• You perform an LDAP query against one of these directory services.
• Many result records match the LDAP query.

In this scenario, the LDAP query fails. The following are typical examples of this problem.

Case 1

When you try to display a list of mailboxes in the Exchange Management console in Microsoft Exchange Server, the operation fails. This situation typically occurs when there are as many as several thousand mailboxes. Additionally, the following event is logged in the Application log:

Event Type: Error
Event Source: MSExchange ADAccess
Event Category: LDAP
Event ID: 2061
Description:
Process mmc.exe (EMC) (PID=PID). An LDAP search call to Directory Server Server name failed - Error code=1
(Additional information: The directory service encountered an unknown failure. Active directory response: 000020EF: SvcErr: DSID-020A0EA3, problem 5005
(UNABLE_TO_PROCEED), data 87).

Case 2

In the Exchange Management Shell, you perform an LDAP query by using the -sortby switch. If the query has large result sets, the query fails after the first page of results is returned.

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 1, x86-based versions

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

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

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

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

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

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

To work around this problem, use one of the following methods.

Method 1

Modify the LDAP query to meet one of the following conditions:

• The total number of the result records to be returned is less than the value of the MaxTempTableSize registry entry. The default value of this registry entry is 10,000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
  315071  (http://support.microsoft.com/kb/315071/ ) How to view and set LDAP policy in Active Directory by using Ntdsutil.exe
• The number of the result records to be returned is less than the number of entries that are configured for the maximum page size. The default maximum page size setting is 1,000 entries.

Method 2

Modify the LDAP query so that the result is not sorted on the server. Instead, sort the result in the client application.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Technical support for x64-based versions of Microsoft Windows

If your hardware came with a Microsoft Windows x64 edition already installed, your hardware manufacturer provides technical support and assistance for the Windows x64 edition. In this case, your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation by using unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you must have technical help with a Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware. If you purchased a Windows x64 edition such as a Windows Server 2003 x64 edition separately, contact Microsoft for technical support.

For product information about Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about x64-based versions of Windows Server 2003, visit the following Microsoft Web site: