CAUSE
This problem occurs if the following conditions are true:
- The Exchange server has to access user rights information from domain controllers in the remote site over a WAN connection.
- The WAN connection to the remote site works intermittently. Or, the WAN connection has a low bandwidth.
When you access a server that is running Exchange Server 2003 or Exchange 2000 Server from a remote site, the Exchange server may try to access an authoritative domain controller in your home domain to receive user rights information. If the WAN connection is not working, the LDAP queries will time out. However, if the WAN connection is intermittent or has a low bandwidth, the LDAP queries that are waiting for a response accumulate. These queries cause the server to run out of threads. Therefore, the server stops responding.
RESOLUTION
Hotfix information
Microsoft Exchange Server 2003
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Exchange Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesYou must install Microsoft Exchange Server 2003 Service Pack 2 (SP2) before you install the hotfix.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
836993
How to obtain the latest service packs for Exchange Server 2003
Restart requirementYou do not have to restart the computer after you apply the hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes.File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
|
| Dsaccess.dll | 6.5.7650.25 | 637,952 | 18-Jan-2006 | 04:30 | x86 |
Microsoft Exchange 2000 Server
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.PrerequisitesYou must install Microsoft Exchange 2000 Server Service Pack 3 (SP3) and the August 2004 Exchange 2000 Server post-Service Pack 3 update rollup before you install the hotfix.
For more information about how to obtain both these software updates, click the following article number to view the article in the Microsoft Knowledge Base:
301378
How to obtain the latest Exchange 2000 Server service pack
Restart requirementYou do not have to restart the computer after you apply the hotfix. Hotfix replacement informationThis hotfix does not replace any other hotfixes.File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the
Time Zone tab in the Date and Time tool in Control Panel.
|
| Dsaccess.dll | 6.0.6619.5 | 577,536 | 22-Feb-2006 | 06:19 | x86 |
MORE INFORMATION
After you install this hotfix, the default time-out period for LDAP threads is reduced to 30 seconds. If you want to change the default time-out period, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\ SYSTEM\CurrentControlSet\Services\MSExchangeDSAccess
- Double-click the LdapBindTimeoutSecs registry entry.
Note The LdapBindTimeoutSecs registry entry is a DWORD value. - In the Value data box, type the value that you want to use for the time-out period. For example, if you want the time-out period to be 25 seconds, type 25.
This hotfix resolves the problem that is described in this article. The hotfix will not resolve a problem in which the Exchange server cannot access local domain controllers when the connections to these domain controllers are not working. In this scenario, you must troubleshoot the connections to the local domain controllers.
Information about changes to the Send As user right in post-Exchange Server 2003 SP2 hotfixes
After Exchange Server 2003 SP2 was released, a change was made to the security behavior of the Exchange Server information store. This change concerns how users assign the Send As user right. This change is included in all post-Exchange Server 2003 SP2 hotfixes that are version 6.5.7650.23 or later.
Before this change was made, if you assigned Full Mailbox Access user rights to a service account, the service was able to send messages as the owner of the mailbox in some circumstances. After this change was made, mailbox security granularity now requires that you explicitly assign the Send As user right.
Many third-party add-in programs and services send messages for Exchange Server users. These programs and services include mobile device synchronization services. These programs and services may not have been granted Send As user rights. Instead, they may rely on Full Mailbox Access user rights. After you apply this hotfix, a program or a service may no longer function correctly because the program or service account can no longer send messages for other users.
For more information about how to assign the Send As user right to an account, click the following article number to view the article in the Microsoft Knowledge Base:
912918
Error message when an application tries to send a message as another user by using Exchange Server 2003:"Access denied"
For more information, 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
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
817903
New naming schema for Exchange Server software update packages