Export (0) Print
Expand All
Expand Minimize
2 out of 2 rated this helpful - Rate this topic

Top 10 Database Mounting Issues and Their Solutions

 

Topic Last Modified: 2009-04-01

Got a problem getting your databases in Exchange 2000 Server and later to mount? There are several conditions that can:

  • Cause your Exchange databases to not mount, even though the Exchange Information Store service still starts
  • Prevent the Information Store service itself from starting, which would leave databases unmounted

In most cases, the application log of the server running Exchange provides enough information to continue troubleshooting the problem and find the root cause. Those events are typically logged with a source of either MSExchangeIS (Microsoft Exchange Information Store) or ESE (Extensible Storage Engine).

Find out the how to address these issues, numbered in the order of greatest impact, by reading the Microsoft Knowledge Base articles listed on this page.

  1. Exchange reaches the 16-gigabyte (GB) limitation.
    See Knowledge Base article 828070, Exchange Server 2003 mailbox store does not mount when the mailbox store database reaches the 16-GB limit.
  2. File-level antivirus software deletes or modifies the transaction log files.
    See Knowledge Base article 823166, Overview of Exchange Server 2003 and antivirus software.
  3. Permissions in Active Directory directory service are modified.
    See the following articles in the Knowledge Base:
  4. Hardware issues are preventing your databases from mounting.
    See the following articles in the Knowledge Base:
  5. Exchange needs rights that Group Policy does not have.
    See Knowledge Base article 314294, Exchange 2000 Error Messages Are Generated Because of SeSecurityPrivilege Right and Policytest Issues.
  6. The wrong organization or administrative group names are displayed after disaster recovery.
    See the following articles in the Knowledge Base:
  7. After Exchange disaster recovery, Exchange databases do not mount if the Information Store service is not updated to the service pack level of restored databases.
    See Knowledge Base article 326017, Information Store Service Does Not Start After You Install Service Pack 1 on a Clustered Exchange Server.
  8. Exchange has run out of hard drive space.
    See Knowledge Base article 294318, C1041724 error occurs when you try to mount a database.
  9. Databases do not mount after /disasterrecovery setup.
    See Knowledge Base article 285169, Information Stores Do Not Mount After You Use the "/disasterrecovery" Switch.
  10. Hard disk NTFS file system permissions have been modified.
    See Knowledge Base article 307242, Information store does not mount with 0xfffff745 and -2235 errors.
 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.