Calling RpcAsyncCancelCall function breaks connection and causes MAPI_E_NETWORK_ERROR

Symptoms

You use Extended MAPI in an application using the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 download and randomly receive MAPI_E_NETWORK_ERROR errors.

Cause

This is caused by a problem in the Exchange MAPI/CDO download.

Resolution

This problem is fixed in the latest version of the Exchange MAPI/CDO download (6.5.8190). The latest version of the Exchange MAPI/CDO download can be downloaded here: http://www.microsoft.com/downloads/en/details.aspx?familyid=E17E7F31-079A-43A9-BFF2-0A110307611E&displaylang=en

More Information

To identify this problem as the root cause you can use a network traffic capturing utility such as Network Monitor 3.3 (NetMon) or WireShark to record the activity between the client and server. You can then filter the frames by "MSRPC.Orphaned || MSRPC.Fault.Status == 0x1c00001a" in NetMon or "dcerpc.pkt_type == 19 or dceprc.cn_status == 0x1c00001a" in Wireshark. After filtering you should see these errors occurring around the time the error happened in the application. More specifically, you should see both an Orphan call and an error of 0x1c00001a around the time the error occurred in the faulting application.

BUG #: 262978 (Exchange Legacy)


Properties

Article ID: 2405611 - Last Review: Feb 4, 2011 - Revision: 1

Feedback