ESEUTIL to Repair Exchange Database Dirty Shutdown – Manual Guide


Exchange Server saves a large amount of data in EDB (Exchange database) file. Many a time, EDB gets corrupt which in turn makes the database inaccessible. There are several reasons behind EDB file corruption i.e. unexpected shutdown, power outage, virus infection. In this post, we will discuss one of the frequently occurring issue – Exchange database Dirty Shutdown and Eseutil to fix it.

What is Dirty Shutdown Issue?

When dirty shutdown state occurs, the following error message comes: Operation terminated with error -550 JET_errDatabaseDirtyShutdown. Every so often, Exchange Server shut down unexpectedly. This is when dirty shutdown problem arises. The issue results in inconsistent Exchange database.

Inbuilt Tool of MS Exchange Server – ESEUTIL

Microsoft included two inbuilt utilities named eseutil.exe and isinteg.exe to repair Exchange EDB file. ESEUTIL is designed to fix low level of the database. Besides, it is used to defragment the Exchange database. Whereas, Isinteg is used for database integrity.
Note: Both the utilities work with offline or dismounted Exchange database.

Location of Eseutil: \EXCHSRVR\BIN directory

ESEUTIL /P This cmdlet is known as repair mode which rectifies page level and Extensible Storage Engine (ESE) level issues. It doesn’t work with application level issues. ESEUTIL /p scan, repair EDB mailbox and fix issues. Eseutil can repair database dirty shutdown as well. Run the below command against your database:
ESEUTIL /D This cmdlet is known as a deframentation mode which is used to defragment a database by removing unused space. The process compact a database in offline mode.

ESEUTIL Repair Exchange Database Dirty Shutdown


 Step 1: Run eseutil /mh to know the shutdown was clean or dirty. To do this, go through the following commands:

 Step 2: If step 1 shows dirty shutdown then carry out soft recovery to make database consistent and repair database dirty shutdown with eseutil. Execute the following command:

eseutil /r is soft recovery method. In this, Exchange server reads the checkpoint file and starts replaying log files.

Alternate Method to Repair Exchange Database Dirty Shutdown 

Apart from manual method, a reliable and effective method is available named Exchange database recovery software which is a third party tool. Unlike eseutil, this software doesn’t remove highly corrupted data. One can perform recovery of mailboxes from EDB file within few clicks.

 Conclusion: The above article gives the solution for Exchange dirty shutdown issue. Eseutil is a utility which is widely used by Exchange administrators to resolve Exchange database problems.s Users can easily fix the error by using above mentioned methods.

Comments

  1. Keith Gibson8 May 2018 at 05:34

    EDB to PST Converter tool which helps users gracefully convert Exchange to Outlook PST file with overall data present in it and export mailbox from EDB to PST with whole email, contacts, calendars, tasks, notes etc. Through this massive application users can recover corrupted Edb files and save in to outlook EML, MSG, PST, RTF, PDF, and HTML and live exchange server format. Also works on all EDB File versions 2000, 2003, 2007, 2010. 2013, 2015, and 2016.
    For more information visit: https://www.edbmails.com

    ReplyDelete

Post a Comment

Popular posts from this blog

New-MailboxRestoreRequest Exchange 2010 2013 2016 Tutorial

New-MailboxRestoreRequest Exchange 2010, 2013 and 2016 cmdlet - Guide What is Exchange New-MailboxRestoreRequest cmdlet? To restore a mailbox that was soft deleted by using the New-MailboxRestoreRequest Exchange 2010, 2016 or 2013 command is used.  The above command works with disconnected, deleted mailbox and recovers all soft deleted data into main archive mailbox from an exchange server. There are different syntax and its details for Exchange 2016, 2013 and 2010. All three are explained below with parameter details link. At the end of this description, it's also explained that how the user can remove or disable mailbox. Exchange 2010 New-MailboxRestoreRequest cmdlet The Syntax for MailboxRestoreRequest cmdlet as follows: New-MailboxRestoreRequest -SourceDatabase <DatabaseIdParameter> -SourceStoreMailbox <StoreMailboxIdParameter> -TargetMailbox <MailboxOrMailUserIdParameter> [-AcceptLargeDataLoss <SwitchParameter>] [-AllowLegacyDNMismatch
Read more

Fix Error 1022 JET errDiskIO in Microsoft Exchange Server

The Error 1022 JET errDiskIO usually occurs due to disk input/output failure. So, whenever the Exchange Server requests for the database page but due to some reason the operating system is unable to get the access to that particular page and the error occurs. In this case, Server will make a request for a page number which is greater than the number of pages in that database file. This error can also occur if some incomplete transaction log set is being replayed in the database. For instance, if a transaction is running on log 9 but the transaction could not be completed because it might have exceeded the database size but after that, the page reference size has now been added to log 10. Because of this, it leads to the error 1022.
Read more