Microsoft KB Archive/303425

= XADM: Error Message: Setup Failed While Installing Sub-Component Information Store Service with Error Code 0x80005000 =

Article ID: 303425

Article Last Modified on 2/28/2007

-

APPLIES TO


 * Microsoft Exchange 2000 Server Standard Edition

-



This article was previously published under Q303425





SYMPTOMS
When you install Exchange 2000, you may receive the following error message:

Setup failed while installing sub-component Information Store Service with error code 0x80005000 (please consult the installation logs for a detailed description). You may cancel the installation or try the failed setup again.

In addition, the Exchange Server Setup Progress log may contain the following information:

[13:51:20] Entering CAtomMDB::ScCreateServerLevelPublicMDB

[13:51:20] Entering ScMAPITLHExists

[13:54:12] Leaving ScMAPITLHExists

[13:54:12] CAtomMDB::ScCreateServerLevelPublicMDB

(K:\admin\src\udog\exsetdata\components\server\a_mdb.cxx:1277) Error code 0X80005000 (20480): An invalid ADSI pathname was passed.



CAUSE
This problem can occur because in large Exchange Server deployments, the Lightweight Directory Access Protocol (LDAP) search to detect the public folder Messaging Application Programming Interface (MAPI) top-level hierarchy in the organization can time out. In this case, a bad LDAP path is formed, and then Setup fails with the error code 0x80005000.



WORKAROUND
To work around this problem, use either of the following methods:  Run Setup during off-peak hours. The LDAP query is more likely to succeed because the domain controllers are not as busy with other requests.

-or- Increase the LDAP query duration on your domain controllers. The default duration is two minutes; the Setup issue is more likely to occur if this duration is decreased. For example, if a large Exchange Server deployment exists, if you set the duration to one minute instead two minutes, the LDAP time-out issue is more likely to occur.

For additional information about how to increase the LDAP query duration, click the article number below to view the article in the Microsoft Knowledge Base:

291438 How to Modify the MaxQueryDuration Setting for Active Directory Services Interface

NOTE: The LDAP query duration setting is global to all Active Directory servers in the forest. If you change this value on one Active Directory server, all the other domain controllers in the Active Directory forest receive the change. If you change the LDAP query duration setting, you must consider how this change affects other Active Directory-dependent programs in your environment.



STATUS
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.

Additional query words: exch2kp2w

Keywords: kbbug kberrmsg kbnofix KB303425

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.