Microsoft KB Archive/258845

= LDAP Server Stops Responding Due to Blocking in SQL Server =

Article ID: 258845

Article Last Modified on 5/20/2003

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition
 * Microsoft Commercial Internet System 2.0
 * Microsoft Commercial Internet System 2.5

-



This article was previously published under Q258845



SYMPTOMS
Your Lightweight Directory Application Protocol (LDAP) server may stop responding to requests when the server is under a heavy load. You may also notice that your SQL Server computer, which stores your Membership database(s), is experiencing some blocking caused by the System Process IDs (SPIDs) from the LDAP server. You may also receive the following error message in your Application event log:

Event ID: 20

Source: PM Directory Store

Description: SQL Error: HRESULT: 80040e31 Minor Code: 0 Source: Microsoft OLE DB Provider for ODBC Drivers Description: [Microsoft][ODBC SQL Server Driver]Timeout expired SQLErrorInfo: 0, S1T00



CAUSE
The LDAP Query Timeout value is too low.



RESOLUTION
To resolve this issue, increase the LDAP Query Timeout value by using the following steps:
 * 1) In the Site Server Management Console, expand the Personalization and Membership object.
 * 2) Expand the server object.
 * 3) Expand the membership instance.
 * 4) Right-click the LDAP object, and then click Properties.
 * 5) Under Searches, increase the Max Query Time value.
 * 6) Restart the LDAP Service.

NOTE: Depending on the circumstances, you may need to slowly increase this value incrementally until you find a value that resolves this problem.

Keywords: kbprb KB258845

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.