SaveChanges fails and generates a MAPI_E_NOT_FOUND error message on a large message body in Exchange 2013 CU6

Symptoms

In Microsoft Exchange Server 2013 Cumulative Update 6 (CU6), if you call the Message-class SaveChanges method on a property that does not define the preferred (best) body format, and if the message body is too large, the process fails and returns the following error message:

This problem occurs only when you use an Outlook profile in online mode.

For example, a best body format that is defined by the PR_NATIVE_BODY_INFO property is set to "HtmlBody (0x03)." This setting corresponds to the PR_HTML property of the message body. If a request is then made to change the PR_RTF_COMPRESSED property, the request to save the changes fails if the message body is too large.

Note This is a known problem that affects Symantec Enterprise Vault. In this case, the plain text body updates correctly. However, the RTF body returns the MAPI_E_NOT_FOUND error message.

Cause

This problem occurs because, although Exchange 2013 supports multiple body formats, the program stores only one body format. Also, Exchange performs a dynamic conversion if a different format is requested.

For example, if the HTML body is stored, and an RTF body is requested, Exchange converts the HTML body to RTF, and it returns a ReadOnly stream. Because the PR_RTF_COMPRESSED property does not actually exist in the store, the store returns a MAPI_E_NOT_FOUND error message when Outlook tries to access it in read/write mode.

Resolution

To resolve this issue, install the following cumulative update:

Cumulative Update 8 for Exchange Server 2013

Workaround

Use the PR_NATIVE_BODY_INFO property to determine the kind of message body that is stored and to access the only property that is stored. You no longer have to update all the message bodies because only the one message body is stored.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.