MS Exchange Repair Tool to repair corrupted or damaged edb file

Sometimes, when you try to start MS Exchange Server database, you may come across an error message. Reasons for the occurrence of above error message could be lost/corrupt Exchange Server database files, network issues, and more. In most cases of error message occurrence, data saved in the database becomes inaccessible. An ideal alternative to access database in such situations is by restoring it from an updated backup. However, in case the backup is not available or fails to restore data, you need to opt for an effective Eseutil utility that repairs the database. But, there are situations, when the error message persists even after running the above utility. In such cases, the user needs to search for an effective third-party Exchange Server Repair utility to repair your database.

To illustrate the above situation, consider a practical case wherein your Exchange database gets corrupted and the server stops the recovery of the database:

“Error -1216 (JET_errAttachedDatabaseMismatch) ”

On viewing the event log, you encounter the underneath entry:

“Event Type: Error
Event Source: ESE98
Event Category: Logging/Recovery
Event ID: 0
Date: 4/24/2001
Time: 6:20:18 PM
User: N/A
Computer: EXCHANGE1
Description: Information Store (4312) Database recovery failed with error -1216 because it encountered references to a database, ‘D:\exchsrvr\mdbdata\PRIV2.edb’, which is no longer present. The database was not brought to a consistent state before it was removed (or possibly moved or renamed)”

Cause:

The root cause for the occurrence of the above error message is replacement or deletion of critical files that are used to open and operate Exchange Server database.

Resolution:

To resolve the above error message and to access Exchange Server database, you will need to follow the below mentioned steps:

• Use Eseutil/P repair command to repair the database.
• If the command fails, restore the database from an adequate backup.
• In case of backup unavailability, use a commercial Exchange Server Repair application. An Exchange Repair utility ensures maximum edb repair of logically damaged MS Exchange database and restoration at user-specified location.

Exchange Repair Software is a powerful, yet easy to operate Exchange Repair application that is competent enough to repair any Exchange Server 5.5, 2000, 2003, and 2007 databases. The repair application recovers almost all EDB file objects, including e-mails, tasks, notes, attachments, and appointments. It can be installed on Windows 7, Vista, XP, 2003, and 2000.

An Exchange Server database can get corrupt for several reasons, the most common being ‘Dirty Shutdown’. This leads page-level, ESE-level, or application-level corruption. Many times corruption remains undetected during normal database operations and is reflected when the user tries to backup the database. In such situations, the user needs to apply Exchange Repair methods to extract the data.

For instance, consider a situation when an Exchange Server administrator, runs a backup program to take backup of a storage group. The backup task fails and the below error message pops up:

“Error, Unable to open \ because it is currently being backed up by another process.”

The error statement further suggests that database or database element is corrupt and does not let you backup the storage group.

Cause

The error indicates that Exchange storage group is in use by some other application or process. This can occur due to one of the following reasons:

1. Another backup program is simultaneously trying to backup the Exchange Information store. Since the database file(s) are open, the backup application take them as corrupted.

2. An antivirus application has been configured that is scanning the Exchange database files

3. You are using a backup utility that is not Exchange-aware

4. The Exchange database is corrupt and backup utility cannot read it

Solution

Following are the corresponding solutions that can help you recover from such problems:

1. Deselect the Exchange Server components, that are to be backed up by another backup utility running on the computer

2. Disable the antivirus program to scan Exchange Server files

3. Try using a different, Exchange-aware utility

4. Restore the problem Exchange database using the last available backup or repair it using Eseutil commands.

Running Eseutil commands for corrupted Exchange database is not safe as the resultant database can be out of some important data. For safe MS Exchange Repair, it is however, recommended to use a commercial application. These Exchange Repair software can scan and restore the affected database without harming the original integrity of database.

Exchange Server Repair Tool is an advanced EDB Repair utility that repairs corrupted Exchange databases and restores the mailboxes in separate *.pst files. The MS Exchange Repair tool supports Exchange Server 2007, 2003, 2000, and 5.5. With deleted mailbox feature, the tool can also recover the STM file data in the body of an e-mail message.