This question came to me from a user of a software package we have been using for many years. It uses CR runtime.

User previews a Crystal Report. User then selects "export", format as a pdf and select "mapi".

This then causes whatever program we're doing this from to crash. The event log shows "Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll"

I had the user clarify several things for me:

1. MAPI works correctly from other places (e.g. clicking e-mail address on web page).
2. The problem was progressive. Everything worked fine until a month ago, and one by one, the computers began having this problem so that now all computers in the office have this problem. (This would tend to make me think it is related to some Windows or MS Office, so I have asked the user for clarification on the OS version but have not yet received a response).
3. They are using Office 2016. I also asked the user to clarify whether they are using 32-bit or 64-bit, since I know there can be architecture-based issues with some application integration.
4. The problem does not occur when they run the same report using Crystal Standard/Pro instead of runtime.

This would all be CR XI. I recall some sort of DLL-version tinkering I had to do with CR runtime back in CR 8.