Resolve Exchange Event ID 474 and 705 Error – Fix Corruption & Page CheckSum Issue

About Event ID 475 and 707 In Exchange Server

While using different versions of Exchange Servers such as 2007, 2010, 2013 and 2016, users and Administrator can face multiple numbers of errors. Exchange Server creates a log file of errors that help users to fix the issues. We have seen a number of people searching for information related to Event ID 474 and 705 that occur on Exchange Server 2007 and other Exchange Versions. 

To address these user's queries, we have decided to discuss these events in this post. First of all, we will talk about the events in brief and then move to the remedial methods. Continue reading to know why event id 474 generated in Exchange 2013, 2010, 2007 and below accounts and 705 occur and what the solutions to these event ids are.

About Exchange ESE Event ID 474 Error

The event ID 474 is also known as Exchange error code 1018 (page checksum mismatch.) Hardware issues are mostly responsible for this event. This event error code signifies a situation when a particular Exchange database page that has been referenced is damaged or corrupt. This corruption leads to event id 474 checksum mismatch value error with Category of Database Page Cache,i.e., database page verification has been failed. In some cases, database pages remain healthy and in those cases, users get the message that the error is not caused by corrupt database page, rather by firmware malfunction.

The trait of Event Id 474 ESE Error In Exchange 2010, 2013, 2016 Server

Whenever a user starts facing give below issues in Exchange Seve, you may be suffering from Error ID 474 ESE issue.

• Inability to send or/and receive emails
• Outlook not starting on the client system
• Getting 474 error during Online Defragmentation
• Online backup does not finish and shows Event Id 474 error message in Exchange.

Fix Event Id 474 Database Page Cache Via ESEUTIL Commands of Exchange

There are two solutions to this error event id 474. The first solution is to use eseutil and isinteg commands. The second remedial option is to move the corrupted mailbox of Exchange. We will learn about both these solutions in section below.

Resolve Exchange Event ID 474 by using Built-in Eseutil Utilities Commands

To resolve this error, we will use eseutil and isinteg commands. Before you perform these steps, be sure to take backup of EDB Database (either healthy or corrupt) and dismount data from the server. Follow the steps to execute the commands:

• Click on Windows+R keys together on the machine.
• Run dialog box will open. Write cmd in the box and Press Enter.
• Type “C:\Program Files\Exchsrvr\bin” in the command prompt to find out eseutil.exe on your system.
• Once you have located eseutil.exe, run this command to fix major Exchange corruptions:

Eseutil /p C:\Program files\Exchsvr\mdbdata\ primary name.EDB

• After the corruptions are repaired, defragment the database by running this under command:

Eseutil /d C:\Program files\Exchsvr\mdbdata\ primary name.EDB

• Now, close the command prompt. Then open eseutil again and run this command to check the integrity weaknesses:

Isinteg –s {Exchange Server name}-fix-test all tests

• Now verify if the database has some specific inconsistencies by running this command:
  
  

Eseutil /g C:\Program files\Exchsvr\mdbdata\ primary name.EDB

Above commands helps to fix Event ID 474 Issues, If this method does not work, you can apply another method of moving Corrupted Mailbox.

Resolve Exchange Error Event 474 by Moving Mailboxes

This is another way to fix this problem. Users have to use Exchange Management Console to move the mailbox.

• To begin with, you have to launch Exchange Management Console.
• There will be a console tree, from which you have to expand Recipient Configuration option. Then click on Mailbox.
• Select the mailbox(es) you wish to move by clicking on them.
• Click on Move Mailbox from the action pane.
• Move Mailbox Wizard will open on the screen. On the first page, you have to select the server, storage group, and destination mailbox database. Click on Next.
• On the next page named “Move Options”, choose how the corrupt mailbox messages will be handled and click Next.
• On the page called “Move Schedule”, specify the time of the move and click Next to continue.
• Confirm all information regarding mailbox move by checking the summary on “Move Mailbox” page.
• Click Finish on the final page. Your mailbox will be successfully moved to some other location.

Event Id 705 - Online Defragmentation Error In Exchange

Exchange Event ID 705 occurs when an online database defragmentation ends unexpectedly and untimely due to some error. In other sense, it is a signal that ESE database or Exchange store memory is having some problems. However, when the data defragmentation process is started again, it resumes from the point of disruption.

Causes: Whenever Event ID 705 Generated, a code is also listed with the error, Check out the error codes of event 705 to know its actual causes.

Error -1069 (0xfffffbd3):Jet_errVersionStoreOutOfMemory: Exchange Server is out of memory. This error code deals with space memory for the Defragmentation process. 

Error -327 Jet_errBadPageLink & Error -338 Jet_errBadParentPageLink: B-Tree contains a bad page link, i.e., there is a database corruption at the Jet level. 

Error -1018 or Jet_errReadVerifyFailure: It means a checksum error exists on a database page. It may also indicate ESE level database corruption. Hardware, controller & problems related to hardware file system level are responsible for this error code.

Manual Solution to Resolve Event ID 705 Error In Exchange Server

To Fix this issue, you can try to move all the mailboxes to another location using the above steps mentioned in above section. Create New Mailbox Database and try to move back the affected database and check whether still you are facing the same issue or not. 

If after all these steps you are not able to repair the Database then you can try SysTools Exchange Recovery Tool to fix this event ID error. The tool includes Quick and Advance Scan Mode to repair Corrupted or Damaged Exchange EDB Database File of 2016,2013, 2010 and below versions. After you remove all the corruptions from your Exchange Server, you can move the database to Live Exchange Server without any data loss.

Conclusion

The post has attempted to resolve Exchange Server 2007 event id 474 and 705. Our aim has been to inform the users elaborately regarding these two error messages. Hopefully, readers will be able to solve these issues by implementing the approaches mentioned here.