MAPI Operation Failures
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool has determined that the server has many reported MAPI failures. Some MAPI operations are expected to return errors occasionally. However, sometimes a client application may not respond to the error correctly. As a result, the application may reissue the RPC request that caused the error, thereby increasing the load on the server.
An example of a frequent client error is when a MAPI client requests a list of items in batches and continues to request the items after the request has been returned by Exchange. For example, a client computer may request all items in a given folder that contain an attachment. The client may further request that the items are returned in batches of 30 items each. In some cases, after the Exchange server has returned the last item in the request, the client will continue to request a new batch of 30 items. In these cases, Exchange returns a "Not Found" error. If the client computer continues to request items even after the "Not Found" error is returned, the client computer is not responding to the error correctly. In this scenario, Exchange Server User Monitor (ExMon) would report multiple MAPI failures. In this case, although the ratio of failures to number of operations is high, the high failure rate is expected. MAPI operations with expected high failure rates include, GetPerUserGuid, ImportMsgMove, and Logon.To correct this error
Use ExMon to determine which user or group of users is causing the high number of MAPI failures.
Determine what application on the client computer is causing this problem.
Fix or remove the application that is causing the problem.
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 troubleshooting Exchange Server performance issues, see Troubleshooting Microsoft Exchange Server 2003 Performance (http://go.microsoft.com/fwlink/?LinkId=47588).