Exchange 2007 db is in dirty shutdown state
Good day all, I am getting an error when trying to mount my exchange 2007 db Failed to mount database 'Mailbox Database'. Mailbox Database Failed Error: Exchange is unable to mount the database that you specified. Specified database: SRDEXCML1\First Storage Group\Mailbox Database; Error code: MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database. (hr=0x80004005, ec=-543) I do not know how to get this back up any ideas?
February 15th, 2010 7:02pm

Hi,Run the below commandeseutil /mh "Database file"In output check the Log Required XXXX andXXXXXcheck if the log files are present at the location, if yes then run the commandSoft recoveryeseutil /r "prefix"<E00> /l <log file location> /d <database location>if the log file is not present then you have two options1: restore from backup2: run the hard repair on the databasehttp://support.microsoft.com/kb/259851All the bestThanks, -GULAB
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2010 7:21pm

the log requires states 79610-79629 Where do I look for this log?
February 15th, 2010 7:29pm

If you right click the properties of Storage Group In the Exchange Management Console this would give the location of the transaction logs & these logs (79610-79629) are in decimal can you provide information in hexadecimal or they should look as follows 0x136FA - 0x1370D When you run the eseutil /mh "path of the database file.edb" the database would be in dirty shutdown Q.1 Name of the storage group?Q.2 Location of the transaction logs of the storage group?Q.3 Location of the system path file (*.chk)?Q.4 Name of the database?Q.5 Location of the database file?There are 20 logs missing however if the logs are in healthy state & as well in proper order without any missing logs then we can replay these logs into the database.To check the state of the Enn.log file (nn means the log prefix.. i.e first storage group prefix will be E00 & E01 for the second storage group)These first & storage groups are created by default when E2K7 is deployed.First Storage Group by default will have Mailbox Database & Second Storage Group will be Public Folder DatabaseTo find if the Enn.log is healthy then run the following command C:\Program Files\Microsoft\Exchange Server\bin>eseutil /ml "location of the Enn.log file" which will give the lGeneration value please take a note of it from command-promptC:\Program Files\Microsoft\Exchange Server\bin is the default location however would depend the location were exchange is installed & path provided during setup.If the Enn is healthy which could be found if you run C:\Program Files\Microsoft\Exchange Server\bin>eseutil /ml "location of the Enn.log file" with the integrity state being healthy...Then run C:\Program Files\Microsoft\Exchange Server\bin>eseutil /ml "path of the Enn" >C:\logshealth.txt i.e the .log should be removed when you mention the path of the Enn"All the eseutil commands should be run from command-promptIf these logs from C:\logshealth.txt are not damaged then you need to run the following commandeseutil /r Enn /l "path of the logs" /d "path of the database" to replay these logs into the database.
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2010 8:14pm

This is a good post by asiam. From my years working at Microsoft in support this is a question that comes up a lot and something I want to blog on. If you are unable to find the log files let us know because you have some other options to get the data out of the database but there are some caveats you need to be aware of. Chris cbfive.com
February 15th, 2010 9:38pm

ok the database states it is in a clean state but still unable to mount database error as follows -------------------------------------------------------- Microsoft Exchange Error -------------------------------------------------------- Failed to mount database 'Mailbox Database'. Mailbox Database Failed Error: Exchange is unable to mount the database that you specified. Specified database: SRDEXCML1\First Storage Group\Mailbox Database; Error code: MapiExceptionJetErrorAttachedDatabaseMismatch: Unable to mount database. (hr=0x80004005, ec=-1216)
Free Windows Admin Tool Kit Click here and download it now
February 15th, 2010 11:39pm

What’s the error event in the application log when encounter the error info above? How many databases do you have in the SG? How’s the status of other databases?James Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com
February 16th, 2010 5:51am

What you want to do is create a folder called "OLD" under the Transaction Log drive. Once the folder is created what you want to do is move all the transaction log files to the "OLD" folder. Try to mount the database again. Let me know if this works.Chris cbfive.com
Free Windows Admin Tool Kit Click here and download it now
February 16th, 2010 9:01am

hi, not sure if this is still a problem with you, but i just had the issue on a live 2007 system. was just trying to move a CMS from one node to another, a mailstore cluster drive failed to go over (think missing signature) and so the reliant mailstore failed to mount. switched back and got the drive back up, tried to mount db and got MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database. (hr=0x80004005, ec=-543) running eseutil ml <logpath> returned : JET_errFileAccessDenied, Cannot access file. the file is locked or in use after x seconds i was going to look for a prog called handles by sysinternals to try and locate the process locking out the file, but in the end thought that it was only an hour or twos logs on a mailstore thats fortunately not one thats in high use on a weekend, so i just copied the logs out to a sub dir...tried to re-mount...got MapiExceptionJetErrorMapiCallFailed...deleted the logs it tried to create and then copied the correct logs back from the sub dir in to the true log dir, attempted to mount drive again and it succeeded...my assumption is that what i essentially did was release the lock on the files by moving the logs back and forth. ...anyway, its back up now. now to find why node 2 suddenly wont host cms2s drive for this mailstore...
March 27th, 2010 1:51pm

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

Other recent topics Other recent topics