Exchange 2007 – Unable to mount database

25 pts.
Tags:
Exchange 2007 error messages
Microsoft Exchange
Microsoft Exchange 2007
Microsoft Exchange errors
With exchange 2007, I'm getting following error message when I try to mount the Exchange Database: 
Fehlercode: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)
Asked: Last updated:
Related Questions
1

Answer Wiki

Thanks. We'll let you know when a new response is added.

Check this thread for more help.

It seems to resolve a similar problem to the one you are reporting.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Exchange server 2007
    Well this happens to me and I was able to resolve it by restoring it from backup and then mount. It works!
    605 pointsBadges:
    report
  • bobluis
    There could be the following causes for this erroneous situation: * The ‘DomainNameExchange Servers’ group is not assigned the ‘Manage auditing and security log’ user right. * The Exchange server database file is corrupt or damaged. For the first cause, check this solution:http://kbalertz.com/925825/Event-logged-Application-mount-database-Exchange-Server.aspx If this doesn't solve the problem you will have to restore it from an old backup file or run eseutil.exe command utility. Please follow these steps: 1. Run Eseutil /p, a hard repair process on the corrupted database. 2. Run Eseutil /d, to defragment the database. Offline defragmentation process makes a new physical database 3. Now run Isinteg -fix to Check the consistency of the Exchange server database. You may need to run Isinteg several times until it returns zero errors. Note: Eseutil /p may cause data loss as it removes the damaged database pages during repair process to bring the database file into consistent state.
    1,450 pointsBadges:
    report
  • Subhendu Sen
    First make a offline backup before messing up everything. Then run as, eseutil/mh <database path + name> & check if the shutdown is clean.
    140,850 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: