Microsoft Exchange 2000 Server Setup Does Not Work If an LDAP Query Times Out While the Query Searches for the MAPI TLH

Article translations Article translations
Article ID: 312813 - View products that this article applies to.
This article was previously published under Q312813
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

Microsoft Exchange 2000 server Setup may not work if Lightweight Directory Access Protocol (LDAP) queries time out while the queries are searching for the Messaging Application Programming Interface (MAPI) top-level hierarchy (TLH).

CAUSE

This problem can occur if Exchange 2000 does an un-optimized search for the public folder tree in ScMAPITLHExists, and then improperly handles the no results case.
To resolve this problem, obtain the following update from the following Microsoft Web site: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=0D835016-428E-419C-9BE9-3DB6A5F7D097

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 the Microsoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Component: System attendant

The English version of this fix should have the following file attributes or later:

Collapse this tableExpand this table
File nameVersion
Exsetdata.dll6.0.4417.07

RESOLUTION

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 2.

MORE INFORMATION

After you apply this fix, Setup in large deployments no longer stops working in ScMAPITLHExists with 0x80005000 "Invalid ADSI Path".

Properties

Article ID: 312813 - Last Review: October 24, 2013 - Revision: 2.2
APPLIES TO
  • Microsoft Exchange 2000 Server Standard Edition
Keywords: 
kbnosurvey kbarchive kbbug kbexchange2000presp2fix kbexchange2000sp2fix kbfix KB312813

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com