| Event Id | 413 |
| Source | ESE |
| 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. |
| Event Information | According to Microsoft: CAUSE: Error 1811 corresponds to JET_errFileNotFound. This issue may occur in an Exchange log file that has a mismatching signature and LGeneration. Typically, the Exchange log file is the E00.log file. If the E00.log file has a mismatching signature, the information store might not mount even if the database is consistent. RESOLUTION: To resolve this issue, run the eseutil /mh command on all available databases in the corresponding storage group. If all databases are consistent, run the eseutil /ml command on the E00.log file. If there is a signature mismatch between the E00.log file and the recorded log signature in the database (eseutil /mh output), follow these steps: 1. Save your current log files. 2. Delete the E00.log file. When you mount the information store, a new E00.log file that has the correct signature and LGeneration is generated. 3. If you still cannot mount the information store, delete all transaction logs. These files include the Exx.log files and the Exxnnnnn.log files. |
| Reference Links | The Exchange database store may not mount in Exchange Server 2003 or in Exchange 2000 Server, and event IDs 9175, 486, 455, 413, and 5 may be logged |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.