CTOBOB

TECHNOLOGY – MEDIA – BLOG

Repair IT

Exchange error – An Active Manager operation failed. Error Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)

Exchange

Exchange 2010 Repair IT Article – By Bob Pellerin

Problem: The server had a “rough night” and needed to be relocated to a new host after a few unexplained hangs. Priliminary tests after the move were positive. Email got in and out from internal and external sources. We noticed that the public database was “unmounted”. Trying to mount it resulted in this message:

Couldn’t mount the database that you specified. … An Active Manager operation failed. Error Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515)

I’d like to point to the obvious step of trying to restore the database from your backup at this point. If the backup is hours old and you really want to try to get the latest posible version (as I did) then read on:

Here’s what I ended up doing to get it back up.

 

  1. Locate the database in question. [Hint, you’re looking for a .edb file)
  2. Backup the entire directory somewhere else.
  3. If you notice that there are a lot (as in hundreds of thousands) of log files then there’s a possible suspect to look into (later). I’m assuming you have this database all by itself (isolated).
  4. Open the Exchange Command prompt and use the eseutil as follows
  5. Command to type in the shell:    ESEUTIL /P “E:\data\public\database.edb”
  6. WARNING: DON’T DO THIS IF YOU HAVE MULTIPLE DATABASES ALL IN THE SAME DIRECTORY!!!. If you get a message that the database is locked: (Use your judgement here!) Erase all the files except the ONE .edb file you want to work on (Should be mostly .log files). (Reminder: You did back all this up into another directory in step 2).
  7. Repeat step 4.

You should now be able to mount it. Keep in mind this is a last resort procedure and should only be done if you have corruption and you’re tried other “safer” solutions. I can not be held liable for lost data or productivity if the above proves not ot work or not to bring back everything the database held previously.

I hope this helped. I’d love to hear how to improve this article, so feel free leave constructive comments.

-CTOBob

Related articles to read:
http://support.microsoft.com/kb/240145