Exchange 2007 db is in dirty shutdown state
Hi, We had a power cut and obviously the UPS ran out before it returned. Since then First Storage Group will not mount. Tried Database repair tool from within Exhange Management console but it does not complete and stops responding. Errors as follows; -------------------------------------------------------- Failed to mount database 'Mailbox Database'. Mailbox Database Failed Error:Exchange is unable to mount the database that you specified. Specified database: SBS2008\First Storage Group\Mailbox Database; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-528) -------------------------------------------------------- - Exchange Toolbox Diagnostics shows Analysis results: Mailbox Database Database status is 'Dirty Shutdown' Details: There are missing or mismatched log files. Database information: Domain controller you selected is: SBS2008 Server that you selected is: sbs2008 Storage group that you selected is: First Storage Group Database that you selected is: Mailbox Database Lowest required log file is: 0x2FDB Highest required log file is: 0x2FDF Lowest log file found in the log directory is: E0000002FDC.log Highest log file found in the log directory is: E00.log (0x2FE0) Missing or mismatched log files: E0000002FDB.log
September 11th, 2010 4:04pm

On the log file directory, did you see E0000002FDB.log ? Thanks Shaba
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2010 4:17pm

Hi, Thanks for the quick reply. E0000002FDB.log appears to be mising and there is no backup for it. Andreas
September 11th, 2010 4:41pm

Try running this > eseutil /R Enn /A i.e. eseutil /R E00 /A This will try to fix the db if there's a missing log file. Else if that fail, you will need to run a /p as a worse case. http://technet.microsoft.com/en-us/library/aa997152(EXCHG.80).aspx Good luck.
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2010 5:21pm

Hi Thanks for this. I ran this and got the following message 'Recovery has indicated that there may be a lossy recovery option. Run recovery with the /a option. Operation terminated with error -528 JETerr_missinglogfile current logfile missing. The syntax I used was exactly this eseutil /R E00 /A in the database and logfile directory. What should I try next?
September 11th, 2010 9:41pm

Do you have a full backup you can restore and then replay the logs you have?
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2010 10:05pm

I took a copy of the database and log files before trying any of the repairs but there is no backup of the working database before it crashed. I do have a PST of all the mailboxes from client PC's so could build a new database if necessary. There are only 7 mailboxes. I'd rather not do this though if we can recover the faulty db
September 11th, 2010 10:16pm

If this helps this is the content of the folder; Folder: catalogdata ..... 08/09/2010 Files: e00.chk 08/09/2010 09.24 e00 08/09/2010 09.25 e00res00001.jrs 10/06/2010 e00res00002.jrs 10/06/2010 e0000002FDC 08/09/2010 09.24 e0000002FDD 08/09/2010 09.24 e0000002FDE 08/09/2010 09.25 e0000002FDF 08/09/2010 09.25 Mailbox Database.edb 08/09/2010 09.25
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2010 10:28pm

You might have to run the eseutil /p because if the /R Exx /A doesn't work and you don't have a backup copy then the /p switch is what you might have to run.
September 12th, 2010 10:14am

Before I run the /p is there anything else I can do? Did I get the syntax correct? Because there was a .chk file and catalogdata folder does this look like exchange tried to fix automatically? If /p loses too much data what is the procedure to create a new blank database that I can move the .pst files into to make it good? thanks for your help
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2010 2:12pm

To create a new store, move (do not delete) the .edb and log files to another directory and remount the store to create a new blank store. Then you can import the psts.
September 12th, 2010 4:28pm

Hi Thanks for this. I'm going to try the repair using /p forst which ran on the database successfully. I'll check the mailboxes and see how successfull it was. I this loses too much data I will start with a blank storee. PS: Now that the repair has run there are still several log files left what do I do with these?
Free Windows Admin Tool Kit Click here and download it now
September 12th, 2010 9:43pm

I tried mounting the store after the /p repair which is reported to have been done successfully and I get the same error Failed to mount database 'Mailbox Database'. Mailbox Database Failed Error:Exchange is unable to mount the database that you specified. Specified database: SBS2008\First Storage Group\Mailbox Database; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-528) What's next?
September 12th, 2010 9:45pm

I deleted all these, and the store remounted ok. Checked all Mailboxes and everything is now in order. Thank you all! Folder: catalogdata ..... 08/09/2010 Files: e00.chk 08/09/2010 09.24 e00 08/09/2010 09.25 e00res00001.jrs 10/06/2010 e00res00002.jrs 10/06/2010 e0000002FDC 08/09/2010 09.24 e0000002FDD 08/09/2010 09.24 e0000002FDE 08/09/2010 09.25 e0000002FDF 08/09/2010 09.25 Mailbox Database.edb 08/09/2010 09.25
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2010 12:08am

You arent done yet! You should create a new store and move mailboxes to it after gettting a good, full online backup. If you cant do that, then since you ran eseutil /p, you should now: Run Eseutil /d on this repaired store Then run Isinteg -fix -tests -alltests on the store till it reports no errors ( 2 or 3 times typically). Repaired stores should not be run in production!
September 13th, 2010 12:26am

Ok thanks. Just to clarify. Create a new store as you've suggested above, then how do I move the mailboxes into it?
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2010 7:40am

Here you go: http://technet.microsoft.com/en-us/library/bb124797(EXCHG.80).aspx http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/moving-mailboxes-exchange-2007-part1.html
September 13th, 2010 11:14am

You arent done yet! You should create a new store and move mailboxes to it after gettting a good, full online backup. If you cant do that, then since you ran eseutil /p, you should now: Run Eseutil /d on this repaired store Then run Isinteg -fix -tests -alltests on the store till it reports no errors ( 2 or 3 times typically). Repaired stores should not be run in production! I agree with Andy. If you move the mailboxes to the new storage group then the mailbox by default during the move will defrag for you but also by running isinteg it will remove any corrupted messages in the database.
Free Windows Admin Tool Kit Click here and download it now
September 13th, 2010 12:00pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics