Resolving Error database Page Read Failed Verification Because Of No Page Data

Microsoft Exchange Server display a number of Exchange database related errors on regular basis

. Quite often these error messages make the routine schedule of network administrators and executives miserable. The situation worsens when administrators have to deal with data loss comprising of entire EDB database. Administrators come across these critical data loss situations when the Exchange Server database (EDB) files face corruption issues.

EDB file might get damaged or corrupt due to number of reasons such as malicious virus, physical damage to your storage media, improper server shutdown etc. When Exchange Server database (EDB) file gets damaged, MS Outlook cannot access users email, calendars etc from it which further makes the situation difficult to handle. The communication amongst the users halts and might cause delay in scheduled projects as information related to projects cannot be shared.

In order to restart the information sharing and communication, administrators have to perform Exchange disaster recovery and rebuild the Exchange database which might result in data loss. Corrupt Exchange Server database wont mount and will stop. However, if you perform Exchange disaster recovery using eseutil utility to perform EDB repair, your EDB file might just mount. If this utility fails too, then you will be compelled to use the updated backup of the file so that you can restore your data from the backup file. But if somehow the backup option doesnt works for you and you come across the following error message:

Database page read failed verification because of no page data.

The situation further suggests that you have to move the present EDB database to a new hardware. The error is logged with event 376 in application event log. The above mentioned error clearly depicts that the database read operation has failed. The chief reason behind the occurrence of the above mentioned error message are mentioned below:

A particular database page that has been referenced here within the EDB database is supposed to be in use, but EDB finds it empty or uninitialized.

EDB file is corrupt and so it is mapping some pages into database which are actually not related to it

This page might have failed the checksum test with error-1018. But the page number field in use is 0x00000000, the checksum failed page will show -1019 error instead.

Logical links or pointers between database pages were not right

Event 476 can be associated with -1018 error which indicates checksum mismatch and is caused generally due to hardware issues. Check your system for related hardware issues if the database corruption still haunts you, replace the hardware and upgrade your firmware/ disk controller. Repair your Exchange database using Exchange disaster recovery software and get rid of corruption.

by: Articlechamp

POST COMMENT

Los Siete Errores Capitales En Escritura Los 4 Mejores Software Para Dj's Profesionales What Inventory Tracking Software Can Do For You 10 Successful Testing Tips for Offshore Software Development Company Spybubble-mobile tracking software Bookmarking Demon: What Kind Of Software Is It? Guidance Software GD0-100 Exam Solving The Challenges Of Offshore Software Application Development Try with the Excellent Software Training Kerala Rigpsnap.dll Error Solution for Fixing Rigpsnap.dll Error And Speed Up PC What is SharePodLib.dll Error And How to Fix SharePodLib.dll Error Swiss-Indian Software Development How to Fix Runtime Error 235 instantly And Avoid it for ever