TM1 architect always crashes when starting on my windows system (windows 10 Home edition).
When I start architect with 'run as administrator', I can see the program running in good status with the popup window showing availabe TM1 servers, and "ready for use" message appeared at the left bottom of the window.
However, the program then crashes when I click mouse in an attemption to input user/pwd. Even clicking mouse on other icons on my desktop, which is not related to architect, or tm1, will trigger the crash as well.
The message shown in event viewer of windows are in below:
--------------------------------------------------------------------------------------------------------------------
Faulting application name: tm1a.exe, version: 10.3.10500.60388, timestamp: 0x5ad75acf
Faulting module name: tm1p.dll, version: 10.3.10500.60388, timestamp: 0x5ad75ab5
Exception code: 0xc000041d
Error offset: 0x0010594c
Error process ID: 0x2c54
Error application start time: 0x01db0087520e7593
Error application path: D:\ibm\cognos\tm1_64\bin\tm1a.exe
Error module path: D:\ibm\cognos\tm1_64\bin\tm1p.dll
Report ID: 69efeb15 - b51e - 4ae8 - 8eb1 - ea11b33961f6
Faulting package full name:
Faulting package relative application ID:
-------------------------------------------------------------------------------------
I studies Exception code 0xc000041d in internet. It says 0xc000041d indicates a STATUS_FATAL_USER_CALLBACK_EXCEPTION error. But without more hints, it's too hard to determine the posssible cause of this error.
Is there any way I can get more clues about this crash? for example, check the log file of architect, or set debuging log for tm1a.exe, etc?
Thanks in advance, Chris.
tm1p.dll crash with excpetion code 0xc000041d
-
- Posts: 121
- Joined: Thu Jan 31, 2013 1:03 pm
- OLAP Product: TM1
- Version: 10.2
- Excel Version: 2007
-
- Posts: 121
- Joined: Thu Jan 31, 2013 1:03 pm
- OLAP Product: TM1
- Version: 10.2
- Excel Version: 2007
Re: tm1p.dll crash with excpetion code 0xc000041d
There is no logging parameters in tmp1.ini, and I can not find dedicated log file for tm1 architect.
But fortunately, I found the dump file. It seems the crash caused by "tm1p!RunSubsetEditor+0x00000b4c" for Access violation to stack address 0000003c.
Below is detail information shown in Windbg. Can anyone help me to solve it?
===========================================================================================
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.078 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27668.1000 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Chris\AppData\Local\CrashDumps\tm1a.exe.1628.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19045 MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Sat Sep 7 14:54:15.000 2024 (UTC + 8:00)
System Uptime: not available
Process Uptime: 0 days 0:00:08.000
................................................................
.........................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr
(65c.1db8): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
eax=00000000 ebx=00000000 ecx=1445fc00 edx=00000091 esi=00000003 edi=00000003
eip=77b635bc esp=1445f1d8 ebp=1445f368 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200206
ntdll!NtWaitForMultipleObjects+0xc:
77b635bc c21400 ret 14h
0:011> .symfix
0:011> .reload
................................................................
.........................................................
0:011> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 2937
Key : Analysis.Elapsed.mSec
Value: 170482
Key : Analysis.IO.Other.Mb
Value: 28
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 57
Key : Analysis.Init.CPU.mSec
Value: 1952
Key : Analysis.Init.Elapsed.mSec
Value: 360742
Key : Analysis.Memory.CommitPeak.Mb
Value: 117
Key : Failure.Bucket
Value: NULL_CLASS_PTR_WRITE_c0000005_tm1p.dll!Unknown
Key : Failure.Hash
Value: {a6bf1139-b1fc-beb3-ba2e-d223f24e1c4c}
Key : Timeline.Process.Start.DeltaSec
Value: 8
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 10.3.10500.60388
FILE_IN_CAB: tm1a.exe.1628.dmp
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
CONTEXT: (.ecxr)
eax=1445fbfc ebx=00000000 ecx=1445fc00 edx=00000091 esi=00000001 edi=5d1e9d20
eip=5d1e594c esp=1445fbe0 ebp=00000000 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210206
tm1p!RunSubsetEditor+0xb4c:
5d1e594c 895d3c mov dword ptr [ebp+3Ch],ebx ss
0000003c=????????
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 5d1e594c (tm1p!RunSubsetEditor+0x00000b4c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 0000003c
Attempt to write to address 0000003c
PROCESS_NAME: tm1a.exe
WRITE_ADDRESS: 0000003c
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p 0x%p %s
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 0000003c
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 tm1p!RunSubsetEditor+0xb4c
SYMBOL_NAME: tm1p+b4c
MODULE_NAME: tm1p
IMAGE_NAME: tm1p.dll
STACK_COMMAND: ~11s; .ecxr ; kb
FAILURE_BUCKET_ID: NULL_CLASS_PTR_WRITE_c0000005_tm1p.dll!Unknown
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x86
OSNAME: Windows 10
IMAGE_VERSION: 10.3.10500.60388
FAILURE_ID_HASH: {a6bf1139-b1fc-beb3-ba2e-d223f24e1c4c}
Followup: MachineOwner
---------
===========================================================================================
But fortunately, I found the dump file. It seems the crash caused by "tm1p!RunSubsetEditor+0x00000b4c" for Access violation to stack address 0000003c.
Below is detail information shown in Windbg. Can anyone help me to solve it?
===========================================================================================
************* Preparing the environment for Debugger Extensions Gallery repositories **************
ExtensionRepository : Implicit
UseExperimentalFeatureForNugetShare : true
AllowNugetExeUpdate : true
NonInteractiveNuget : true
AllowNugetMSCredentialProviderInstall : true
AllowParallelInitializationOfLocalRepositories : true
EnableRedirectToChakraJsProvider : false
-- Configuring repositories
----> Repository : LocalInstalled, Enabled: true
----> Repository : UserExtensions, Enabled: true
>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds
************* Waiting for Debugger Extensions Gallery to Initialize **************
>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.078 seconds
----> Repository : UserExtensions, Enabled: true, Packages count: 0
----> Repository : LocalInstalled, Enabled: true, Packages count: 42
Microsoft (R) Windows Debugger Version 10.0.27668.1000 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Chris\AppData\Local\CrashDumps\tm1a.exe.1628.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Version 19045 MP (8 procs) Free x86 compatible
Product: WinNt, suite: SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Debug session time: Sat Sep 7 14:54:15.000 2024 (UTC + 8:00)
System Uptime: not available
Process Uptime: 0 days 0:00:08.000
................................................................
.........................................................
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr
(65c.1db8): Access violation - code c0000005 (first/second chance not available)
For analysis of this file, run !analyze -v
eax=00000000 ebx=00000000 ecx=1445fc00 edx=00000091 esi=00000003 edi=00000003
eip=77b635bc esp=1445f1d8 ebp=1445f368 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200206
ntdll!NtWaitForMultipleObjects+0xc:
77b635bc c21400 ret 14h
0:011> .symfix
0:011> .reload
................................................................
.........................................................
0:011> !analyze -v
*******************************************************************************
* *
* Exception Analysis *
* *
*******************************************************************************
KEY_VALUES_STRING: 1
Key : AV.Dereference
Value: NullClassPtr
Key : AV.Fault
Value: Write
Key : Analysis.CPU.mSec
Value: 2937
Key : Analysis.Elapsed.mSec
Value: 170482
Key : Analysis.IO.Other.Mb
Value: 28
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 57
Key : Analysis.Init.CPU.mSec
Value: 1952
Key : Analysis.Init.Elapsed.mSec
Value: 360742
Key : Analysis.Memory.CommitPeak.Mb
Value: 117
Key : Failure.Bucket
Value: NULL_CLASS_PTR_WRITE_c0000005_tm1p.dll!Unknown
Key : Failure.Hash
Value: {a6bf1139-b1fc-beb3-ba2e-d223f24e1c4c}
Key : Timeline.Process.Start.DeltaSec
Value: 8
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
Key : WER.Process.Version
Value: 10.3.10500.60388
FILE_IN_CAB: tm1a.exe.1628.dmp
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
CONTEXT: (.ecxr)
eax=1445fbfc ebx=00000000 ecx=1445fc00 edx=00000091 esi=00000001 edi=5d1e9d20
eip=5d1e594c esp=1445fbe0 ebp=00000000 iopl=0 nv up ei pl nz na pe nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210206
tm1p!RunSubsetEditor+0xb4c:
5d1e594c 895d3c mov dword ptr [ebp+3Ch],ebx ss
Resetting default scope
EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 5d1e594c (tm1p!RunSubsetEditor+0x00000b4c)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 0000003c
Attempt to write to address 0000003c
PROCESS_NAME: tm1a.exe
WRITE_ADDRESS: 0000003c
ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p 0x%p %s
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 00000001
EXCEPTION_PARAMETER2: 0000003c
STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 tm1p!RunSubsetEditor+0xb4c
SYMBOL_NAME: tm1p+b4c
MODULE_NAME: tm1p
IMAGE_NAME: tm1p.dll
STACK_COMMAND: ~11s; .ecxr ; kb
FAILURE_BUCKET_ID: NULL_CLASS_PTR_WRITE_c0000005_tm1p.dll!Unknown
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x86
OSNAME: Windows 10
IMAGE_VERSION: 10.3.10500.60388
FAILURE_ID_HASH: {a6bf1139-b1fc-beb3-ba2e-d223f24e1c4c}
Followup: MachineOwner
---------
===========================================================================================
-
- MVP
- Posts: 3222
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.1.5
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: tm1p.dll crash with excpetion code 0xc000041d
Is the only reason why you are doing all this, the advanced rules editor ?
Best regards,
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
-
- Posts: 121
- Joined: Thu Jan 31, 2013 1:03 pm
- OLAP Product: TM1
- Version: 10.2
- Excel Version: 2007
Re: tm1p.dll crash with excpetion code 0xc000041d
Not exactly. Though I choose PA 2.0.6 for the sake of advanced rule editor.
But in actually, this problem exists for a long time. my TM1 10.2.2 failed on this laptop several years ago. and I test PA 2.0.9 on it again months ago, same crash happened as well.
I suspected the crash is caused by some settings of network, but no way to identify the exact one. Just one hour ago, by accident I enabled the 'Use TLS 1.3' option in the "advanced settings" of "Internet Properties". And amazingly, ARCHITECT was started and functioned properly without crash. Everything looks fine. I thought I have solved the problem. However, when I reboot the laptop, to my dispointing, the crash returns again.
But in actually, this problem exists for a long time. my TM1 10.2.2 failed on this laptop several years ago. and I test PA 2.0.9 on it again months ago, same crash happened as well.
I suspected the crash is caused by some settings of network, but no way to identify the exact one. Just one hour ago, by accident I enabled the 'Use TLS 1.3' option in the "advanced settings" of "Internet Properties". And amazingly, ARCHITECT was started and functioned properly without crash. Everything looks fine. I thought I have solved the problem. However, when I reboot the laptop, to my dispointing, the crash returns again.
-
- Posts: 121
- Joined: Thu Jan 31, 2013 1:03 pm
- OLAP Product: TM1
- Version: 10.2
- Excel Version: 2007
Re: tm1p.dll crash with excpetion code 0xc000041d
I finally identified the root cause of tm1p.dll crash.
It's in conflict with another software (a Pinyin input tool provided by sogou.com), which I have used for more than 10 years. No idea why these two are in conflict.
It's in conflict with another software (a Pinyin input tool provided by sogou.com), which I have used for more than 10 years. No idea why these two are in conflict.
-
- MVP
- Posts: 3222
- Joined: Mon Dec 29, 2008 6:26 pm
- OLAP Product: TM1, Jedox
- Version: PAL 2.1.5
- Excel Version: Microsoft 365
- Location: Brussels, Belgium
- Contact:
Re: tm1p.dll crash with excpetion code 0xc000041d
Good catch !
Best regards,
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly
Wim Gielis
IBM Champion 2024-2025
Excel Most Valuable Professional, 2011-2014
https://www.wimgielis.com ==> 121 TM1 articles and a lot of custom code
Newest blog article: Deleting elements quickly