Custom Import of a Large User List May Cause an LDAP Timeout

ID: Q195387

The information in this article applies to:

SYMPTOMS

During the import of a large user list, Custom Import reports the following error message:

The import was unable to finish because of the following problem. The LDAP server may not be configured correctly. Please set the Max Query Timeout value to 0 (unlimited) and the Max ResultSet value to Unlimited.
The following error is reported in the application event log: 

   Source: P&M 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

This occurs because the SQL Server computer takes longer to respond to an LDAP query than the LDAP application allows.


RESOLUTION

To resolve this problem, increase the LDAP query timeout by performing the following steps:

  1. In the LDAP Administrator, go to the Directory Properties page, select each database in turn, and then choose Edit.


  2. Increase the timeouts from 60 (seconds) to 600 (seconds).


  3. This will need to be done for each database individually.



STATUS

Microsoft has confirmed this to be a problem in Site Server version 3.0.


MORE INFORMATION

Increasing the LDAP timeout should be done cautiously. This change can contribute to delays in the completion of the custom import process. In some cases it has been observed that the process can take days to complete. The timeout value should reflect a reasonable delay time. Other areas to check include the hardware that SQL Server runs on, memory on all platforms, database size, number of imported attributes, and network connection speeds.

Additional query words: 


Keywords          : prodsitesrv3 prodACI 
Version           : WINNT:3.0
Platform          : winnt 
Issue type        : kbbug

Last Reviewed: July 15, 1999