Share
ReportHi,
One of our customers recently removed local administrator rights of their end-user accounts.
Since then, they are experiencing AX client crashes every now and then.
They report that the client crashes when filtering data on a list page and they receive the following error message:
We cannot reproduce the crash in any way.
Yesterday they sent me a crash dump. This dump points to the triedit.dll being the cause of the crash.
Triedit.dll is part of the DHTML Editing Control (ActiveX), which is only used by a form to edit emails in our system.
Having this linked to a user filtering data on a listpage is beyond me.
My knowledge of WinDbg is fairly limited, so I cannot figure out what exactly went wrong.
Please find the results of !analyze -v below.
Any help regarding this issue is greatly appreciated!
0:018> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
Unable to load image C:\Windows\assembly\NativeImages_v4.0.30319_32\mscorlib\277a04b4ec834bb70c1bd343b14ebd3a\mscorlib.ni.dll, Win32 error 0n2
*** WARNING: Unable to verify timestamp for FwcWsp.dll
*** ERROR: Module load completed but symbols could not be loaded for FwcWsp.dll
*** WARNING: Unable to verify checksum for System.Windows.Forms.ni.dll
GetUrlPageData2 (WinHttp) failed: 12030.
DUMP_CLASS: 2
DUMP_QUALIFIER: 400
CONTEXT: (.ecxr)
eax=00000000 ebx=1e99ed70 ecx=00000000 edx=00000000 esi=00000000 edi=1e99ed70
eip=075b60f0 esp=1e99ec70 ebp=1e99ec9c iopl=0 nv up ei pl nz na po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
TriEdit+0x260f0:
075b60f0 e828ebffff call TriEdit+0x24c1d (075b4c1d)
Resetting default scope
FAULTING_IP:
TriEdit+260f0
075b60f0 e828ebffff call TriEdit+0x24c1d (075b4c1d)
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 075b60f0 (TriEdit+0x000260f0)
ExceptionCode: 40000015
ExceptionFlags: 00000000
NumberParameters: 0
PROCESS_NAME: Ax32.exe
ERROR_CODE: (NTSTATUS) 0x40000015 - {Fatal Application Exit} %hs
EXCEPTION_CODE: (NTSTATUS) 0x40000015 (1073741845) - {Fatal Application Exit} %hs
EXCEPTION_CODE_STR: 40000015
WATSON_BKT_PROCSTAMP: 5886d6b8
WATSON_BKT_PROCVER: 6.3.5000.2046
WATSON_BKT_MODULE: TriEdit.dll
WATSON_BKT_MODSTAMP: 4435935c
WATSON_BKT_MODOFFSET: 260f0
WATSON_BKT_MODVER: 6.2.0.1
BUILD_VERSION_STRING: 10.0.16299.431 (WinBuild.160101.0800)
MODLIST_WITH_TSCHKSUM_HASH: d16579a6ca1a7a74c93940ab88cd1c6041039925
MODLIST_SHA1_HASH: 035dd394219032162790de2b8fd57081b47fe496
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
DUMP_FLAGS: 94
DUMP_TYPE: 1
MISSING_CLR_SYMBOL: 0
ANALYSIS_SESSION_HOST: LWAWOHUY
ANALYSIS_SESSION_TIME: 11-16-2018 10:09:19.0838
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
MANAGED_CODE: 1
MANAGED_ENGINE_MODULE: clr
MANAGED_BITNESS_MISMATCH:
Managed code needs matching platform for proper analysis. Use 'x86' debugger.
THREAD_ATTRIBUTES:
OS_LOCALE: NLD
PROBLEM_CLASSES:
Tid [0x0]
Frame [0x00]
String [STATUS_FATAL_APP_EXIT]
Data Bucketing
NOSOS
Tid [0x2558]
Failure Bucketing
BUGCHECK_STR: STATUS_FATAL_APP_EXIT_NOSOS
DEFAULT_BUCKET_ID: STATUS_FATAL_APP_EXIT_NOSOS
LAST_CONTROL_TRANSFER: from 075b6045 to 075b60f0
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
1e99ec9c 075b6045 075b600c 7656dcf0 1e99ed70 TriEdit+0x260f0
1e99ed40 775033a6 1e99ed70 774d3b92 1e99fa0c TriEdit+0x26045
1e99fa1c 774c5d57 ffffffff 774ead1f 00000000 ntdll!__RtlUserThreadStart+0x3d64e
1e99fa2c 00000000 6c93345e 1dcd0c20 00000000 ntdll!_RtlUserThreadStart+0x1b
THREAD_SHA1_HASH_MOD_FUNC: a51f6540123bd9921793745e790731fee88520c8
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: ebe85617eb4c8fa09c92fbf9817edf1bf8fe66d7
THREAD_SHA1_HASH_MOD: b35694ccdf0b82bc415c5ef5b29989b09190070a
FOLLOWUP_IP:
TriEdit+260f0
075b60f0 e828ebffff call TriEdit+0x24c1d (075b4c1d)
FAULT_INSTR_CODE: ffeb28e8
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: TriEdit+260f0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: TriEdit
IMAGE_NAME: TriEdit.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4435935c
STACK_COMMAND: .ecxr ; kb
BUCKET_ID: STATUS_FATAL_APP_EXIT_NOSOS_TriEdit+260f0
PRIMARY_PROBLEM_CLASS: STATUS_FATAL_APP_EXIT_NOSOS_TriEdit+260f0
FAILURE_EXCEPTION_CODE: 40000015
FAILURE_IMAGE_NAME: TriEdit.dll
BUCKET_ID_IMAGE_STR: TriEdit.dll
FAILURE_MODULE_NAME: TriEdit
BUCKET_ID_MODULE_STR: TriEdit
FAILURE_FUNCTION_NAME: Unknown
BUCKET_ID_FUNCTION_STR: Unknown
BUCKET_ID_OFFSET: 260f0
BUCKET_ID_MODTIMEDATESTAMP: 4435935c
BUCKET_ID_MODCHECKSUM: 43571
BUCKET_ID_MODVER_STR: 6.2.0.1
BUCKET_ID_PREFIX_STR: STATUS_FATAL_APP_EXIT_NOSOS_
FAILURE_PROBLEM_CLASS: STATUS_FATAL_APP_EXIT_NOSOS
FAILURE_SYMBOL_NAME: TriEdit.dll!Unknown
FAILURE_BUCKET_ID: STATUS_FATAL_APP_EXIT_NOSOS_40000015_TriEdit.dll!Unknown
WATSON_STAGEONE_URL: watson.microsoft.com/.../000260f0.htm
TARGET_TIME: 2018-11-15T14:07:31.000Z
OSBUILD: 16299
OSSERVICEPACK: 431
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: 1975-01-20 20:44:01
BUILDDATESTAMP_STR: 160101.0800
BUILDLAB_STR: WinBuild
BUILDOSVER_STR: 10.0.16299.431
ANALYSIS_SESSION_ELAPSED_TIME: 777f
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:status_fatal_app_exit_nosos_40000015_triedit.dll!unknown
FAILURE_ID_HASH: {cd9b40d0-e83c-b319-6b61-2f6626364020}
Followup: MachineOwner
---------
*This post is locked for comments
All responses (
Answers (
291,269
