Go Premium for a chance to win a PS4. Enter to Win

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 963
  • Last Modified:

Exchange 2007 Mailbox Database wont mount

Hi Guys, have major problem with my SBS08 server, i cannot get the Mailbox Database to mount.
Tried the database recovery tool in exchange, tried to use eseutil but kept getting multiple error messages, tried restoring from dpm2010 but got a vss writer error, tried restoring the First Storage Group directory with backup from dpm2010 that succeeded however still unable to mount database, also after this it knocked my Second Storage Group down, now unable to mount anything.
PS i have not got much experience with exchange, just stumbling along as you can probably tell.
Thanks in advance

Microsoft Exchange Error
Failed to mount database 'Mailbox Database'.

Mailbox Database
Exchange is unable to mount the database that you specified. Specified database: DHGSBS08\First Storage Group\Mailbox Database; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)

Microsoft Exchange Error
Failed to mount database 'Public Folder Database'.

Public Folder Database
Exchange is unable to mount the database that you specified. Specified database: DHGSBS08\Second Storage Group\Public Folder Database; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-515
2 Solutions
I know you have already tried eseutil, but still; try eseutil /mh "database path + name" and check if the shutdown is clean.

There may be some dataloss if there is corruption in the database, but go to the directory where the database is located and execute the following command: eseutil /r E00 (E00 being the 3 character code from the log file).

If that doesn't work, you can try to use eseutil /p.

1. eseutil /p will essentially do a 'hard repair' on the database.
2.  Then use eseutil /d to defrag the database. This might help, because offline defragmentation creates a new physical database structure and moves the existing data to that new structure.
3. Check the database consistency of the database with: isinteg -fix. Try and run the last commands as many times as it taxes to no longer show any errors.

I hope that helps you further.
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
If you cant even mount a blank database so run the below command

setup.com /prepareAD

- Rancy
I QasmiCommented:
I think when u ran eseutil/p you didnt moved the logs and  checkpoint file or whatever is there in the database folder to another folder , create a new one and move all files except the database files i.e. edb or stm file etc , There should be just the *.edb files on that location where the eseutil/p is performed

Then after successfull eseutil/p
run ISINTEG -fix and check whether you can mount the stores or not.

and since the mailbox store and the public store depends upon the checkpoint file and logs.

Repairing both in the same manner will resolve the issue.

check if this helps.
I QasmiCommented:
also if you restore the database to the same location ,
you need to do the same that is move the old logs and checkpoint file or *.trn or whatever file is there to another folder and then mount the database and check whether this resolves the issue.
donhodgeAuthor Commented:
Hi Guys, thanks very much.
Microsoft finally called back and we worked that I was doing everything except moving the logs, also had to get rid of the old cue folder to get mail flow working.

Featured Post

Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now