Repair Exchange Database Corruption via ISINTEG Command

SysToolsData Expert - Recovery,Backup,Migration
SysTools Simplifying Technology Leading  in Data Recovery, Data Migration & Data Backup With 200+ Solutions.
In Exchange Server 2003 and 2007 the command isinteg is used to check the health of database and to repair Exchange Database. If the command is not successful to restore a corrupt damaged Exchange Mailbox. try an automated solution as isinteg command supports Exchange 2007 and below versions only.

Introduction to ISINTEG Command In Exchange Server

ISINTEG is a valuable command used as Microsoft Exchange Information Store Integrity Checker. This Exchange isinteg utility is utilized to test and repair Exchange database to remove logical inconstancies. This is a stand-alone Powershell Command line that can detect the actual Exchange database. It understands the link that maps tables and records with their source folders and messages, whereas ESEUTIL cannot do this. 

How to Run Isinteg Command in Exchange 2003 / 2007 Mailboxes

Information Store Integrity Checker can be used with both private and public information store of Exchange database. It inspects the information (locate the path of data in the database) linked with the Mailboxes, folders, data items, and attachments for errors. If any errors exist, repair Exchange database via the fix option of this tool. If the storage disk is physically damaged then, users have to seek other remedies. The default location of ISINTEG tool is “drive >> Program >> Files >> exchsrvr >> bin”.

The ISINTEG utility is generally used with any one of the following switches/attributes / Perimeter

  • -? Usage is displayed
  • -pri Check private information store (default)
  • -pub Check public information store
  • -fix Repair information store
  • -l [logfilename] Store log information in log filename
  • -patch Offline backup restore patch
  • -s Server name (applicable only to Exchange 2000)

Default Location: By default the ISINTEG tool stored in location Exchsrvr\Bin folder.

Pre-requisites before using ISINTEG Command In Exchange Database

Before you repair Exchange database via ISINTEG verify the following conditions:

  • a) The database should be taken completely for backup because it is possible to lose some data while repairing.
  • Backup should be kept irrespective of the Corrupted or Damaged files.
  • Enough disk space is required to execute ISINTEG command.
  • Empty EDB Database of Exchange Server.
  • No Bad Sector should be available on the hard disk.

Using Information Store Integrity Checker

To run INISTEG command line, execute the following command in Command Prompt:isinteg — s ServerName [-fix] [-verbose] [-1 logfilename] -test testname [[,test name]…]

After implying above-stated isinteg command, it will display the health state of the database and display a list of tables examined by it:

After running ISINTEG –FIX command, your system will prompt many warnings notifications before executing repair Exchange database process. However, you can ignore these messages safely. All you have to do is, pay the attention to the end of ISINTEG. If the database is in the healthy state, it will imply zero errors reported. To verify the zero error condition, run ISINTEG command once again.

Fix Exchange Database Corruption via ISINTEG Powershell

If the Exchange EDB files comprise high-level corruption that is caused by Jet Engine Failure or other accidental reason then it becomes a difficult task to repair database using ISINTEG and ESEUTIl commands. Thus, to repair Exchange database from highly-corruption, Exchange Recovery Software can be used. The Tool is capable to recover and restore back of Offline EDB File in healthy condition.

Exchange Recovery recover data from Exchange Private, Public Folders (Priv.edb, Pub.edb) and STM Files. It allows exporting data by category: Emails, Contacts, Calendar, Tasks, Journals etc. The software supports the recovery from Dismounted and offline EDB data files. The best thing about this software is that it is compatible with all versions of including Exchange Server 2016. Download Demo version of Software from below link. 

To know more visit Office Website:

Wrapping Up

Since various scenarios occur when Exchange Administrator and user faces corruption issues in Exchange Database and to fix minor corruption issues in EDB mailboxes offers two built-in utilities i.e. INISTEG and ESEUTIL. In above section, we discussed Information Store Integrity Checker Isinteg Command, which used in Exchange 2007 and below versions whereas ESEUTIL Command still used to repair exchange database. If this command line implies high-level corruption, it cannot be possible to repair Exchange Database manually via ESEUTIL.

In that case, You can go for trusted SysTools Exchange Recovery Software. A Secured way to recover data from corrupted, deleted, dismounted, offline or damaged Exchange databases and retrieve EDB in healthy condition and restored back then in Live Exchange account and Office365 account.

SysToolsData Expert - Recovery,Backup,Migration
SysTools Simplifying Technology Leading  in Data Recovery, Data Migration & Data Backup With 200+ Solutions.

Comments (0)

Have a question about something in this article? You can receive help directly from the article author. Sign up for a free trial to get started.