Application Event Log contains:
Log Name: Application
Source: Application Error
Date: 6/5/2015 3:37:48 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: MMCNALLY-W7.domain1.company.com
Description:
Faulting application name: mfcmapi.exe, version: 15.0.0.1042, time stamp: 0x53daa53b
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000005
Fault offset: 0x0003b4a8
Faulting process id: 0x1bec
Faulting application start time: 0x01d09fc714142da6
Faulting application path: C:\Users\mmcnally\Downloads\MFCMapi.exe.15.0.0.1042\mfcmapi.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: 5832b6f6-0bba-11e5-9987-d067e51f39f8
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-06-05T19:37:48.000000000Z" />
<EventRecordID>40755</EventRecordID>
<Channel>Application</Channel>
<Computer>MMCNALLY-W7.domain1.company.com</Computer>
<Security />
</System>
<EventData>
<Data>mfcmapi.exe</Data>
<Data>15.0.0.1042</Data>
<Data>53daa53b</Data>
<Data>MSVCR90.dll</Data>
<Data>9.0.30729.6161</Data>
<Data>4dace5b9</Data>
<Data>c0000005</Data>
<Data>0003b4a8</Data>
<Data>1bec</Data>
<Data>01d09fc714142da6</Data>
<Data>C:\Users\mmcnally\Downloads\MFCMapi.exe.15.0.0.1042\mfcmapi.exe</Data>
<Data>C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll</Data>
<Data>5832b6f6-0bba-11e5-9987-d067e51f39f8</Data>
</EventData>
</Event>
Comments: ** Comment from web user: kirkgrabowski **
I ran into this too once Microsoft rolled out MAPI over HTTP to our Exchange Online tenant. Adding the registry key HKCU\Software\Microsoft\Exchange\MapiHttpDisabled = 1 (DWORD) resolved the issue by reverting to the older RPC over HTTPS protocol. (You may need to clear the Autodiscover.xml files from %localappdata%\Microsoft\Outlook and restart Outlook a couple of times for the setting to take effect. There's some general information about the newer protocol at the following links. Also, once I upgraded to Outlook 2013, the problem went away without needing to disable MAPI/HTTP.
http://blogs.technet.com/b/exchange/archive/2014/05/09/outlook-connectivity-with-mapi-over-http.aspx
https://technet.microsoft.com/en-us/library/dn635177%28v=exchg.150%29.aspx