Long-running MAPI bulk operation

[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 taking longer than should reasonably be expected on a healthy Exchange server.

As part of its analysis, the Exchange Server Analyzer reviews the ExMon data for user-issued MAPI Bulk operations that have taken longer than 30 seconds to complete.

MAPI Bulk operations are operations that act on more than one object and are typically expensive (require many I/Os).

If the Exchange Server Analyzer determines that a user has had one or more MAPI Bulk operations take longer than 30 seconds, the Exchange Server Analyzer displays an error.

MAPI Bulk operations taking longer than 30 seconds may not always be a problem. If the user is acting on (copying, deleting, setting attribute flags, and so on) a thousand or more messages at one time, it could cause the MAPI Bulk operations to take longer than normal.

If the user or users are experiencing frequent delays, or delays that adversely affect their messaging experience, these MAPI Bulk operation delays should be investigated further to make sure they are not symptomatic of more serious latency issues such as resource bottlenecks or nested dependencies.

To address this error:

  • Consider using the ExMon tool to capture a larger data sample for the Exchange Server Analyzer to review. Because of the large volume of data generated by Exchange, we recommended that the data collection sample be kept to 30 minutes or less.

For more information, see the following Exchange Server resources: