Isinteg - Microsoft Exchange Server Tools

Do be aware that Isinteg is a dangerous tool and that you ought to practice on a test server before unleashing it on a production network.  

 

That warning over, there will be situations where Isinteg is your get-out-of-jail card.  Isinteg in Exchange 2003, replaces Esefile found in older versions of Exchange.

 

  • Isinteg switches for Exchange
  • Isinteg -test
  • Isinteg -fix
  • Isinteg -patch?
  • Summary

 

Isinteg for Exchange

 

Isinteg is a valuable command line utility to check and then repair logical database inconsistencies in Microsoft Exchange Server.  If there is physical damage to the disk and database, then seek other remedies.

 

You can find isinteg in the Exchsrvr\Bin folder.  Since this folder is not in the Path, you need to be careful when executing Isinteg from the cmd prompt.  The trick is to navigate to the \exchsrvr\bin folder.  One popular method is to find the executable with explorer, then copy the path from the Address bar and paste it into the cmd prompt.  Before you start practicing with isinteg, the MSExchangeIS service should be running but the mailbox store should be dismounted.  Here is the syntax for isinteg.

 

isinteg -s ServerName [-fix] [-verbose] [-l LogFilename] -test TestName[[, TestName]...]

 

 

Isinteg switches in Exchange Server 2003

 

When you run isinteg, the first switch to append, the switch I always forget, is the -s ExchangeServer.

 

Isinteg -test

 

The -test switch has a range of further commands.  If in doubt then try -test Alltests.

 

Example 1: of Event log ID 7200 FDsWaitTask problem

ID 7200 Background thread FDsWaitTask halted due to error code <xxx>.

 

This error, with FDsWaitTask, can usually be cured with Isinteg -test mailbox

 

Example 1: of Event log ID 7200  EcFlushInTransitUserMail problem

 

Background thread EcFlushInTransitUserMail halted due to error code <xxx>.

 

Another common 7200 error is EcFlushInTransitUserMail,

this time try a different switch: Isinteg -test folder

 

 

Isinteg - fix (be wary)

 

ISINTEG - Firstly, one of my rare disclaimers.  Be careful with Isinteg, especially the - fix switch. Backup your Exchange .edb and log files BEFORE you even think about using Isinteg. Always begin by using ISINTEG - test, rather than -fix.

 

Example, you get error 080040301 when you are moving mailboxes to another store. The best solution is to get a hotfix, however, in an emergency try ISINTEG

 

ISINTEG -s BigServer -fix is Guy's candidate for the worlds most dangerous switch, the - fix has been know to destroy exchange. So only use in an emergency, and yes you did backup BEFORE you tried Isinteg -s BigServer -fix?

 

Here is a list of tables Isinteg examines: ACL List

 

ACL Member

Attachment

Cross Reference

Deleted Folders

Deleted Recipients

DeliveredTo

Folder

Global

Mailbox

Message

Miscellaneous

Oof History

Per-User Read

PropsIn Contents

ReplidMap

Special Folders

Timed Events

 

 

Isinteg -patch?

 

Patch files are created during an online backup of open files.  Exchange 2003 automatically patches restores, so there is no need to use the -patch switch. If there is a problem, you should use the check box 'This database can be overwritten by a restore' in Exchange System Manager.

 

The isinteg -Patch was used for correcting errors with Exchange 5.5 backup, or to be precise, problems with a restore from an offline backup. Typical Event log IDs were 1087 or Error 2083.

 

 

Summary Microsoft Exchange Server 2003 - Isinteg

 

For with inconsistencies in Microsoft Exchange 200x databases, turn to Isinteg.  I strongly recommend practicing with -tests switch before trying the -fix command.  Remember that Isinteg needs the -S servername switch.