An error occurred while opening a log file
Topic Last Modified: 2007-11-16
The Microsoft Exchange Server 2007 Management Pack for Microsoft Operations Manager (MOM) monitors the Windows Application log on computers that are running Exchange Server 2007 and generates this alert when the event or events specified in the following Details table are logged.
To learn more about this event, do one or more of the following:
Review the description of the event that includes the variables specific to your environment. From the MOM Operator Console, select this alert, and then click the Properties tab.
Review all events that have been logged that meet the criteria of this MOM alert. From the MOM Operator Console, click the Events tab, and then double-click the event in the list for which you want to review the event description.
Details
Product Name |
Exchange |
Product Version |
8.0 (Exchange Server 2007) |
Event ID |
455 |
Event Source |
ESE |
Alert Type |
Warning |
MOM Rule Path |
Microsoft Exchange Server/Exchange 2007/Common Components/Extensible Storage Engine |
MOM Rule Name |
An error occurred while opening a log file. This may be caused by a permissions or hardware issue. Use the error listed in the Description to resolve this error. |
Explanation
This Warning event indicates that an unexpected error occurred during runtime. The error code in the event description provides information about the cause of the warning.
The most common error is -1811, which indicates the Jet_errFileNotFound error. The log file may be missing or there may be other causes for this error. For example, the E00.log file may have a mismatching signature between the log and the database. Another reason for error -1811 includes that the Exchange Database and log files may have been put on network storage, which is not supported. Also, the checkpoint file may be corrupt, or the log drive itself may have failed.
Another error you may receive may be -1032, which is the Jet_errFileAccessDenied error. In this case, the wrong NTFS permissions on the drive where the log exists may cause this error.
User Action
To resolve this warning, do one or more of the following:
If the error code is -1032, then check the permissions on the log file drive.
If the error code is -1811:
Check the system event log for indications of hardware problems. You may need to restore from backup if the problem is based on media failure.
Review Microsoft Exchange Server Analyzer article ESE 455 -1811 (0xfffff8ed): Missing Current (Exx.log) Transaction Log File.
For information about ESE error codes other than the ones explained in this topic, see the following Microsoft Knowledge Base articles:
For more detailed information on resolving both of the errors associated with event 455, see the Microsoft Knowledge Base.
For More Information
To search the Microsoft Knowledge Base articles based on criteria that generated this alert, visit the Search the Support Knowledge Base (KB) Web site.
To review Exchange 2007 event message articles that may not be represented by Exchange 2007 MOM alerts, see the Events and Errors Message Center.
If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.