LDAP queries are executed more slowly than expected in the AD or LDS/ADAM directory service and Event ID 1644 may be logged
When you enable field engineering (debug) logging to trace an LDAP query, the following event log shows that the LDAP query is an inefficient query:
Event ID : 1644
Category : Field Engineering
Source : NTDS General
Type : Information
Machine : ComputerName
Message : Internal event: A client issued a search operation with the following options.
Starting node: DC=contoso,DC=com
Search scope: subtree Attribute selection: …
Visited entries: 31950
Returned entries: 1
Additionally, you experience a slow response time.
When you inspect the attributes in the search filter, you find that they all have indexes that are defined. Additionally, if attributes do not have indexes that are defined, and you add the indexes through a schema change, the problem persists.
However, the LDAP server can only use one index to process a paged query. This is because LDAP does not have a transaction to end a query, and the implementation for paged searches does not create an expensive context for the query.
Article ID: 951581 - Last Review: 11/09/2010 16:19:00 - Revision: 3.0
- kbexpertiseinter kbtshoot kbprb KB951581