Eseutil Exchange 2003 Utility
Microsoft Exchange Server is based on client-server architecture whose client is MS Outlook. MS Exchange Server stores users' mailboxes in .edb file that must be managed efficiently to keep issues related to .edb file corruption far away. Keeping EDB related issues in mind, Microsoft has provided eseutil, a command-line utility to help system administrators and help desk staff to resolve EDB related issues. Using Exchange eseutil 2003 utility, the system administrator and help desk staff can perform following tasks :
- Database defragmentation
- Database repair
- Database integrity check
- Compact the database
- Verify checksum on all pages in EDB file, log files, and checkpoints
- View headers of EDB file, log files, transaction files, etc
Aforementioned are the functions that can be performed using Defrag Exchange 2003 eseutil tool. However, to use eseutil Exchange 2003 in a fruitful manner, the system administrator must have good knowledge about using Exchange eseutil along with its switches. There are various switches used with eseutil to perform aforementioned tasks. For example, eseutil /d is used to defragment the database, eseutil /p is used to repair the database, eseutil /k is used to verify checksums on all pages, and so on. Though, eseutil offers lots of benefits it also has some limitations that are listed below:
- It can be run against one Exchange database at a time.
- It can be used to perform only offline defragmentation, which means, it does not support online defragmentation.
- It can repair EDB file having less corruption.
Exchange Server 2003 experts recommend using defrag exchange 2003 when you have to verify the state of database, verify integrity in database tables, and to defragment the database. However, in case, you want to repair EDB using eseutil Exchange 2010, you are suggested to use third-party Exchange repair tool especially when Exchange 2003 eseutil has been failed to repair the database.
Most of the time it happens that eseutil exchange 2010 gets failed to completely repair the database and bring it back to clean shut down state. This happens when the EDB database has major corruptions. At that time, tool like Exchange Recovery tool enables you to repair EDB file and recover users' mailboxes with full accuracy. In that situation, Exchange Recovery software helps you bring database in clean shut down state and resolve following error messages :
- Exchange Server Error 550
- Unable to initialize the Microsoft Exchange Information Store service
- JET_errRecordNotFound, the key was not found
- Jet_errRecordDeleted
- Exchange Server Error Code 528
- # JET_errDatabaseDirtyShutdown -550
- # JET_errInvalidDatabase -1028
- # JET_errDatabaseCorruptedNoRepair -1224
Aforementioned are the errors amid other Exchange errors that can be resolved by repairing the corrupt Exchange database file. eseutil exchange 2003 Recovery tool recursively scans the corrupt EDB file, fetches users' mailboxes from it, and then allows you to save them either in PST format or in EDB file. Mailboxes saved in PST format can be directly opened with MS Outlook while the EDB file can be mounted on Exchange Server.