About ISInteg Utility<\/strong><\/h2>ISInteg stands for Microsoft Exchange Information Store Integrity Checker. It is a command-line utility that searches through an offline information store, such as Exchange, for integrity weaknesses. By default, the ISInteg tool is installed in the Bin folder in Exchange Server setup. To run it globally on a server from any command prompt, the full path of Bin directory needs to be added when executing the command.<\/p>
The ISInteg utility is used with one of the following switches:<\/p>
\n- -?<\/strong> – Usage is displayed<\/li>\n\n\n\n
- -pri<\/strong> – Check private information store (default)<\/li>\n\n\n\n
- -pub<\/strong> – Check public information store<\/li>\n\n\n\n
- -fix<\/strong> – Repair information store<\/li>\n\n\n\n
- -l [logfilename]<\/strong> – Store log information in logfilename<\/li>\n\n\n\n
- -patch<\/strong> – Offline backup restore patch<\/li>\n\n\n\n
- -s<\/strong> – Server name (applicable only to Exchange 2000)
<\/li>\n<\/ul>Repairing Exchange Database with ISInteg (2003, 2007, 2010<\/em>)<\/strong><\/h2>When trying to repair Exchange database by using the ESEUtil and ISInteg utilities, you should keep the following things in mind:<\/p>
\n- Before proceeding with the repair, copy all Exchange database files since the repair procedure can cause some data loss<\/li>\n\n\n\n
- You must have sufficient free disk space to successfully run ISInteg and ESEUtil<\/li>\n\n\n\n
- Exchange Database repair with these utilities takes a substantial amount of time, depending on the size and damage<\/li>\n<\/ol>
Here’s the syntax to run the ISInteg utility:<\/strong><\/p>isinteg -pri|-pub [-fix] [-detailed] [-verbose] [-l logfilename] -test testname[[, testname]…]<\/code><\/pre>![\"isinteg](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/09\/isinteg-pri.png\")
<\/figure>If ISInteg completes its operation without any errors, the database on which it was run is considered to be repaired and ready to replace the damaged database. To put the repaired database back into production:<\/p>
\n- Run Eseutil \/MH<\/a> to see if the database is in Clean Shutdown<\/li>\n\n\n\n
- Defrag the database using Eseutil \/D. After Eseutil \/D completes successfully, run Isinteg –fix –test alltests<\/li>\n<\/ol>
![\"run](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/09\/run-Isinteg-%E2%80%93fix-%E2%80%93test-alltests.png\")
<\/figure>If, after running ISInteg, the error count in the database is greater than zero (meaning some errors still remain), do not discard the repaired database. Instead, run ISInteg again until the count becomes zero or the count does not decrement on successive runs. If successive runs of ISInteg fail to bring the error count to zero, attempt to recover as much data from the repaired database as possible.<\/p>
Problems with ISInteg<\/strong><\/h3>While ISInteg is a perfectly efficient utility to repair Exchange 2003,2007 database, it has been deprecated from Exchange server 2010 SP1. This means users of Exchange 2010 SP1 and later versions cannot use this tool to detect and fix Exchange errors. However, to replace the functionality of ISInteg, Microsoft has introduced an online mailbox corruption repair command that can run against all mailboxes during the normal maintenance window. This is the New-MailboxRepairRequest<\/a> cmdlet in EAS. To run it, the database doesn’t need to be taken offline.<\/p>Here’s how to use this cmdlet:<\/strong><\/p>New-MailboxRepairRequest -Mailbox <MailboxIdParameter> [-Archive <SwitchParameter>] <COMMON PARAMETERS><\/code><\/pre>![\"SwitchParameter\"](\"https:\/\/www.stellarinfo.com\/blog\/wp-content\/uploads\/2022\/09\/SwitchParameter.png\")
<\/figure>In the above command, COMMON PARAMETERS include instructions to detect and repair corruption based on its type. This cmdlet can detect and fix the following types of corruptions:<\/p>
\n- Search folder corruption (SearchFolder)<\/li>\n\n\n\n
- Aggregate count on folders that aren’t reflecting correct values (AggregateCounts)<\/li>\n\n\n\n
- Views on folders that aren’t returning correct contents (FolderView)<\/li>\n\n\n\n
- Provisioned folders that are incorrectly pointing into parent folders that aren’t provisioned (ProvisionedFolder)<\/li>\n<\/ul>
\nNote:<\/em><\/strong> Before running this cmdlet, appropriate permissions need to be assigned to the account from which they are to be run.<\/em><\/p>\n<\/blockquote>A Better Alternative<\/strong><\/h3>While ISInteg can repair corruption in most cases for Exchange versions prior to 2010 and New-MailboxRepairRequest can do the same for Exchange 2010 and later, using these utilities is not easy. You need to have proper understanding of their working and be ready to accept some data loss, since they aren’t foolproof. You’ll also need proper permissions to use these utilities. Even after all that, ISINTEG is not working or fails to fix severely corrupted EDB files.<\/p>
A better approach, thus, is to use competent and reliable third-party Exchange database recovery tool<\/a> such as Stellar Repair for Exchange<\/em>. Empowered with advanced scanning and repair algorithms, this tool is the perfect alternative to ISInteg and EseUtil utilities. It doesn’t require you to have any special permissions, nor does it need you to be a technical expert. It is a GUI-based tool that can repair multiple Exchange mailboxes simultaneously. The tool supports exchange server versions from 5.5, 2007, 2010, until 2019.<\/p>
<\/li>\n<\/ul>
Repairing Exchange Database with ISInteg (2003, 2007, 2010<\/em>)<\/strong><\/h2>When trying to repair Exchange database by using the ESEUtil and ISInteg utilities, you should keep the following things in mind:<\/p>
\n- Before proceeding with the repair, copy all Exchange database files since the repair procedure can cause some data loss<\/li>\n\n\n\n
- You must have sufficient free disk space to successfully run ISInteg and ESEUtil<\/li>\n\n\n\n
- Exchange Database repair with these utilities takes a substantial amount of time, depending on the size and damage<\/li>\n<\/ol>
Here’s the syntax to run the ISInteg utility:<\/strong><\/p>isinteg -pri|-pub [-fix] [-detailed] [-verbose] [-l logfilename] -test testname[[, testname]…]<\/code><\/pre><\/figure>If ISInteg completes its operation without any errors, the database on which it was run is considered to be repaired and ready to replace the damaged database. To put the repaired database back into production:<\/p>
\n- Run Eseutil \/MH<\/a> to see if the database is in Clean Shutdown<\/li>\n\n\n\n
- Defrag the database using Eseutil \/D. After Eseutil \/D completes successfully, run Isinteg –fix –test alltests<\/li>\n<\/ol>
<\/figure>If, after running ISInteg, the error count in the database is greater than zero (meaning some errors still remain), do not discard the repaired database. Instead, run ISInteg again until the count becomes zero or the count does not decrement on successive runs. If successive runs of ISInteg fail to bring the error count to zero, attempt to recover as much data from the repaired database as possible.<\/p>
Problems with ISInteg<\/strong><\/h3>While ISInteg is a perfectly efficient utility to repair Exchange 2003,2007 database, it has been deprecated from Exchange server 2010 SP1. This means users of Exchange 2010 SP1 and later versions cannot use this tool to detect and fix Exchange errors. However, to replace the functionality of ISInteg, Microsoft has introduced an online mailbox corruption repair command that can run against all mailboxes during the normal maintenance window. This is the New-MailboxRepairRequest<\/a> cmdlet in EAS. To run it, the database doesn’t need to be taken offline.<\/p>Here’s how to use this cmdlet:<\/strong><\/p>New-MailboxRepairRequest -Mailbox <MailboxIdParameter> [-Archive <SwitchParameter>] <COMMON PARAMETERS><\/code><\/pre><\/figure>In the above command, COMMON PARAMETERS include instructions to detect and repair corruption based on its type. This cmdlet can detect and fix the following types of corruptions:<\/p>
\n- Search folder corruption (SearchFolder)<\/li>\n\n\n\n
- Aggregate count on folders that aren’t reflecting correct values (AggregateCounts)<\/li>\n\n\n\n
- Views on folders that aren’t returning correct contents (FolderView)<\/li>\n\n\n\n
- Provisioned folders that are incorrectly pointing into parent folders that aren’t provisioned (ProvisionedFolder)<\/li>\n<\/ul>
\nNote:<\/em><\/strong> Before running this cmdlet, appropriate permissions need to be assigned to the account from which they are to be run.<\/em><\/p>\n<\/blockquote>A Better Alternative<\/strong><\/h3>While ISInteg can repair corruption in most cases for Exchange versions prior to 2010 and New-MailboxRepairRequest can do the same for Exchange 2010 and later, using these utilities is not easy. You need to have proper understanding of their working and be ready to accept some data loss, since they aren’t foolproof. You’ll also need proper permissions to use these utilities. Even after all that, ISINTEG is not working or fails to fix severely corrupted EDB files.<\/p>
A better approach, thus, is to use competent and reliable third-party Exchange database recovery tool<\/a> such as Stellar Repair for Exchange<\/em>. Empowered with advanced scanning and repair algorithms, this tool is the perfect alternative to ISInteg and EseUtil utilities. It doesn’t require you to have any special permissions, nor does it need you to be a technical expert. It is a GUI-based tool that can repair multiple Exchange mailboxes simultaneously. The tool supports exchange server versions from 5.5, 2007, 2010, until 2019.<\/p>
Here’s the syntax to run the ISInteg utility:<\/strong><\/p> If ISInteg completes its operation without any errors, the database on which it was run is considered to be repaired and ready to replace the damaged database. To put the repaired database back into production:<\/p> If, after running ISInteg, the error count in the database is greater than zero (meaning some errors still remain), do not discard the repaired database. Instead, run ISInteg again until the count becomes zero or the count does not decrement on successive runs. If successive runs of ISInteg fail to bring the error count to zero, attempt to recover as much data from the repaired database as possible.<\/p> While ISInteg is a perfectly efficient utility to repair Exchange 2003,2007 database, it has been deprecated from Exchange server 2010 SP1. This means users of Exchange 2010 SP1 and later versions cannot use this tool to detect and fix Exchange errors. However, to replace the functionality of ISInteg, Microsoft has introduced an online mailbox corruption repair command that can run against all mailboxes during the normal maintenance window. This is the New-MailboxRepairRequest<\/a> cmdlet in EAS. To run it, the database doesn’t need to be taken offline.<\/p> Here’s how to use this cmdlet:<\/strong><\/p> In the above command, COMMON PARAMETERS include instructions to detect and repair corruption based on its type. This cmdlet can detect and fix the following types of corruptions:<\/p> Note:<\/em><\/strong> Before running this cmdlet, appropriate permissions need to be assigned to the account from which they are to be run.<\/em><\/p>\n<\/blockquote> While ISInteg can repair corruption in most cases for Exchange versions prior to 2010 and New-MailboxRepairRequest can do the same for Exchange 2010 and later, using these utilities is not easy. You need to have proper understanding of their working and be ready to accept some data loss, since they aren’t foolproof. You’ll also need proper permissions to use these utilities. Even after all that, ISINTEG is not working or fails to fix severely corrupted EDB files.<\/p> A better approach, thus, is to use competent and reliable third-party Exchange database recovery tool<\/a> such as Stellar Repair for Exchange<\/em>. Empowered with advanced scanning and repair algorithms, this tool is the perfect alternative to ISInteg and EseUtil utilities. It doesn’t require you to have any special permissions, nor does it need you to be a technical expert. It is a GUI-based tool that can repair multiple Exchange mailboxes simultaneously. The tool supports exchange server versions from 5.5, 2007, 2010, until 2019.<\/p>isinteg -pri|-pub [-fix] [-detailed] [-verbose] [-l logfilename] -test testname[[, testname]…]<\/code><\/pre><\/figure>\n
<\/figure>Problems with ISInteg<\/strong><\/h3>
New-MailboxRepairRequest -Mailbox <MailboxIdParameter> [-Archive <SwitchParameter>] <COMMON PARAMETERS><\/code><\/pre><\/figure>\n
\n
A Better Alternative<\/strong><\/h3>