Topic Last Modified: 2010-02-15
The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.
To learn more about this alert, in Operations Manager, do one or more of the following:
- From the Operations Console, double-click this alert, and then
click the General tab. Review the description of the alert
that includes the variables specific to your environment.
- From the Operations Console, double-click this alert, and then
click the Alert Context tab. Review the logged events that
meet the criteria of this Operations Manager alert.
Details
Product Name |
Exchange |
Product Version |
14.0 (Exchange 2010) |
Event ID |
7010 |
Event Source |
MSExchangeTransportLogSearch |
Alert Type |
Warning |
Rule Path |
Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Transport Log Search |
Rule Name |
The Microsoft Exchange Transport Log Search service failed to access a log file due to an I/O error. |
Explanation
This Error event indicates that the Microsoft Exchange Transport Log Search service experienced an I/O exception while trying to access the specified directory.
The Microsoft Exchange Transport Log Search service is used by the Get-MessageTrackingLog and Search-MessageTrackingReport cmdlets in the Exchange Management Shell, the Delivery Reports tool in the Exchange Control Panel, and the Tracking Log Explorer tool in the Exchange Management Console to search the message tracking logs on the Hub Transport server, Edge Transport server, or Mailbox server.
The location of the message tracking logs is controlled by the MessageTrackingLogPath parameter on the Set-TransportServer cmdlet or the Set-MailboxServer cmdlet. By default, the message tracking logs are located at C:\Program Files\Microsoft\Exchange Server\V14\TransportRoles\Logs\MessageTracking.
An I/O exception can be caused by any of the following conditions:
- Problems with the physical hard disk drive
structure This condition could include the
hard disk drive itself or the hard disk drive controller.
- Problems with the logical disk
structure This condition could include file
system errors or corruption.
- Transient software errors This
condition could include intense periods of read and write activity
on the hard disk drive.
User Action
To resolve this error, do the following:
- Verify that the drivers and firmware for the hard disk drives
and the hard disk drive controller are up to date.
- Run the command CHKDSK drive letter: /F /R. This command
finds and repairs physical errors and file system errors on the
affected hard disk drive.
- Move the message tracking log directory to another hard disk
drive.
For more information about managing message tracking logs, see Configure Message Tracking.
For More Information
If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.