Similar to other software, occurrence of the error messages is not an exception in the Exchange Server. Few of them are indicative of the database corruption while few of them just show a mere malfunction, fixable through the simple procedures. But those which show the corruption in the Exchange server need a help of Exchange Server recovery and one of such log error is mentioned below:
Event ID: 23
Source: EDB
Type: Error
Category: Database Page Cache
Description: MSExchangeIS ((455)) Direct read found corrupted page error -1018 ((1:251563) (0-2295758), 251563 379225672 381322824). Please restore the database from a previous backup.
This error message is related to the JET database operation, on which the MS Exchange Server like products has been built, which results into 1018 (JET_errReadVerifyFailure) error.
Root of the Problem
This problem is encountered when some transactions are made. During this the information store of the Exchange Server writes these transactions to a transaction log file prior to it is committed to the database. A value called page’s checksum value is calculated which is aimed to be written in the page header.
After this a request is made to the file system to write the data on the disk, which is again forwarded to the hardware device driver. An acknowledgement is sent to the file system then on completion of the job. At this point of time, if some hardware device driver or hardware is faulty then this may acknowledge a complete operation but in actual this may not have been done properly and thus leading to the database corruption.
The mentioned error message is a result of the un-matching of the checksum value of the page header to that being returned by the READ call, when some database operation related to reading the data is performed.
Solution
To combat the present situation, Microsoft has suggested to restore from the last backup or to use the Edbutil.exe utility. Some of the users may find it hard or even impossible to adopt the mentioned solution in case if the backup is not complete and the vulnerabilities attached to the incorrect usage of the utility. So the last option left out is to have exchange server recovery via the help of specialized software.
These software are termed as Exchange recovery software and perform the EDB repair without any regard to the cause of the corruption. The software run the most powerful algorithms to scan the corrupted EDB file and then end up at Exchange Server recovery at the maximum.
Stellar Phoenix Mailbox Exchange Recovery is the most developed and advanced utility which is applicable in each case of corruption. This EDB recovery software can be used for Microsoft Exchange Server 5.5, 2000 and 2003.
The software comes packed with an easy to use interface which makes the functioning of the software quite easier. You can have Exchange recovery for any type of messages, contacts, tasks and other Exchange Server objects.

