Dirty Shutdown & eseutil (Full Version)

All Forums >> [Microsoft Exchange 2003] >> General



Message


steve02a -> Dirty Shutdown & eseutil (2.Jan.2006 8:56:44 AM)

I've discovered (and you might see from my other posting here) that I have a bad database file for my exchange.
Most likely, my priv1.edb is all wacko - which of course, has caused my exchange email to pretty much shut down and not
let me mount the mailbox stores.

Anyhow...I've been attempting to run the eseutil /r <log file name> command and it's not working because of a dirty shutdown.

I found the database was in a dirty shutdown (vs. a clean shutdown) because I ran the eseutil /k priv1.edb and it told me.

Here's a little nibble from the results:
File: priv1.STM
ERROR: database was not shutdown cleanly (dirty shutdown)


Operation terminated with error -550 (JET_errDatabaseDirtyShutdown, Database was
not shutdown cleanly. Recovery must first be run to properly complete database
operations for the previous shutdown.) after 161.94 seconds.

So, I run the eseutil /r priv1.edb to see if I can do a soft recovery and I get:

Initiating RECOVERY mode...
   Logfile base name: priv1.edb
           Log files: <current directory>
        System files: <current directory>
Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API para
meter) after 0.0 seconds.

So I find out my database is in a dirty shutdown state.  I try to recover it, and it won't let me.  What do you think I should do next - or maybe I'm missing a step?  Btw, what would cause the dirty shutdown state in the first place?




steve02a -> RE: Dirty Shutdown & eseutil (3.Jan.2006 1:30:33 AM)

I just wanted to let everyone know my issue has been resolved and my email is back up and running fine.

I ended up getting free support from Microsoft since my company is a partner w/them.  My resolution was:


Ran the eseutil /p frorm the BIN folder and repaired both the priv1.edb and pub1.edb files.
Deleted the log and chk files.
Ran a defrag on the stores . eseutil /d
Ran isinteg (isinteg -s servername -fix -test alltests) frorm the bin folder.
Mounted the stores.

I was weary about running the eseutil /p - since I've read horror stories about using /p - but it worked out fine for me.

Hope someone can use this in the future.




Exchange_Admin -> RE: Dirty Shutdown & eseutil (3.Jan.2006 4:51:05 AM)

Those are almost the steps I gave you in your other question. Glad you got everything back up and running.

And you were correct to be leary of ESEUTIL /P. What happens when you run this is that ESEUTIL is that each 4 KB page is checked for errors. If an error is found then it tries to correct it. If the error cannot be found then that page of the database is discarded (thus data loss). I have seen an entire 13 GB database be empty after running ESEUTIL /P. But I have also seen outcomes like yours.
This is why a good backup plan is essential. And test these backups. The last thing you want in a crisis situation is to have to figure out how to restore a backup. There are several disaster recovery whitepages on the internet. As a matter of fact Microsoft has one that you can download.




haydenhancock -> RE: Dirty Shutdown & eseutil (8.Mar.2011 12:56:33 PM)

Can you expand of this a little bit?

Which log and chk files were deleted? Do you have to delete these files before running the defragmentation?




uemurad -> RE: Dirty Shutdown & eseutil (9.Mar.2011 12:51:20 AM)

First, you do realize you're responding to a thread that's been inactive for 5 years?

The LOG and CHK files mentioned would be the ones associated with the particular mailbox store.  If you are running Standard Edition, there is only one set.  If you are running Enterprise Edition they are the ones associated with the Storage Group.

You do not ordinarily do anything with those files performing an offline defrag.  If you also are experiencing a problem because of a dirty shutdown, I highly recommend you call Microsoft PSS to resolve your issues.  They will do what they can to salvage your data.  As mentioned in the thread, there are no guarantees and you can lose data.




Ellinor -> RE: Dirty Shutdown & eseutil (14.Sep.2013 10:40:00 AM)

Users need to backup the edb, logs, and stm files before running eseutil /r or eseutil /p repair command line tools to fix the Exchange dirty shutdown error. Make sure that your hard disk has 110 % free space before running these inbuilt utilites. ESEUTIL /p is a last resort utility that is only run when databases will not mount due to inconsistency or serious issues in databases. If this hard repair methods does not work, then you may take help from a third party software.

Here are some simple steps also to fix this problem: http://rickytechblog.wordpress.com/2012/08/17/tips-to-fix-exchange-dirty-shutdown-state-in-exchange-server/




admin503 -> RE: Dirty Shutdown & eseutil (29.Nov.2013 12:16:10 AM)

when exchange server shows up errors like: exchange database is dirty shutdown or cannot mount exchange database etc. This situation clearly reveals that exchange database (edb) is corrupted and lies in dirty shutdown state. At this point, bring database into clean shutdown state by eseutil/r command. But, even after a successful operation to clean shutdown the database, edb files fails to mount and entire exchange mailboxes remain inaccessible. At this point, permanently repair edb file after dirty shutdown without losing original info via a dedicated solution.




johndempsey -> RE: Dirty Shutdown & eseutil (23.Feb.2014 3:50:36 PM)

Exchange Server Repair Toolbox is the perfect solution to repair corrupt EDB file and restoring users' mailboxes. This EDB software efficiently recover emails, contacts, calenders, attachments, tasks and other mailbox items from corrupt database. Tool supports MS Exchange Server 2010, 2007, 2003, 2000, and 5.5 and compatible with Windows 7, Vista, Server 2003, XP, and 2000.

http://www.exchangeserver.repairtoolbox.com/




yegulalp -> RE: Dirty Shutdown & eseutil (23.Mar.2014 11:23:51 AM)

quote:

ORIGINAL: steve02a

I've discovered (and you might see from my other posting here) that I have a bad database file for my exchange.
Most likely, my priv1.edb is all wacko - which of course, has caused my exchange email to pretty much shut down and not
let me mount the mailbox stores.

Anyhow...I've been attempting to run the eseutil /r <log file name> command and it's not working because of a dirty shutdown.

I found the database was in a dirty shutdown (vs. a clean shutdown) because I ran the eseutil /k priv1.edb and it told me.

Here's a little nibble from the results:
File: priv1.STM
ERROR: database was not shutdown cleanly (dirty shutdown)


Operation terminated with error -550 (JET_errDatabaseDirtyShutdown, Database was
not shutdown cleanly. Recovery must first be run to properly complete database
operations for the previous shutdown.) after 161.94 seconds.

So, I run the eseutil /r priv1.edb to see if I can do a soft recovery and I get:

Initiating RECOVERY mode...
   Logfile base name: priv1.edb
           Log files: <current directory>
        System files: <current directory>
Operation terminated with error -1003 (JET_errInvalidParameter, Invalid API para
meter) after 0.0 seconds.

So I find out my database is in a dirty shutdown state.  I try to recover it, and it won't let me.  What do you think I should do next - or maybe I'm missing a step?  Btw, what would cause the dirty shutdown state in the first place?


Here is an other great opportunity for all Exchange users, Exchange Server with better GUI. By using this utility you can recover your valuable data from damaged Exchange databases using this advance exchange server repair tool.

Download demo version from here : http://email-****-tool.blogspot.in




GaryDangelo75 -> RE: Dirty Shutdown & eseutil (8.May2014 5:44:48 AM)

Although ESEUTIL /p repair tool can help you to repair your corrupt Exchange database but due to some limitations, it does not give the accurate results. Specially, when exchange database file is severely damaged. In such cases, only a third party Exchange EDB recovery tool may help you to rebuild the corrupted items in databases. Here is one such program that helped us to recover and restore the damaged Exchange database file successfully from Exchange dirty-shut down problem:
http://bit.ly/1QvJlkZ
Use Free Version to Get Results.




GeorgeSellers -> RE: Dirty Shutdown & eseutil (2.Jun.2014 5:50:13 AM)

Read blog post to repair corrupt exchange server database errors.
http://exchangeserverstips.wordpress.com/2013/12/05/how-to-solve-when-exchange-database-fails-to-mount-with-hr0x80004005-ec-528-error/

I hope it will help you.
Thanks




LouisBlackmore -> RE: Dirty Shutdown & eseutil (14.Aug.2014 1:19:16 AM)

Microsoft provides some free utilities, named as Eseutil.exe, Exmerge.exe and Export-Mailbox. These tools convert EDB to PST and extract the user mailboxes in .PST file format. However in case of severely corruption, these tools may fails. The best way to handle this situation is using some advanced third party Exchange Server Recovery software. You can use free trial version for extracting edb mailboxes.
http://www.exchangeserver.pcrecoverytools.com/
Free to Try




amiliaa1 -> RE: Dirty Shutdown & eseutil (9.Oct.2015 2:01:16 PM)

Exchange Server Recovery is the best and powerful solution to fix all EDB file corruption issues effectively. The software performs accurate recovery of all emails, attachments, contacts, and other mailbox items from corrupt EDB files in a very short span of time. Read more information and free download click here http://exchangeserverdatabaserecovery.blogspot.com and http://mailbox-exchange-recovery.blogspot.com




annabeleva042 -> RE: Dirty Shutdown & eseutil (25.May2017 7:15:21 AM)

Enstella Exchange EDB Recovery Software is very protected and trustworthy application to scan and repair several types of Exchange EDB corruption issues like as :- Dirty Shutdown errors , file size errors , jet engine errors and unavailability of internet etc and gives the four easy to readable formats to convert Exchange EDB File to PST (Outlook)/EML/MSG and HTML. This tool has powerful capacity to transfer single and multiple Exchange Mailboxes Data to Outlook with all attachment/properties/journal/appointment/body content and contact etc. This application gives the split command to break oversize of PST File into small PST File from 1 GB to 5 GB during conversion process.


Read More :- Exchange EDB to PST Recovery




lizzewatson90 -> RE: Dirty Shutdown & eseutil (15.Jun.2017 5:36:11 AM)

EDB Repair software helps to export exchange database to PST. Exchange **** easily repair corrupt EDB and extract EDB emails with all email properties like: To/Cc/Bcc/Subject/Date & Time etc and swiftly export to PST mailbox.




gupta1991ravi -> RE: Dirty Shutdown & eseutil (7.Oct.2019 2:56:57 AM)

I found a blog where some easy steps have been discussed related to your query. I think it will help you to repair Exchange database from dirty shutdown state.

https://www.mailsdaddy.com/blogs/repair-exchange-database-edb-dirty-shutdown-state/




Page: [1]