Non-default SMTP LdapRequestTimeLimit registry value
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool reads the following registry entry to determine whether the default LdapRequestTimeLimit has been changed:
If the Exchange Server Analyzer finds that the LdapRequestTimeLimit registry value has been manually created to change the default Exchange server binary setting of 600 seconds, the Exchange Server Analyzer displays a non-default warning message. By default, the LdapRequestTimeLimit registry value is not created by an Exchange Server installation. However, the LdapRequestTimeLimit registry value can be manually created after the Exchange Server installation in order to change the maximum time in seconds that a single LDAP request waits in the queue. If the registry value is manually created and the setting for the registry value is configured incorrectly, the Exchange server may experience message transport problems.
It is recommended that the LdapRequestTimeLimit registry value should be created or modified only after careful consideration. The default values in the binaries for Exchange server were carefully selected for optimal performance for use in most Exchange server environments. A general best practice is to address the root cause of the problem instead of modifying the default behavior of Exchange Server by manually configuring the registry. To comply with best practices, if the LdapRequestTimeLimit registry value exists, you may want to delete this registry value to configure the Exchange server back to the default binary setting.
The Exchange Server Analyzer reports this configuration for informational purposes only. However, you may want to change the registry value back to the default setting by editing the registry.
This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information about how to do this, view the "Restore the Registry" Help topic in Regedit.exe or Regedt32.exe.
To correct this warning
Click Start, click Run, type Regedit, and then click OK.
In the console tree locate and then click the following registry key: HKEY_LOCAL_MACHINE System\CurrentControlSet\Services\SMTPSvc\Parameters
In the details pane right-click on the LdapRequestTimeLimit registry value. Change value data to 600.
Optionally, in the details pane you can right-click the LdapRequestTimeLimit registry value and then click Delete. Confirm the deletion of the registry value by clicking Yes in the dialog box.
Restart the Exchange server.
Before you edit the registry, and for information about how to edit the registry, see Microsoft Knowledge Base article 256986, "Description of the Microsoft Windows registry" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=256986).
For more information about editing the Microsoft Windows registry see the following Microsoft Knowledge Base articles:
322755, "How to back up, edit, and restore the registry in Windows 2000" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=322755)
322756, "How to back up, edit, and restore the registry in Windows XP and Windows Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=322756)