XADM: Exchange Server May Appear to Hang With Non-Responsive Domain Controller

This article was previously published under Q322056
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
The Microsoft Exchange Information Store service may appear to stop responding (hang). New clients may be unable to log on. If this is a virtual server for a cluster, a cluster failover may occur.
CAUSE
The information store relies on DSAccess to query directory services. DSAccess uses Wldap32.dll to query directories, and relies on Wldap32.dll to return an error if a time-out is exceeded during normal operation.

If the Lightweight Directory Access Protocol (LDAP) server (domain controller) cannot receive more data from the client (store) because the server-side data buffers are full, Wldap32.dll may loop forever trying to submit more data. The typical time-out logic does not apply to this condition.
RESOLUTION
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
A new Wldap32.dll option (LDAP_OPT_SEND_TIMEOUT) has been created that allows Wldap32.dll to end a loop when the receiving end cannot receive more data. This fix includes an updated Dsaccess.dll file that takes advantage of this new Wldap32.dll option. The English version of this fix should have the following file attributes or later:

Component: Information Store

File nameVersion
Exmgmt.exe6.0.5770.97
Mad.exe6.0.5770.97
Store.exe6.0.5770.97
Davex.dll6.0.5770.97
Dsaccess.dll6.0.5770.97
Dscmsg.dll6.0.5770.97
Excdo.dll6.0.5770.97
Exoledb.dll6.0.5770.97
Exprox.dll6.0.5770.97
Exres.dll6.0.5770.97
Exsp.dll6.0.5770.97
Exwmi.dll6.0.5770.97
Jcb.dll6.0.5770.97
Mdbmsg.dll6.0.5770.97
Mdbsz.dll6.0.5770.97
Phatcat.dll6.0.5770.97

NOTE: Because of file dependencies, this update requires Microsoft Exchange 2000 Server Service Pack 2.
STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 3.
Properties

Article ID: 322056 - Last Review: 10/24/2013 11:42:45 - Revision: 1.3

  • Microsoft Exchange 2000 Server Standard Edition
  • kbnosurvey kbarchive kbbug kbexchange2000presp3fix kbexchange2000sp3fix kbfix KB322056
Feedback