Corruption may creep into the database of Exchange Server system anytime, which results in many hardware or firmware related issues. Oftentimes, firmware upgrades, controller issues, memory upgrades or failures, etc. lead to problems within the storage subsystem. Also, it brings to a checksum mismatch error in Exchange Server during the particular page verification in Windows 10, 8, 7 OS.
At the time using Microsoft Exchange Server 2007, 2010, 2013, 2016, and 2019, users and administrator may face multiple numbers of errors. Exchange Server creates a log file to resolve these errors. Event ID 474 and 705 errors are very common problems in Exchange. Hence, we will give you an idea how to troubleshoot checksum mismatch error and data defragmentation issues creates by event id 474 and 705 in Exchange server. First, we will talk about the events in short and then move towards the remedial solutions.
Generally, Exchange creates event id 474 error due to hardware issues. This error is also known as Exchange error code 1018 i.e page checksum mismatch error in Exchange. It means that error 474 arises when a particular page of Exchange database is corrupted or damaged. It also occurs when database page verification has been failed.
Event ID: 474
Description: Information store “2680” the database page read from the file “~\mdbdata\priv1.edb” at offset 4050944 (0x00000000003dd000) for 4096 (0x00001000) bytes failed verification due to a page checksum mismatch error.’
There are following situations where you may be suffering from Exchange error ID 474 ESE issue.
Fixing Exchange event id 474 Database Page Cache issue can be done by using two methods:
You can resolve the Event ID 474 with the help of Eseutil and Isinteg commands. But, before performing the resolving steps, you should take a backup of the .edb database either in a healthy or corrupt state and dismount database Exchange 2016, 2013, 2010. Now, follow the steps to run the commands:
Eseutil /p C:\Program files\Exchsvr\mdbdata\ primary name.EDB
Eseutil /d C:\Program files\Exchsvr\mdbdata\ primary name.EDB
Isinteg –s {Exchange Server name}-fix-test all tests
Eseutil /g C:\Program files\Exchsvr\mdbdata\ primary name.EDB
If you are still facing the error, then you can try another method to fix this problem.
When MS Exchange online database defragmentation stops unexpectedly untimely due to any error, Exchange Event ID 705 occurs. This event id works as a signal that shows the ESE database or Microsoft Exchange store memory is having some issues. Nevertheless, when the data defragmentation is started again, it resumes from the disruption point.
There can be various reasons behind this Exchange error message 705:
In order to fix the online defragmentation error in Exchange, you need to transfer all mailboxes to another location. To do this, you can follow the same steps that are discussed in the above section. You can also create a new mailbox database and then try to move the affected database. After that, you should check the Exchange database whether it is still generating an error message or not.
In case, if you are still facing the page checksum mismatch error in Exchange, then you can use the SysTools Exchange Database Recovery tool to resolve the Event ID 474 and 705 errors. Because this advanced recovery manager for Exchange database tool offers many outstanding features like quick and advanced scan mode to recover corrupted Exchange database file and repair Exchange mailbox. After repairing defected files of Exchange database, you can easily move the recovered mailboxes it to the Live Exchange Server 2016/2013/2010/2007/2003 mailboxes without any cost of data loss.
In this post, we have discussed the page checksum mismatch error in Exchange Server or event id 474 and 705 error. Here, we have given the complete idea about these both errors and also discussed the reliable solutions to fix these event ids. If users still face the issues after performing the manual methods, then they can try an alternate third-party solution like Exchange File Recovery tool.