How to Solve Event 413 in Exchange Server?
February 23rd, 2010 | by admin |Axel Culver asked:
An Exchange Server database might fail to mount if it is inconsistent. In such cases, you can use Exchange utilities to repair them. However, if it fails to perform the repair, you need to use your backup or scan the database using an efficient Exchange Repair software.
For an instance, consider that you try mount a Microsoft Exchange Server database, but it fails and an error message displays with ID no. C1041724. When you view the application log, you come across the following event:
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 413
Description: Information Store (3932) First Storage Group: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1811.
Cause
There can be several reasons for this error to occur:
The Exchange log file has been deleted or quarantined by an antivirus application
You run eseutil /p command on the database, but the log file doesn’t get removed
Exchange log file has a mismatching LGeneration and signature
You run eseutil /r command with incorrect logfile base name
Solution
Corresponding solutions to the given problem are as below:
If the Exchange log file has been deleted, you need to use your Storage Group database backup to restore and replay the log files. If restoring from backup is not feasible, you should repair it using database repair utilities or a third-party application to make the database back to consistent state.
If the Exchange log file has been quarantined, you should recover it to the folder containing your production log files and start Microsoft Exchange Information Store service.
Move the transaction log files to a different folder if running eseutil /p command is the issue, while making sure that the databases are consistent. If the databases are inconsistent, restore them from backup or apply a third-party tool to repair them.
Use the correct switch to run eseutil /r command successfully.
If the database is consistent and you cannot repair it using Exchange utilities or restore it from backup, you need to perform Exchange Server Repair using a powerful third-party tool. Exchange Repair Tool use high-end repair algorithms to repair and restore a damaged Exchange database in all cases.
Stellar Phoenix Mailbox Exchange Recovery is a reliable and advanced MS Exchange Repair tool that repairs and restores a damaged Exchange database. It supports Exchange Server 5.5, 2000 and 2003. It is a non-destructive Exchange Server Repair tool providing impressive features and options. The tools enables to restore all user mailboxes together with unchanged contents.
Stainless Steel Paint
An Exchange Server database might fail to mount if it is inconsistent. In such cases, you can use Exchange utilities to repair them. However, if it fails to perform the repair, you need to use your backup or scan the database using an efficient Exchange Repair software.
For an instance, consider that you try mount a Microsoft Exchange Server database, but it fails and an error message displays with ID no. C1041724. When you view the application log, you come across the following event:
Event Type: Error
Event Source: ESE
Event Category: Logging/Recovery
Event ID: 413
Description: Information Store (3932) First Storage Group: Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1811.
Cause
There can be several reasons for this error to occur:
The Exchange log file has been deleted or quarantined by an antivirus application
You run eseutil /p command on the database, but the log file doesn’t get removed
Exchange log file has a mismatching LGeneration and signature
You run eseutil /r command with incorrect logfile base name
Solution
Corresponding solutions to the given problem are as below:
If the Exchange log file has been deleted, you need to use your Storage Group database backup to restore and replay the log files. If restoring from backup is not feasible, you should repair it using database repair utilities or a third-party application to make the database back to consistent state.
If the Exchange log file has been quarantined, you should recover it to the folder containing your production log files and start Microsoft Exchange Information Store service.
Move the transaction log files to a different folder if running eseutil /p command is the issue, while making sure that the databases are consistent. If the databases are inconsistent, restore them from backup or apply a third-party tool to repair them.
Use the correct switch to run eseutil /r command successfully.
If the database is consistent and you cannot repair it using Exchange utilities or restore it from backup, you need to perform Exchange Server Repair using a powerful third-party tool. Exchange Repair Tool use high-end repair algorithms to repair and restore a damaged Exchange database in all cases.
Stellar Phoenix Mailbox Exchange Recovery is a reliable and advanced MS Exchange Repair tool that repairs and restores a damaged Exchange database. It supports Exchange Server 5.5, 2000 and 2003. It is a non-destructive Exchange Server Repair tool providing impressive features and options. The tools enables to restore all user mailboxes together with unchanged contents.
Stainless Steel Paint
