Operation terminated with error -550 (Jet_errDatabaseDirtyShutdown, Database was not shutdoen cleanly. Recovery must first run to properly complete I'm getting that error. can someone how to recoevery this. I was reading on google and they told me to to run the eseutil /P .edb then run the /d on the .edb. is this the right way to do it?

yes,you need to bring the database back to a consistent, clean shutdown state. to do this, dismount the database, the run the eseutil /p command on the database to repair it after which you run the /d swith to defragment it and finally scan the database with isinteg to make sure it is consistent. You should now be able to successfully mount the database. Note: before running the eseutil command with any of the switches make sure that you have enough free space for the process to complete, that is 110% the totalsize of the database should be free for the tool to run.

Whoa - STOP! I hate it when people just give blanket advice like this without knowing more information. If you are just in a dirty shutdown state, there normally should NOT be a need to run eseutil /p. Here in PSS, we even avoid running eseutil /p unless it is the ONLY option. If you run eseutil /mh and specify the database, it should tell you the required log files to bring it to a clean state. What is the output from that? What you will typically see is something like the following (below). This tells me that the database needs log file e000000F.login order to come up cleanly. Now, if I look at my logs, the most recent file is e000000E.log, but there is also the e00.log file, which the database knows is the next log file. If you are missing a log fie, then the best course of action is to perform a restore from backup. If your logfiles are ok, you can try running eseutil /r (recovery mode) and specifying the log file sequence. What happens when you do these steps? C:\Program Files\Exchsrvr\bin>eseutil.exe /mh ..\MDBDATA\priv1.edb Microsoft(R) Exchange Server Database UtilitiesVersion 6.5Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Database: ..\MDBDATA\priv1.edb File Type: Database Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdefFormat ulVersion: 0x620,11Engine ulVersion: 0x620,11Created ulVersion: 0x620,9 DB Signature: Create time:08/13/2003 14:44:19 Rand:17616329 Computer: cbDbPage: 4096 dbtime: 142038 (0x22ad6) State: Dirty Shutdown Log Required: 15-15 (0xf-0xf) Streaming File: Yes Shadowed: Yes Last Objid: 370 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 0 Repair Date: 00/00/1900 00:00:00Old Repair Count: 0 Last Consistent: (0xE,91F,159) 01/22/2007 16:13:37 Last Attach: (0xE,928,165) 01/22/2007 16:39:25 Last Detach: (0x0,0,0) 00/00/1900 00:00:00 Dbid: 1 Log Signature: Create time:08/13/2003 14:43:56 Rand:17563390 Computer: OS Version: (5.2.3790 SP 1) Previous Full Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 Previous Incremental 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: 0cpgUpgradeSpaceMapPages: 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: noneOld bad Checksum Error Count: none Operation completed successfully in 2.123 seconds.

Hi Ben.... I have this problem and when i dump the database with eseutil, say me: Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 08.01 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Database: Database1.edb File Type: Database Format ulMagic: 0x89abcdef Engine ulMagic: 0x89abcdefFormat ulVersion: 0x620,12Engine ulVersion: 0x620,12Created ulVersion: 0x620,12 DB Signature: Create time:11/10/2007 22:33:42 Rand:2508273 Computer: cbDbPage: 8192 dbtime: 34452687 (0x20db4cf) State: Dirty Shutdown Log Required: 56356-56362 (0xdc24-0xdc2a) Log Committed: 0-56362 (0x0-0xdc2a) Streaming File: No Shadowed: Yes Last Objid: 8525 Scrub Dbtime: 0 (0x0) Scrub Date: 00/00/1900 00:00:00 Repair Count: 0 Repair Date: 00/00/1900 00:00:00Old Repair Count: 0 Last Consistent: (0xDBB7,7E0,12F) 01/02/2008 18:14:27 Last Attach: (0xDBB8,9,86) 01/02/2008 18:14:27 Last Detach: (0x0,0,0) 00/00/1900 00:00:00 Dbid: 1 Log Signature: Create time:11/10/2007 22:33:41 Rand:2507177 Computer: OS Version: (5.2.3790 SP 2) Previous Full Backup: Log Gen: 0-0 (0x0-0x0) Mark: (0x0,0,0) Mark: 00/00/1900 00:00:00 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: 0cpgUpgradeSpaceMapPages: 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: noneOld bad Checksum Error Count: none Operation completed successfully in 0.15 seconds. Im using exchange 2007 with SP1, and i dont have any backup... .... so....my only solutions is run /p parameter??? eseutil /ml in the transaction log folder say me: Extensible Storage Engine Utilities for Microsoft(R) Exchange Server Version 08.01 Copyright (C) Microsoft Corporation. All Rights Reserved. Initiating FILE DUMP mode... Verifying log files... Base name: e00 Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC16.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC17.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC18.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC19.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC1A.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC1B.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC1C.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC1D.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC1E.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC1F.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC20.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC21.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC22.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC23.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC24.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC25.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC26.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC27.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC28.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E000000DC29.log - OK Log file: C:\Program Files\Microsoft\Exchange Server\Mailbox\First Storage Group\E00.log - OK No damaged log files were found. Operation completed successfully in 0.250 seconds. Can you help me?.Thanks Daniel Gonzalez

The listed log files have not yet been committed to the databse (at time of dismount) causing it to fall into a Dirty Shutdown state. Try running eseutil /r "path-to-database.edb" to perform a soft recovery. If this fails then thereappears to be some logs missing or corrupt from the SG Log Directory. Have a look in your AV software Quarantine to see if by any chance you have any Exchange Logs (E00xxxxxx.log) which have been moved from the Log Directory above. (in this case it should only be the log file : E000000DC2a.log) If you can locate the missing logs then you should restore them to the log folder & run eseutil /r again to attempt another soft recovery of the databases. If you cannot locate the missing log file then the thing to do is to restore from last good backup & replay the logs (again using eseutil /r) to recover the server to the latest good configuration. You should always ensure that your AV Software on ExchangeServershas exclusions set as per MS KB245822

Hello Johan Dreyer,If you look into the log files required and logs committed you would see the following:Log Required: 56356-56362 (0xdc24-0xdc2a)Log Committed: 0-56362 (0x0-0xdc2a)The last committed log shown here 0xdc2a this means the last log file was already committed to the database. Now as per your suggestion we require no log files.I think the only way to perform the same would be restore from the backup and reply all the transation log files by running eseutil /ccIf I am wrong do let me know.I am presently facing the same issue and when I try soft replay the transaction log files it is successful and still the database would show as dirty shutdown.Thanks,V.Sujith Nair

Have you checked the state of your Public Folder by running the eseutil /mh command? you sure that softrecovery completed successfuly? type the command you did to do the soft recovery? Vinod |CCNA|MCSE 2003 +Messaging|MCTS|ITIL V3|

In order to sort out this issue, you need to use the following measures: 1. Run eseutil /r for the corrupted database that allows playing the transaction log files 2. If this doesn't help, restore from the last online backup if available 3. In case no valid backup is present, you can run run eseutil /p command, followed by eseutil /d to defragment the database. Eeseutil /p is a hard repair command and checks each 4 KB database page for errors. If it finds errors that it cannot correct, it simply discards the page and proceeds further. Thus the command can cause serious data loss. To avoid data loss problem, you are suggested to use a safer Exchange server recovery program like this:http://www.recover-computerdata.com/exchange-server-recovery.html. This EDB repair utility scans the corrupted database and repair it using powerful, yet safe, algorithms.The software rebuilds the Exchange database file and repaired database file can be directly mounted on the server. This tool is compatible with all versions of Exchange Server.