A paged LDAP query fails on the second page and the pages that follow in Windows Server 2008 R2

Symptoms

Consider the following scenario:

You have a Lightweight Directory Access Protocol (LDAP) server or domain controller that is running Windows Server 2008 R2.
You perform a paged LDAP query against the domain controller.
You use the createTimeStamp or modifyTimeStamp attribute in the query filter.
The query result covers multiple pages.

In this scenario, the paged LDAP query fails on the second page and the pages that follow the second page.The following is an example scenario:

You deploy a domain controller that is running Windows Server 2008 R2.
You deploy a Microsoft Exchange Server 2007 server on a computer, and then you enable Microsoft Office Outlook Web Access.
You configure enough user information to enable more than one page of results from a global address list (GAL) search.
You enter a search term that will return more than one page of results.
You try to scroll back through multipage GAL search results.

In this scenario, you cannot scroll back through the results, and you receive the following error message:

Could not connect to a directory server. If the problem continues, contact technical support for your organization.

Cause

The issue occurs because some search filters are changed incorrectly in LDAP paged queries.

Resolution

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 the problem described in this article. 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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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 be running the following operating system:

Windows Server 2008 R2
Windows Server 2008 R2 Service Pack 1 (SP1)

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

Version	Product	SR_Level	Service branch
6.1.7600.20xxx	Windows Server 2008 R2	RTM	LDR
6.1.7601.21xxx	Windows Server 2008 R2	SP1	LDR

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2008 R2

File name	File version	File size	Date	Time	Platform
Ntdsa.mof	Not applicable	227,765	10-Jun-2009	20:34	Not applicable
Ntdsai.dll	6.1.7600.20861	2,723,328	18-Dec-2010	06:09	x64
Ntdsa.mof	Not applicable	227,765	05-Nov-2010	01:54	Not applicable
Ntdsai.dll	6.1.7601.21624	2,723,328	18-Dec-2010	08:51	x64

Workaround

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in WindowsTo work around the issue, you must create a registry subkey on the LDAP server. To do this, follow these steps:

Click Start , type regedit in the Search programs and files box, and then press ENTER.

If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.
Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters
On the Edit menu, point to New, and then click String Value.
Type DSA Heuristics, and then press ENTER.
Right-click DSA Heuristics, and then click Modify.
In the Value data box, type 000000000001, and then click OK.
Exit Registry Editor.

Status

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

More Information

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

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2

File name	Amd64_149ee8c9e20c2afd3347ba6c7b8f3a51_31bf3856ad364e35_6.1.7601.21624_none_e08641138148d4a0.manifest
File version	Not applicable
File size	716
Date (UTC)	21-Dec-2010
Time (UTC)	00:14
Platform	Not applicable

File name	Amd64_ffed5210101de2b65fbc8adf4e82aac4_31bf3856ad364e35_6.1.7600.20861_none_bb751eb51b570fad.manifest
File version	Not applicable
File size	716
Date (UTC)	21-Dec-2010
Time (UTC)	00:14
Platform	Not applicable

File name	Amd64_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.1.7600.20861_none_4d5676a6ebe4c26e.manifest
File version	Not applicable
File size	3,531
Date (UTC)	18-Dec-2010
Time (UTC)	06:54
Platform	Not applicable

File name	Amd64_microsoft-windows-d..toryservices-ntdsai_31bf3856ad364e35_6.1.7601.21624_none_4f6b143ae8e80a9b.manifest
File version	Not applicable
File size	3,531
Date (UTC)	18-Dec-2010
Time (UTC)	09:27
Platform	Not applicable