Article ID: 2674185 - View products that this article applies to.
Consider the following scenario:
Note By default, the RPC Client Access log is located in the following folder:
Exception of type 'Microsoft.Exchange.RpcClientAccess.BufferTooSmallException' was thrown.
C:\Program Files\Microsoft\Exchange Server\V14\Logging\RPC Client Access
This issue occurs because the Exchange server returns an ecBufferTooSmall response that the MAPI application cannot handle to a sequence of remote operations. The ecBufferTooSmall response is generated because the Exchange server detects that the sequence of remote operations may cause a potential loop between the server and the MAPI application. Therefore, the read stream operation fails with the MAPI_E_CALL_FAILED error.
To resolve this issue, install the following update rollup:
2685289After you apply this update rollup, the Exchange Server 2010 server returns the ecBufferTooSmall response only if the following conditions are true:
(http://support.microsoft.com/kb/2685289/ )Description of Update Rollup 3 for Exchange Server 2010 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about random MAPI_E_CALL_FAILED errors in Exchange Server 2010, go to the following MSDN website:
Random MAPI_E_CALL_FAILED errors in Exchange Server 2010For more information about the MAPI function in Outlook 2010, go to the following Microsoft website:
General information about the MAPI function in Outlook 2010For more information about the MAPI function in Outlook 2007, go to the following Microsoft website:
General information about the MAPI function in Outlook 2007For more information about the RopReadStream remote operation, go to the following Microsoft website:
General information about the RopReadStream remote operation
Article ID: 2674185 - Last Review: June 5, 2012 - Revision: 3.0