Blogs >> Technology >>
Event Id 474 while accessing Exchange Server database
One of the most important objects of Microsoft Exchange that saves all
the database files and transaction logs is 'Information Store'. This
component, once corrupted, results in inaccessibility of all the
data/information saved in database. Few most common reasons for the
information store corruption are improper database shutdown, log file
damage, and anti-virus scanning. An easy way to access the information
store after its corruption is by using a complete backup. However, if
the backup is unavailable or corrupted, then you need to search for an
effective third-party Exchange Server Repair software.
As a practical case, you receive the underneath error messages while trying take a backup of your database files, using Veritas software:
“Information Store - is a corrupt file. This file cannot verify.”
On viewing the event log of your Exchange Server, you view the below error message:
“Source : ESE
Category : Database Page Cache
Event Id : 474
Description :
Information Store (2712) First Storage Group: The database page read from the file "E:\Exchange\mdbdata\priv1.edb" at offset 409464832 (0x000000001867f000) (database page 99966 (0x1867E)) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3567500155055337822 (0x31824e7d5639715e) and the actual checksum
was 3711585678364162506 (0x338233827852b9ca). The read operation will fail with error -1018 (0xfffffc06). 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.”
Resolution:
For complete resolution of the above error message and to access data, follow the below mentioned steps:
1. Firstly, take a copy of your raw database and run 'eseutil /p' to perform repair.
2. Now, take a backup of your repaired database and run 'eseutil /d' to defragment your database.
3. Next, take a backup of your defragmented database and run 'Isinteg -fix -test alltests' to check the integrity.
4. In case, you do not receive any error integrity checking, then run ntbackup on exchange server.
5.Lastly, try complete backup information store using the Veritas software.
However, if the information store remains corrupted even after following the above steps and you are still not above to perform database backup, then you need to repair the information store by using an effective Exchange Server Repair. An MS Exchange Repair software incorporates high-end scanning methods to repair corrupt Exchange EDB file.
Exchange Repair Software is an efficient MS Exchange Repair application that repairs corrupt Exchange EDB file(s) created with Exchange Server 5.5, 2000, 2003, and 2007. With recovery of deleted mailboxes, the read-only software saves repaired files in a .PST file format.
As a practical case, you receive the underneath error messages while trying take a backup of your database files, using Veritas software:
“Information Store - is a corrupt file. This file cannot verify.”
On viewing the event log of your Exchange Server, you view the below error message:
“Source : ESE
Category : Database Page Cache
Event Id : 474
Description :
Information Store (2712) First Storage Group: The database page read from the file "E:\Exchange\mdbdata\priv1.edb" at offset 409464832 (0x000000001867f000) (database page 99966 (0x1867E)) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch. The expected checksum was 3567500155055337822 (0x31824e7d5639715e) and the actual checksum
was 3711585678364162506 (0x338233827852b9ca). The read operation will fail with error -1018 (0xfffffc06). 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.”
Resolution:
For complete resolution of the above error message and to access data, follow the below mentioned steps:
1. Firstly, take a copy of your raw database and run 'eseutil /p' to perform repair.
2. Now, take a backup of your repaired database and run 'eseutil /d' to defragment your database.
3. Next, take a backup of your defragmented database and run 'Isinteg -fix -test alltests' to check the integrity.
4. In case, you do not receive any error integrity checking, then run ntbackup on exchange server.
5.Lastly, try complete backup information store using the Veritas software.
However, if the information store remains corrupted even after following the above steps and you are still not above to perform database backup, then you need to repair the information store by using an effective Exchange Server Repair. An MS Exchange Repair software incorporates high-end scanning methods to repair corrupt Exchange EDB file.
Exchange Repair Software is an efficient MS Exchange Repair application that repairs corrupt Exchange EDB file(s) created with Exchange Server 5.5, 2000, 2003, and 2007. With recovery of deleted mailboxes, the read-only software saves repaired files in a .PST file format.
|
|
