An Exchange Server administrator knows the importance of mailbox store. It contains multiple user mailboxes which hold critical information which is crucial for the normal work flow. The information is stored in the form of EDB format. It is quite clear that safety of these files cannot be compromised. Still we encounter wide range of errors in case of crucial EDB files. Let us checkout some practical scenarios where we alight upon such situations.
Event ID: 1148:-
Regular occurrence of this event is termed as “ A rule synchronization error (Read verification error)”.
Cause:
• Exchange database corruption is the main cause of this error.
• Also occurs if desired data is not present in the database.
Solution:
• Run application 'Eseutil'.
• Perform restore on the database from the created backup.
• Do create new backup as it will prevent data loss.
• Again run 'Eseutil/p' to perform repair on the database.
Event ID: 1120 and 5000:-
It shows inconsistent state of the database.
Cause:
• When hard recovery operation is performed on Priv.edb file to fix errors.
• The previous transaction log files are deleted.
• Unable to perform hard recovery for Pub.edb files.
Solution:
• Delete Pub.edb file but be careful with Edb.log file as it is required by Priv.edb.
• Perform 'Eseutil' with /p switch for hard recovery of Pub.edb file.
Event ID: 1018:-
The error is displayed as “Database page read failed verification due to error 1018” or page checksum mismatch.
Cause:
Certain page checksum mismatch means some individual file like Prive1.edb is corrupt.
Impact:
• Halts sending or receiving of mails.
• Unable to start MS Outlook.
• Online backup fails and displays 1018 checksum error.
• After performing online defragmentation the report generates 1018 checksum mismatch error.
Solution:
• Perform system diagnostic test.
• Try another system with different hardware.
• Update disk controller BIOS and firmware.
• Perform Eseutil/p and eseutil/d and isinteg-fix to repair Edb file.
If the aforementioned steps are unable to repair EDB files then it is advisable to choose third party EDB to PST Converter tool.
Stellar EDB to PST Converter is one such tool that can transform EDB to PST file. The user can easily understand through demo version that how simple is the interface of the software. It allows the user to perform the task smoothly and effectively. The conversion process is possible in both on/off-line mode. Beside conversion it can also recover accidentally deleted EDB files. The tool is widely compatible with nearly all the major versions of MS Exchange. The tool also allows users to perform conversion on selected EDB files. It can also convert EDB files into PST, EML and MSG format.
Event ID: 1148:-
Regular occurrence of this event is termed as “ A rule synchronization error (Read verification error)”.
Cause:
• Exchange database corruption is the main cause of this error.
• Also occurs if desired data is not present in the database.
Solution:
• Run application 'Eseutil'.
• Perform restore on the database from the created backup.
• Do create new backup as it will prevent data loss.
• Again run 'Eseutil/p' to perform repair on the database.
Event ID: 1120 and 5000:-
It shows inconsistent state of the database.
Cause:
• When hard recovery operation is performed on Priv.edb file to fix errors.
• The previous transaction log files are deleted.
• Unable to perform hard recovery for Pub.edb files.
Solution:
• Delete Pub.edb file but be careful with Edb.log file as it is required by Priv.edb.
• Perform 'Eseutil' with /p switch for hard recovery of Pub.edb file.
Event ID: 1018:-
The error is displayed as “Database page read failed verification due to error 1018” or page checksum mismatch.
Cause:
Certain page checksum mismatch means some individual file like Prive1.edb is corrupt.
Impact:
• Halts sending or receiving of mails.
• Unable to start MS Outlook.
• Online backup fails and displays 1018 checksum error.
• After performing online defragmentation the report generates 1018 checksum mismatch error.
Solution:
• Perform system diagnostic test.
• Try another system with different hardware.
• Update disk controller BIOS and firmware.
• Perform Eseutil/p and eseutil/d and isinteg-fix to repair Edb file.
If the aforementioned steps are unable to repair EDB files then it is advisable to choose third party EDB to PST Converter tool.
Stellar EDB to PST Converter is one such tool that can transform EDB to PST file. The user can easily understand through demo version that how simple is the interface of the software. It allows the user to perform the task smoothly and effectively. The conversion process is possible in both on/off-line mode. Beside conversion it can also recover accidentally deleted EDB files. The tool is widely compatible with nearly all the major versions of MS Exchange. The tool also allows users to perform conversion on selected EDB files. It can also convert EDB files into PST, EML and MSG format.
No comments:
Post a Comment