Solution to tackle Exchange error 613, 455 and 467

Microsoft Exchange Storage Group is a vital portion of Exchange Server. It holds transaction log files, system files and Exchange database files. The Exchange mailbox store consist of Priv1.edb and Priv1.stm files. These files contains messages, attachments, tables and meta data of messages and other database objects. It is understood that Exchange Storage Group is very crucial and hence it becomes first priority for network administrators to protect it. But there are a number of events available that can harm Microsoft Exchange Storage Group despite of applying number of security checks.

Error: 613
Cause: The error mainly occurs when Exchange database gets corrupt either due to conflict with any application or because of hardware issue. The error 613 generally occurs when checksum values gets mismatched. It happens when backup process compares the checksum values in the page header.  
Solution: Replace the affected hardware and uninstall the conflicting application. If recent backup is available then perform restore. In the absence of backup perform Exchange Server Recovery using Ex-merge.

Error:455
Cause: There are various probable reasons behind the error. It can be due to corruption of Mailbox store. It can be due to performing soft recovery of database using Eseutil without using correct log-file base name. The installed anti-virus may have deleted Exchange Log file. 
Solution: In order to fix the issue following steps can be implemented:

• The user should run eseutil/r command to repair or restore it using recent backup.
• The user is advised to perform soft recovery using exact log file base name like e00, e01, e02 or e03.
• The anti-virus should be restricted from scanning Exchange Server directories. 

Error:467
Cause: The database is corrupted which causes hanging of JET engine, it happens because of inconsistent state of secondary index with related tables.
Solution: First locate the inconsistent database file, then follow the below mentioned steps:

• Dismount the corrupt database.
• Run eseutil/g to check database inconsistency.
• Run eseutil/d to fix the corruption.
• Again mount the database store.

However following aforementioned steps for respective errors might sort out the issue but user can avoid such troublesome issues by taking precaution like maintaining regular backup of Exchange file in PST format. It can be done by using third party EDB to PST converter tool.

Stellar EDB to PST Converter is a tool which can easily convert EDB file to PST file due to its excellent features & user friendly environment. It can work in both on/off-line mode & also while Exchange Server is active. Selective conversions are also possible & it also recovers accidentally deleted EDB mailbox that too in off-line mode. Another feature is that it is compatible with nearly all the versions of MS Exchange like 2010, 2007, 2003, 2000 and 5.5. Another thing to cheer is that its demo version is free to download from its respective website.