Application crashes with access violation exception in mso20win32client.dll when use MAPI

Question

Our application uses MAPI to connect to office exchange server. Here whenever we are trying to close the application after initiating a session, this crash occurs.

This is not happening when we use Office 2013 or earlier version. But with office365 it occurs 100/100.

The crash dump point to an exception occurs in mso20win32client.dll.
Please see the crash dump details :

CONTEXT: (.ecxr)
eax=00000000 ebx=6601b270 ecx=00000040 edx=00eff4f8 esi=1290db00 edi=0c23b8c0
eip=5dfd97b4 esp=00eff4bc ebp=00eff4ec iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010202
mso20win32client+0x197b4:
5dfd97b4 8b4104 mov eax,dword ptr [ecx+4] ds:002b:00000044=????????
Resetting default scope

FAULTING_IP:
mso20win32client+197b4
5dfd97b4 8b4104 mov eax,dword ptr [ecx+4]

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 5dfd97b4 (mso20win32client+0x000197b4)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000000
Parameter[1]: 00000044
Attempt to read from address 00000044

FOLLOWUP_IP:
mso20win32client+197b4
5dfd97b4 8b4104 mov eax,dword ptr [ecx+4]

READ_ADDRESS: 00000044

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 00000000

EXCEPTION_PARAMETER2: 00000044

WATSON_BKT_PROCSTAMP: 5ffd5736

WATSON_BKT_PROCVER: 6.0.21012.5326

PROCESS_VER_PRODUCT: Kofax ReadSoft Invoices

WATSON_BKT_MODULE: mso20win32client.dll

WATSON_BKT_MODSTAMP: 5ffad15b

WATSON_BKT_MODOFFSET: 197b4

BUILD_VERSION_STRING: 18362.1.wow64fre.19h1_release.190318-1202

MODLIST_WITH_TSCHKSUM_HASH: 2f1b8cc947df4d0d91cc6c52487b15e8be984ca6

MODLIST_SHA1_HASH: 822eed1313f228a07db94900be1aa41d1e4353a5

DUMP_FLAGS: 0

DUMP_TYPE: 2

PROCESS_NAME: unknown

MISSING_CLR_SYMBOL: 0

ANALYSIS_SESSION_HOST: PC07VPNT

ANALYSIS_SESSION_TIME: 02-08-2021 11:53:21.0870

ANALYSIS_VERSION: 10.0.17763.132 x86fre

MANAGED_CODE: 1

MANAGED_ENGINE_MODULE: clr

MANAGED_ANALYSIS_PROVIDER: SOS

MANAGED_THREAD_ID: 2ad4

THREAD_ATTRIBUTES:
OS_LOCALE: ENU

ADDITIONAL_DEBUG_TEXT: SOS.DLL is not loaded for managed code. Analysis might be incomplete

BUGCHECK_STR: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_NOSOS

DEFAULT_BUCKET_ID: NULL_CLASS_PTR_READ_NOSOS

PRIMARY_PROBLEM_CLASS: APPLICATION_FAULT

PROBLEM_CLASSES:

ID: [0n313]
Type: [@access _VIOLATION]
Class: Addendum
Scope: BUCKET_ID
Name: Omit
Data: Omit
PID: [Unspecified]
TID: [0x2ad4]
Frame: [0] : mso20win32client
ID: [0n285]
Type: [INVALID_POINTER_READ]
Class: Primary
Scope: BUCKET_ID
Name: Add
Data: Omit
PID: [Unspecified]
TID: [0x2ad4]
Frame: [0] : mso20win32client
ID: [0n310]
Type: [NULL_CLASS_PTR_READ]
Class: Primary
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Add
Data: Omit
PID: [0x4848]
TID: [0x2ad4]
Frame: [0] : mso20win32client
ID: [0n97]
Type: [@SHUTDOWN]
Class: Addendum
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Omit
Data: Omit
PID: [0x4848]
TID: [0x2ad4]
Frame: [0] : mso20win32client
ID: [0n251]
Type: [NOSOS]
Class: Addendum
Scope: DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
BUCKET_ID
Name: Add
Data: Omit
PID: [Unspecified]
TID: [Unspecified]
Frame: [0]

LAST_CONTROL_TRANSFER: from 5dfd765c to 5dfd97b4

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
00eff4ec 5dfd765c 00eff4f8 1290cdd8 00eff520 mso20win32client+0x197b4
00eff4fc 5dfd77c1 1290cdd8 5dfd992b 1290cd80 mso20win32client+0x1765c
00eff520 5e07a3f0 00000000 5dfc4556 00000000 mso20win32client+0x177c1
00eff56c 5e0ce092 00000001 00eff5e0 5e0ce076 mso20win32client+0xba3f0
00eff578 5e0ce076 0c205650 5dfc4556 00000000 mso20win32client+0x10e092
00eff5e0 750d98dc d39cd68b 00000001 00000001 mso20win32client+0x10e076
00eff614 750d98aa 00eff628 00eff62c 00eff630 ucrtbase!__crt_seh_guarded_call::operator()<, &, >+0x30
00eff634 5dff167d 5e42e768 5dff15f8 733178cd ucrtbase!execute_onexit_table+0x2a
00eff674 5dfc1328 00000001 00eff6c0 5dfc1212 mso20win32client+0x3167d
00eff680 5dfc1212 5dfc0000 00000000 00000001 mso20win32client+0x1328
00eff6c0 5dfc110c 5dfc0000 00000000 00000001 mso20win32client+0x1212
00eff6d4 77342ed6 5dfc0000 00000000 00000001 mso20win32client+0x110c
00eff6f4 7731a288 5dfc10f0 5dfc0000 00000000 ntdll!LdrxCallInitRoutine+0x16
00eff740 77310496 00000000 00000001 7b857802 ntdll!LdrpCallInitRoutine+0x51
00eff7d8 77302755 03ff6bb8 0080e870 00000000 ntdll!LdrShutdownProcess+0xf6
00eff8ac 761159a2 00000000 77e8f3b0 ffffffff ntdll!RtlExitUserProcess+0xb5
00eff8b4 77e8f3b0 ffffffff 00eff8dc 00793434 kernel32!ExitProcessImplementation+0x12
00eff8c0 00793434 00000000 008715a0 00eff910 System_Drawing_ni+0x3f3b0
00eff920 717451b2 00000000 00000000 00000000 msvcr120!doexit+0xb2
00eff934 007c62b9 00000000 982ede3f 007c6368 msvcr120!exit+0xf
00eff984 77338944 00d9d000 7b85763a 00000000 kernel32!BaseThreadInitThunk+0x19
00eff9e0 77338914 ffffffff 7735a0bb 00000000 ntdll!_RtlUserThreadStart+0x2f
00eff9f0 00000000 007c6368 00d9d000 00000000 ntdll!_RtlUserThreadStart+0x1b

THREAD_SHA1_HASH_MOD_FUNC: 3596c25df9616386b333a91aaf27566931886859

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 17a906381b786f24c1f52e3b2b8d1473be9b8439

THREAD_SHA1_HASH_MOD: 0f0e296b68f21f68ed530d26f2727a5bc05e7a58

FAULT_INSTR_CODE: 3b04418b

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: mso20win32client+197b4

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: mso20win32client

IMAGE_NAME: mso20win32client.dll

DEBUG_FLR_IMAGE_TIMESTAMP: 5ffad15b

STACK_COMMAND: ~0s ; .ecxr ; kb

FAILURE_BUCKET_ID: NULL_CLASS_PTR_READ_NOSOS_c0000005_mso20win32client.dll!Unknown

BUCKET_ID: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_NOSOS_mso20win32client+197b4

FAILURE_EXCEPTION_CODE: c0000005

FAILURE_IMAGE_NAME: mso20win32client.dll

BUCKET_ID_IMAGE_STR: mso20win32client.dll

FAILURE_MODULE_NAME: mso20win32client

BUCKET_ID_MODULE_STR: mso20win32client

FAILURE_FUNCTION_NAME: Unknown

BUCKET_ID_FUNCTION_STR: Unknown

BUCKET_ID_OFFSET: 197b4

BUCKET_ID_MODTIMEDATESTAMP: 5ffad15b

BUCKET_ID_MODCHECKSUM: 4e853a

BUCKET_ID_MODVER_STR: 0.0.0.0

BUCKET_ID_PREFIX_STR: APPLICATION_FAULT_NULL_CLASS_PTR_READ_INVALID_POINTER_READ_NOSOS_

FAILURE_PROBLEM_CLASS: APPLICATION_FAULT

FAILURE_SYMBOL_NAME: mso20win32client.dll!Unknown

TARGET_TIME: 2021-02-04T10:42:28.000Z

OSBUILD: 18363

OSSERVICEPACK: 1110

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 256

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x86

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt SingleUserTS

USER_LCID: 0

OSBUILD_TIMESTAMP: 2017-09-12 05:13:03

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.wow64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 2dfbc

ANALYSIS_SOURCE: UM

FAILURE_ID_HASH_STRING: um:null_class_ptr_read_nosos_c0000005_mso20win32client.dll!unknown

FAILURE_ID_HASH: {c7362172-e7c8-7624-46b1-5f472905396e}

Followup: MachineOwner

It would be grateful if i get any any help from someone or there is any workaround of any?

Answer

Hi @Nihalkumar Srivastava ,
What's the version of your Outlook 365(File>Office Account>About Outlook), please first ensure that you have updated to the latest version of Outlook.

Here whenever we are trying to close the application after initiating a session, this crash occurs

Did this issue only occur on Outlook 365? Could other office client work normally? And did it only occur on these accounts using MAPI to Exchange server?

For your issue of crashing in Outlook, in order to avoid the interference of add-ins, it's suggested to restart your Outlook in safe mode to check if the issue has any difference (Windows + R >type "outlook.exe /safe"> enter)

If the issue still exists, please understand that here we mainly focus on general issue about Outlook desktop client, and it's not supproted to analyze log files. If you still think it may be related to mso20win32client.dll, I have tried to research a lot about outlook crashing with mso20win32client.dll, and found many related articles and threads, which mentioned that changing the value of "ShownFirstRunOptin" in register editor may work for it, for more information, please refer to this article: Office Applications crash or cannot start

If that's still invalid, for Microsoft 365 users, we could try to use SaRA tools to troubleshoot it, which works by running tests to figure out what's wrong and offers the best solution for the identified problem.

Hope your issue would be resolved soon.

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer

We have the same behavior and the same callstack. Is there any workaround?

Answer

Thanks for your update and sorry for delay, please kindly understand here we mainly focus on general issue about Outlook desktop client, and we may know little about the issue of developing application with MAPI and also not be able to perform any related tests, But I still do a lot of research for you.

According to your description, it could work normally on your orginal office 2013, have you checked other differences between your new client and recent one(such as the Windows os bit or others), which could help us analyze if it was caused by any version compatibility issues in your application.

Also, based on my research, the crash may also occur if you don't have permission to this file, you could also try to check your file permission.

Hope your issue would be resolved soon.

Application crashes with access violation exception in mso20win32client.dll when use MAPI

3 answers