Export (0) Print
Expand All
Expand Minimize

Log record bytes/sec beyond error threshold

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2007-01-23

The Microsoft® Exchange Server Analyzer Tool uses the Exchange Server User Monitor (ExMon) tool to determine whether user MAPI operations are performing as should reasonably be expected on a healthy Exchange server.

As part of its analysis, the Exchange Server Analyzer reviews transaction log usage to determine whether user MAPI operations cause more than 5MB per minute of data to be written to the Exchange transaction logs.

Excessive transaction log file growth from MAPI operations may cause server resource bottlenecks and errors such as checkpoint depth exceeded, disk I/O bottlenecks, and insufficient disk space.

If the Exchange Server Analyzer determines that one or more user MAPI operations cause more than 5MB of data per minute to be written to the Exchange transaction logs, the Exchange Server Analyzer displays an error.

MAPI operations writing more than 5MB of data per minute to the Exchange transaction logs is not always an issue. Writing at a high rate is expected for some actions, such as mailbox moves or other bulk operations against many messages that generate large amounts of transaction log data. In this case, high rates should not be sustained for more than a few minutes.

If the server is experiencing other issues such as high RPC latency, work with the user generating the transaction log data to determine what user activity is causing the high log record write rate.

For more information, see the following Exchange Server resources:

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft