Monday, January 31, 2011

How to Solve Event 217 and 478 In MS Exchange Server ?

Microsoft Exchange server has been using in small to large sized organization as the server side of e-mail communication systems. In case of Exchange Server crashes, storage groups and exchange databases that stores the data, are the most important component for recovery. When a corruption situation occur in database, You might observe some unexpected behavior. For example, you may not be able to backup it and the corresponding event which indicates the failure is logged in application event log file with the detail description of the cause. However, a damaged or corrupted Exchange database (.edb) file should be restored from the backup. But in the absence of backup, you need an effective Exchange Repair tool to repair and restore the same.

For example, suppose you try to perform an online backup of the ESG (Exchange Storage Group), the operation may fail and you might see the below events logging into application log:

Event 217:

Event Type: Error
Event Source:ESE
Event Category:Logging/Recovery
Event ID: 217
Time:10:21:32 PM
Information Store (5484) First Storage Group: Error (-613) during backup of a database (file drive:\Program Files\Exchsrvr\mdbdata\priv1.stm). The database will be unable to restore.

Event 478:

Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 478
Time:10:21:32 PM
User: N/A
Computer: EXCHANGE
Information Store (5484) The streaming page read from the file "drive:\Program Files\Exchsrvr\mdbdata\priv1.stm" at offset 7250493440 (0x00000001b029c000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 2914298788 (0x00000000adb4aba4) and the actual checksum was 4278044063 (0x00000000fefdc59f). The read operation will fail with error -613 (0xfffffd9b). If this condition persists then please restore the database from a previous backup.


Event 217 in Exchange Server illustrates backup failure and event 478 exihibits the corruption in database. Event 217 might also be occured because of "beyond end of file (EOF)" condition.


Make sure all the hotfixes and latest updates are available for your Exchange Server. In order to solve the database corruption issue, you need to perform following steps:

1. Restore the Information Store database, using last online backup
2. Attempt to transfer user mailboxes to another store, if you are using Enterprise edition of Exchange Server 2000 or 2003
3. If above solution doesn't works, try to repair the exchange database by executing eseutil /p repair command followed by eseutil /d command to defragment the database. But these command line utility deletes the pages that it encounters as corrupted. For safe MS Exchange repair, you should run EDB Repair tool that uses safe and advanced algorithms to repair and restore damaged Exchange databases.

The interface of these Exchange mail repair utilities are simple and easy to use that provides complete Exchange Server Repair results. You just need to browse or search the corrupt .edb (exchange database) file and the tool scans the damaged file entirely to repair it.

Stellar Exchange Repair is a powerful tool that provides systematic MS Exchange Server repair. It is a secure EDB Repair Software that supports Exchange Server version 2010, 2007, 2003, 2000 and 5.5. This Repair Exchange tool saves the repaired and recovered exchange mailboxes in individual .pst files, which can be directly accessed in MS Outlook. Thus the software also works as EDB to PST Converter and efficiently repairs the corrupt edb file in all corruption scenarios.

No comments:

Post a Comment