we were installing a new server (not the Exchange 2007 server) into the rack and when sliding it in the power cables for the drive cage for all storage groups/DB for exchange 2007 came unplugged. i have 4 storage groups 3 with mailbox DB's in them and one with the journal DB and public storage DB. the server was froze after that so we had to do a hard shut down/reboot. when rebooting it said it needed to run a check disk, which it found a bunch of corrupt/orphaned files that that it fixed. . the server came back up and seemed ok, but then i noticed that i couldnt access the public folder database. i logged into the exchange server and saw that the public folder DB and the journal DB are dismounted in EMC>Server Configuration>Mailbox. when i try and mount them i get the following error(s): journal DB -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- Failed to mount database 'Journal DB'. Journal DB Failed Error: Exchange is unable to mount the database that you specified. Specified database: FTLX5\Second Storage Group\Journal DB; Error code: MapiExceptionJetErrorFileIOBeyondEOF: Unable to mount database. (hr=0x80004005, ec=-4001) . public folder DB: -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- Failed to mount database 'Public Folders Database'. Public Folders Database Failed Error: Exchange is unable to mount the database that you specified. Specified database: FTLX5\Second Storage Group\Public Folders Database; Error code: MapiExceptionJetErrorFileIOBeyondEOF: Unable to mount database. (hr=0x80004005, ec=-4001) . -------------------------------------------------------- OK -------------------------------------------------------- does anyone know the proper fix for this? i do full nightly backups of the exchange server using backup exec. but wanted to see if there was some other way to fix this without going back to a backup. i have verified that both the journal DB and the public folder DB are present in the path's showing in EMC>Server Configuration>Mailbox. any help would be greatly appreciated, regards, -------------------------------------------------------- OK --------------------------------------------------------

I suspect you'll have to go to backup and restore. Check to see if the stores are in a clean shutdown: eseutil /mh If so, you may be able to mount them if you *move*, do not delete - the transaction logs to another directory and attempt to mount the stores again. You may want to call Microsoft Support if you want to explore other options.

Check the database header and see what state it's in, clean or dirty, could well be that exch was commiting a transaction when the power cut out. If it's dirty shutdown then try to recover (soft). http://sandheep-exchadmin.blogspot.com/2011_04_01_archive.html Sukh

Hi Appears like DB got crashed :( Did you perform a health check of the database file? Open the command prompt and run the below and provide the output ESEUTIL /MH "Public folder Path like C:\exchsrvr\mdbdata\priv1.edb" Provide the full output

Hi Appears like DB got crashed :( Did you perform a health check of the database file? Open the command prompt and run the below and provide the output ESEUTIL /MH "Public folder Path like C:\exchsrvr\mdbdata\priv1.edb" Provide the full output thanks for the replies: here is the output for the two dismounted databases after running the eseutil /mh: public folder: C:\Program Files\Microsoft\Exchange Server\Bin>eseutil /mh "C:\Program Files\Mi rosoft\Exchange Server\Mailbox\Second Storage Group\Public Folders Database.edb Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 08.01 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Database: C:\Program Files\Microsoft\Exchange Server\Mailbox\Second St rage Group\Public Folders Database.edb File Type: Database Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdef Format ulVersion: 0x620,12 Engine ulVersion: 0x620,12 Created ulVersion: 0x620,12 DB Signature: Create time:10/16/2008 15:53:52 Rand:3980501 Computer: cbDbPage: 8192 dbtime: 9662676 (0x9370d4) State: Dirty Shutdown Log Required: 614173-614190 (0x95f1d-0x95f2e) Log Committed: 0-614191 (0x0-0x95f2f) Streaming File: No Shadowed: Yes Last Objid: 4612 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 0 Repair Date: 00/00/1900 00:00:00 Old Repair Count: 0 Last Consistent: (0x85CA4,8,DD) 04/26/2011 17:31:38 Last Attach: (0x85CA7,8,2D) 04/26/2011 17:49:01 Last Detach: (0x0,0,0) 00/00/1900 00:00:00 Dbid: 2 Log Signature: Create time:10/16/2008 15:53:52 Rand:4012649 Computer: OS Version: (5.2.3790 SP 2 NLS 1.1) Previous Full Backup: Log Gen: 613872-613873 (0x95df0-0x95df1) - OSSnapshot Mark: (0x95DF1,5A,15E) Mark: 08/23/2011 22:52:24 Previous Incremental Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 Previous Copy Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 Previous Differential Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 Current Full Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 Current Shadow copy backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 cpgUpgrade55Format: 0 cpgUpgradeFreePages: 0 cpgUpgradeSpaceMapPages: 0 ECC Fix Success Count: none Old ECC Fix Success Count: none ECC Fix Error Count: none Old ECC Fix Error Count: none Bad Checksum Error Count: none Old bad Checksum Error Count: none Operation completed successfully in 0.407 seconds. C:\Program Files\Microsoft\Exchange Server\Bin> journal DB: C:\Program Files\Microsoft\Exchange Server\Bin>eseutil /mh "H:\Journal\Journal D B.edb" Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 08.01 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Error: Access to source database 'H:\Journal\Journal DB.edb' failed with Jet err or -4001. Operation terminated with error -4001 (JET_errFileIOBeyondEOF, a read was issued to a location beyond EOF (writes will expand the file)) after 0.0 seconds. C:\Program Files\Microsoft\Exchange Server\Bin>

Have you treid to repair as per point 2 in my earlier post. You can see that one of the DB are in a dirty shutdown. Sukh

Have you treid to repair as per point 2 in my earlier post. You can see that one of the DB are in a dirty shutdown. Sukh i have not tried the soft repair yet on the dirty state db. i will do that here shortly. what about the journal.db that gave this output? C:\Program Files\Microsoft\Exchange Server\Bin>eseutil /mh "H:\Journal\Journal D B.edb" Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 08.01 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Error: Access to source database 'H:\Journal\Journal DB.edb' failed with Jet err or -4001. Operation terminated with error -4001 (JET_errFileIOBeyondEOF, a read was issued to a location beyond EOF (writes will expand the file)) after 0.0 seconds.

Have you treid to repair as per point 2 in my earlier post. You can see that one of the DB are in a dirty shutdown. Sukh i have not tried the soft repair yet on the dirty state db. i will do that here shortly. what about the journal.db that gave this output? C:\Program Files\Microsoft\Exchange Server\Bin>eseutil /mh "H:\Journal\Journal D B.edb" Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 08.01 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Error: Access to source database 'H:\Journal\Journal DB.edb' failed with Jet err or -4001. Operation terminated with error -4001 (JET_errFileIOBeyondEOF, a read was issued to a location beyond EOF (writes will expand the file)) after 0.0 seconds. That indicates file corruption. Restoring from backup is typically required.

yeah, agreed First of all try to check if the required logs are present, if they are then run a soft recovery. If not then restore from a backup if thats not possible, repair the database

i have just noticed that users that are in cached mode instead of saying all folders are up to date, i am seeing this folder is up to date. does that also indicate a dirty shutdown state? these are in different storage group/mailbox DB's then the original problem i posted before? is it ok to run the eseutil /mh on a database that is online or does it have be dismounted?

i have just noticed that users that are in cached mode instead of saying all folders are up to date, i am seeing this folder is up to date. does that also indicate a dirty shutdown state? these are in different storage group/mailbox DB's then the original problem i posted before? is it ok to run the eseutil /mh on a database that is online or does it have be dismounted? eseutil can only be run against a dismounted store. Ensure the mailbox stores and services are up and running as well.

i have just noticed that users that are in cached mode instead of saying all folders are up to date, i am seeing this folder is up to date. does that also indicate a dirty shutdown state? these are in different storage group/mailbox DB's then the original problem i posted before? is it ok to run the eseutil /mh on a database that is online or does it have be dismounted? eseutil can only be run against a dismounted store. Ensure the mailbox stores and services are up and running as well. mail is flowing to these mailboxes ok. when i look in EMC>Server configuration>mailbox all the mailboxes show as mounted. all services are running as well.

i have just noticed that users that are in cached mode instead of saying all folders are up to date, i am seeing this folder is up to date. does that also indicate a dirty shutdown state? these are in different storage group/mailbox DB's then the original problem i posted before? is it ok to run the eseutil /mh on a database that is online or does it have be dismounted? eseutil can only be run against a dismounted store. Ensure the mailbox stores and services are up and running as well. mail is flowing to these mailboxes ok. when i look in EMC>Server configuration>mailbox all the mailboxes show as mounted. all services are running as well. There seems to be a number of issues. I would focus on the original problem first. If Outlook clients arent updating, I would close and re-open Outlook, delete the .ost cache file if necessary and verify access via OWA.

since restoring from backup did not resolve the issue with the journal database we decided we didnt need anything in the journal database so we mounted a new blank database to fix that. for the public folder which was in a dirty state, all log files were there and ok we tried a repair soft option but that failed. so we went to a backup from prior to the power disruption, but the database was still damaged. we decided to do a recovery with data loss option. everything is backup and running ok (minus the corrupted data). thanks for the help everyone, really helped in pointing me in the right direction.