How to Solve Event 465 in Exchange Server

An Exchange public store or mailbox store of a storage group can be mounted using Exchange Management Console or Exchange Management Shell. This makes the databases ready for use. For any reason, if the process fails, it leads to data inaccessibility. Database mount failure primarily suggests that one or more storage group components are faulty. However, if one or more databases are corrupted, you should use eseutil utility to repair it. Alternatively, you can apply the last good backup or use a powerful EDB Repair utility to repair the corrupted database.

For instance, suppose you try to mount public or mailbox store in Exchange Server. The operation fails and the application event log reports the below information message:

Event ID: 465

Source: Ese98 Type: Error Computer: Server1

Information Store (2184) Corruption was detected during soft recovery in logfile C: ProgramExchsrvrmdbdataE00000E8.log. The failing checksum record is located at position 6531: 471. Data not matching the log-file fill pattern first appeared in sector 6600. This logfile has been damaged and is unusable.

For more information, go

Error 465 is usually accompanied with error 477 that informs checksum mismatch and suggests you to restore the logfile from backup.


The prime cause of error 465 to occur is transaction log file corruption, specifically Edb00000E8.log file.


You should remove the corrupted log file to achieve recovery. To do so, you must first find out the storage group, which is affected from this corruption and then follow these steps:

  1. Dismount all the databases of affected storage group and perform its offline backup.
  2. Run eseutil / mh tool to make sure if the databases exist in consistent state.
  3. If all the databases report 'Clean Shutdown' state, move out all the log files from ExchsrvrMdbdata folder.
  4. But if databases exist in 'Dirty Shutdown' state, perform soft database recovery using eseutil / r
  5. On unsuccessful attempt of soft recovery, you can restore the database from last Exchange backup
  6. In cases when no valid backup is available, you can try repairing the database using eseutil / p , which performs hard repair.
  7. The hard repair of Exchange database causes corrupted pages to delete. Thus, it is suggested to use a third-party EDB Repair Tool for more effective and safe database repair. EDB Repairsoftware employ advanced scanning algorithms and provide you easy-to-implement user interface.

Contact Email Support Number
Contact Email Support Number
Contact Email Support Number
Contact Email Support Number

Article Source Link