Faulty hardware is one among the most common causes of Exchange Server database corruption.
If your application event log frequently records events that point to database damage issues, your hardware is most likely to be replaced.
Such situations however, demand Exchange Server Recovery tools to correct the issue.
Let's elucidate the related problems by taking a suitable example of following event ID.
-Event Type: Error -Event Source: ESE -Event Category: Database Page Cache -Event ID: 476 -Date: date -Time: time -User: user_name -Computer: computer_name -Description: Affected_Component The database page read from the file "file_name" at offset offset for number_bytes bytes failed verification because it contains no page data.
The read operation will fail with error error_number.
If this condition persists then please restore the database from a previous backup.
This problem is likely due to faulty hardware.
Please contact your hardware vendor for further assistance diagnosing the problem.
Event 476 is linked with a -1019 error in the event log.
Cause Database read operation has failed.
Particularly, this indicates that the specified database page that has been mentioned in database file, for example pub1.
edb, is empty and has no data when it is being anticipated to be in use.
Error -1019 corresponds to 'JET_errPageNotInitialized' or an empty database page.
This can occur due to invalid links between database pages, file system inconsistencies, or pages that have been mapped but are not associated with the database file.
Though ordinary hardware diagnostics might fail to detect the problems, but most of these issues happen because of device drivers, firmware, and hardware related concerns.
Solution Get the new hardware and use one of the below methods: 1.
Use Move Mailbox tool by installing another server and move all the mailboxes 2.
Run Exmerge utility to obtain all mailboxes as *.
pst files 3.
Restore the database from backup 4.
Repair the database using Eseutil/p and Isinteg -fix commands 5.
Use a third-party Exchange Recovery tool Note: A third-party Exchange Server Recovery application is more safer than Exchange hard repair utility- Eseutil/p.
The latter utility can delete the database pages and cause serious data loss.
If your application event log frequently records events that point to database damage issues, your hardware is most likely to be replaced.
Such situations however, demand Exchange Server Recovery tools to correct the issue.
Let's elucidate the related problems by taking a suitable example of following event ID.
-Event Type: Error -Event Source: ESE -Event Category: Database Page Cache -Event ID: 476 -Date: date -Time: time -User: user_name -Computer: computer_name -Description: Affected_Component The database page read from the file "file_name" at offset offset for number_bytes bytes failed verification because it contains no page data.
The read operation will fail with error error_number.
If this condition persists then please restore the database from a previous backup.
This problem is likely due to faulty hardware.
Please contact your hardware vendor for further assistance diagnosing the problem.
Event 476 is linked with a -1019 error in the event log.
Cause Database read operation has failed.
Particularly, this indicates that the specified database page that has been mentioned in database file, for example pub1.
edb, is empty and has no data when it is being anticipated to be in use.
Error -1019 corresponds to 'JET_errPageNotInitialized' or an empty database page.
This can occur due to invalid links between database pages, file system inconsistencies, or pages that have been mapped but are not associated with the database file.
Though ordinary hardware diagnostics might fail to detect the problems, but most of these issues happen because of device drivers, firmware, and hardware related concerns.
Solution Get the new hardware and use one of the below methods: 1.
Use Move Mailbox tool by installing another server and move all the mailboxes 2.
Run Exmerge utility to obtain all mailboxes as *.
pst files 3.
Restore the database from backup 4.
Repair the database using Eseutil/p and Isinteg -fix commands 5.
Use a third-party Exchange Recovery tool Note: A third-party Exchange Server Recovery application is more safer than Exchange hard repair utility- Eseutil/p.
The latter utility can delete the database pages and cause serious data loss.
Source...