While recovery or a database restore operation, Microsoft Exchange Server reads the database pages. The application replays the transaction lof files, while keeping them coordinated with database pages. During these operations, Exchange Server ensures that the logical page number and check sum values of all the database pages are correct. If a database page cannot be read for any of these issues, Exchange Server fails to recover or restore the database and reports errors in its application log. In such situations, this is essential that you should have a valid data backup or otherwise, it might require you to perform exchange server recovery using different utilities. Microsoft Exchange Server can detect the file-level corruption that might occur to database pages. To support the fact, we'll now take an associated example. Suppose you, as an Exchange Server administrator, try to start the Information Store when it starts recovering. But the process fails and you receive the below error logging in its application log: Event Type: Error Event Source: ESE Event Category: Logging/Recovery Event ID: 419 Date: date Time: time User: user_name Computer: computer_name Description: Information Store (num) Restore0003: Unable to read page page_num of database E:ExchsrvrMdbdataStoreAMailbox file_name.edb. Error err_num The actual cause of the error message can be determined by the err_num, which displays in the description section of the above event. It can be -1018 ( JET_errReadVerifyFailure), -1019 (JET_errPageNotInitialized), or -1022 (JET_errDiskIO). Cause Error -1018, -1019, and -1022 indicate file system level damage and occurs because of an underlying system, on which Exchange Server depends. Solution Following are troubleshooting steps to resolve this event: You need to diagnose the firmware and device driver issues in your computer. Contacting your hardware vendor might help. You should restore the database from a healthy backup or in its absence, apply Exchange Server Eseutil and Isinteg utilities ot third-party exchange recovery software to repair the corrupted database. In comparison to Exchange Server Eseutil repair utilities, the commercial exchange server recovery tools are more effective and safer. Also, these utilities are competent to restore the database contents to a secure location. If you can mount the database, use ExMerge utility to move all the mailboxes to a new, blank database and delete the corrupted database. But if you cannot mount the database, restore from the last online backup, run Eseutil /p repair, or apply a third-party exchange server recovery utility. Unlike Exchange Eseutil repair utility, an exchange recovery software can scan and repair the corrupted database using safe procedures. Stellar Phoenix Mailbox Exchange Recovery is a comprehensive repair solution for corrupted Exchange databases. This Exchange Recovery tool supports MS Exchange Server 5.5, 2000, 2003, and 2007 and creates individual *.pst files for restoring the mailbox data. With a simple interface, this software can restore all e-mails, notes, contacts, calendars, etc.
Please Rate this Article 5 out of 54 out of 53 out of 52 out of 51 out of 5
Not yet Rated
