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