How to Solve Event 413 in Exchange Server?

An Exchange Server database might fail to mountbase name
if it is inconsistent. In such cases, you can useSolution
Exchange utilities to repair them. However, if itCorresponding solutions to the given problem are
fails to perform the repair, you need to use youras below:
backup or scan the database using an efficientIf the Exchange log file has been deleted, you
Exchange Repair software.need to use your Storage Group database
For an instance, consider that you try mount abackup to restore and replay the log files. If
Microsoft Exchange Server database, but it failsrestoring from backup is not feasible, you should
and an error message displays with ID no.repair it using database repair utilities or a
C1041724. When you view the application log, youthird-party application to make the database back
come across the following event:to consistent state.
Event Type: ErrorIf the Exchange log file has been quarantined, you
Event Source: ESEshould recover it to the folder containing your
Event Category: Logging/Recoveryproduction log files and start Microsoft Exchange
Event ID: 413Information Store service.
Description: Information Store (3932) FirstMove the transaction log files to a different folder
Storage Group: Unable to create a new logfileif running eseutil /p command is the issue, while
because the database cannot write to the logmaking sure that the databases are consistent. If
drive. The drive may be read-only, out of diskthe databases are inconsistent, restore them
space, misconfigured, or corrupted. Error -1811.from backup or apply a third-party tool to repair
Causethem.
There can be several reasons for this error toUse the correct switch to run eseutil /r command
occur:successfully.
The Exchange log file has been deleted orIf the database is consistent and you cannot
quarantined by an antivirus applicationrepair it using Exchange utilities or restore it from
You run eseutil /p command on the database, butbackup, you need to perform Exchange Server
the log file doesn't get removedRepair using a powerful third-party tool. Exchange
Exchange log file has a mismatching LGenerationRepair Tool use high-end repair algorithms to
and signaturerepair and restore a damaged Exchange database
You run eseutil /r command with incorrect logfilein all cases.