Long-running MAPI 'SaveChangesMessage' 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: 2006-11-22
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 SaveChangesMessage operations that have taken longer than 30 seconds to be completed.
The MAPI SaveChangesMessage operation is called when an application is saving the content and or the properties of a message to the server. The time that is required to complete the operation depends on the data written, the speed of the database and the transaction log disks being written to, and whether a resource bottleneck is present.
If the Exchange Server Analyzer determines that a user-issued MAPI SaveChangesMessage operation has taken longer than 30 seconds, the Exchange Server Analyzer displays an error.
MAPI SaveChangesMessage operations taking longer than 30 seconds may not always be a problem. Saving large amounts of message data or file attachments could cause the MAPI SaveChangesMessage operation to take longer than normal. If the user or users are experiencing frequent delays, or delays that adversely affect their messaging experience, the most likely cause is a disk bottleneck.
For More Information
For more information about disk bottlenecks, see Disk Bottleneck Detected
For more information about Exchange Server performance, see the Exchange Server 2003 Performance and Scalability Guide (http://go.microsoft.com/fwlink/?LinkId=47576).
For more information about how to troubleshoot Exchange Server performance issues, see Troubleshooting Microsoft Exchange Server 2003 Performance (http://go.microsoft.com/fwlink/?LinkId=47588).
For more information about best practices for designing storage architectures, see Best Practices Common to Multiple Architectures (http://go.microsoft.com/fwlink/?LinkId=72988).
For more information about how to move user mailboxes to reduce server load, see Move User Mailboxes to Another Server.
For more information about disk sizing, latency, and I/O rates, see the following blogs on the Microsoft Exchange Team Blog Web site:
"A few basic concepts in disk sizing" (A few basic concepts in disk sizing (http://go.microsoft.com/fwlink/?linkid=39538)
"Some more thoughts on disk IO and calculations…." (http://go.microsoft.com/fwlink/?linkid=39539)
How to Calculate Your Disk I/O Requirements (http://go.microsoft.com/fwlink/?linkid=69747)