Microsoft Dynamics 365 Blog

Recently it has come to our attention that some customers are installing both CRM and BCM add-ins in Outlook. This will cause Outlook to crash.

The error you will see in the Event Viewer:

.NET Runtime version 2.0.50727.3082 – Fatal Execution Engine Error (7A035FC0) (80131506)

Error seen when you open Outlook in WinDBG:

CLR:(C:\WINDOWS\assembly\GAC_32\BCMRes\\BCMRes.dll) Rejecting native image because dependency C:\WINDOWS\assembly\GAC_MSIL\System.Windows.Forms\\System.Windows.Forms.dll is not native

(11d4.c3c): Break instruction exception – code 80000003 (first chance)

eax=00000001 ebx=00000000 ecx=00000000 edx=0013a9f8 esi=00000000 edi=7a035fc0

eip=7c81a3e1 esp=0013a558 ebp=0013aa04 iopl=0         nv up ei pl nz na po nc

cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202


7c81a3e1 cc              int     3

Missing image name, possible paged-out or corrupt data.

This happens because: Microsoft.Crm.Application.Outlook.ClientAuth.dll which has a dependency on System.Windows.Forms.dll loads up first as we launch Outlook. BCMRes.dll has a native image and has a hard dependency on System.Windows.Forms.dll which has a native image and this scenario hits a glitch in CLR where:

“If an assembly in the GAC (that has a native image) is loaded for the first time as a dependent bind of an assembly loaded via LoadFrom, Fusion will correctly find the assembly, but there is an oversight where we just never return it to the caller. It gets recorded fine in the load context, so that’s why the second bind finds the native image.”

What then happens is that, since the native image was never returned to the caller (and is thus unavailable for use), and since its existence was recorded in the load context, the CLR fails with a fatal execution engine error

To fix this: Install CLR patch with KB # 963676. Please contact support for more details on this CLR hotfix and other details at:

If you experience any hangs even after CLR patch is installed, please make sure that CRM update rollup 1 or greater is installed which contains the fix for the hang issue (KB # 952046).

Chandra Akkiraju

We're always looking for feedback and would like to hear from you. Please head to the Dynamics 365 Community to start a discussion, ask questions, and tell us what you think!