Toll Free: +1 888 900 4529 |   Toll Free: +44 800 088 5522

How to Fix Cyclic Redundancy Check (CRC) Error of Exchange Backup File

wpedbtopst | November 24th, 2015 | general

This article gives you a summary of the CCR error that occurs in Exchange BKF files. The methods by which the error can be removed have also been mentioned.

Fixing Cyclic Redundancy Check Error of Exchange Backup File

Backup files serve a very important role when it comes to an application’s database. A backup file ensures that the application data will be secured even if the original data is hampered. Exchange BKF files, similar to other backup files, ensure that the Exchange server data will be kept secured even if the data residing in the main database files is compromised due to a disaster or database failure.


However, what proves to be drastic is the corruption of the Exchange BKF files. Once the backup files are corrupted, there exists no way by which the Exchange data can be recovered. Therefore, recovery of data from the BKF file is the last resort to get back the Exchange server database in a working condition.

There are many reasons due to which an Exchange BKF file may get corrupted, among which CRC or Cyclic Redundancy Error is the most common.

Cyclic Redundancy Check Error

CRC is one of the most common error checking mechanism used in data transmission. At the ends of the data transmission, a check is done on the Hexadecimal value of the entire 1’s present in the data stream. It determines the integrity of the data transmission by evaluating the lost or overwritten bites. This helps the user in checking the stability of the data stream.

The CRC error in the Exchange backup files are basically a result of absence of transaction log files or corruption in header files. Since, this error arises in log files. It gets a bit difficult to get hold of the issue.

Manual Utilities to Solve CRC Error

Since CRC error mainly occurs due to missing Log files, restoration of Exchange database is the only way with which the CRC error can be removed manually. There are two manual utilities, which can be used to repair corrupted Exchange BKF files:

1. Eseutility

Eseutility is an inbuilt tool that allows the offline defragmentation and runs integrity check on the Exchange database. In order to run the Eseutil command, the Exchange database should be dismounted from the Exchange server.

Location: Program Files\Exchsrvr\Bin

Follow the below mentioned steps to run the Eseutility:

  • In the search box, type cmd and press Enter.
  • In the command prompt, open
       Program Files\Exchsrvr\bin
  • Type Eseutil.
  • Enter the following command:

       C:\ Program Files\Exchsrvr\bin>Eseutil
Any of the two switches, /p or /r can be used for data recovery. The commands will look like:

Esseutil/p EDB Log File name

Esseutil/r EDB Log File nam

2. Isinteg

Once the Eseutility is used for the Exchange database, the Isinteg utility is used to fix the unresolved corruption issues of Exchange database files. Once the command is used, it detects all the errors in the corrupted Exchange database. It is to be noted that the command should be used until no error is reported in the database.

Location: Program Files\Exchsrvr\Bin.

The command used to run this utility is:

Isinteg –s Servername [-fix]


The above-mentioned manual solutions enable the users to recover data from Exchange BKF file. However, if some precautions are taken, there are chances that the Exchange backup file may not end up in getting corrupted. Saving the backup file at a location different than the one on which the original Exchange database resides, can serve to be a precautionary measure.

The following two tabs change content below.