Thursday, January 7, 2010

How to Solve when Exchange Database Fails to Mount with (hr=0x80004005, ec=-528) Error?

Transaction log files record all the modifications to an Exchange Server database and are crucial for the proper functioning of Exchange. If you remove a log file that has not been written to the associated database, it can bring several issues, the most common being that the database may fail to mount. You can solve this problem by removing all the log files, but you first need to check the database consistency. If it exists in inconsistent state, the solution is to restore from backup or apply an EDB Repair technique. For instance, consider a scenario in Exchange Server. You try to mount a mailbox store, but the operation fails with the below error message.

“Exchange is unable to mount the database thay you specified. Specified database: Servername\First Storage Group\Mailbox Database; Error code: mapiExceptionCallFailed: Unabble to mount database. (hr=0x80004005, ec=-528)”

The error occurs each time when you try to mount the store. As a result, all the clients connected to server are disconnected.

The above error can occur if you remove a (or more) log file, which has not been committed to the database yet.

To solve this issue, you need to move the transaction log files to a different folder. For this, follow the steps mentioned underneath:
  • Stop Information Store and all databases in the storage group
  • Verify the integrity of database by running esesutil /mh command, followed by database name (for example, for Mailbox Store1 database, name is Mailbox Store1.edb). Examine the 'State' value under its header information
  • If the database is in Clean Shutdown (Consistent) state, you can safely remove all the transaction log file and save them to a different folder. Make sure you don't remove the current transaction log file
  • If the database is in Dirty Shutdown (Inconsistent) state, restore from the last online backup. In case backup is invalid, run eseutil /r command for soft recovery.
If this fails, you can run eseutil /p command for hard recovery or use an Exchange repair software. The former option (hard recovery) causes data loss as it deletes the corrupted pages. An EDB Repair utility can safely repair a corrupted Exchange database and provides secure data restoration.

Stellar Phoenix Mailbox Exchange Recovery is a powerful EDB Repair Tool that repairs and restores Exchange database created with Exchange Server 5.5, 2000, 2003, 2007 and 2010. The advanced EDB Repair Software extracts all user mailboxes into individual *.pst files and provides option for selective mailbox recovery. The tool is compatible with Windows 7, Vista, XP, 2003, and 2000.

No comments:

Post a Comment