Tm1 server crash - TM1Server.dll

[WILDE]

Hi,

I have recorded this error twice as an application error happening in the last week on the tm1 server in event viewer. There is plenty of memory and nothing is logged in the tm1server.log. No process was running but there were multiple users logged into the server when it went down. Anyone else come across this?

Faulting application name: tm1sd.exe, version: 10.2.20200.55, time stamp: 0x54811378
Faulting module name: TM1Server.dll, version: 10.2.20200.55, time stamp: 0x548120bc
Exception code: 0xc0000005
Fault offset: 0x00000000000699b5
Faulting process ID: 0x1f14
Faulting application start time: 0x01d1012c74ea7a6e
Faulting application path: C:\Program Files\ibm\cognos\tm1_64\bin64\tm1sd.exe
Faulting module path: C:\Program Files\ibm\cognos\tm1_64\bin64\TM1Server.dll
Report ID: 6a6c9ea3-73d9-11e5-80c3-00155d204c06
Faulting package full name:
Faulting package-relative application ID:

[cwillson]

Hi WILDE,

Did you ever get this resolved? I have come across something similar and was wondering if you had spoken to IBM about it at all, or have got to the root cause of this.

[louwae]

This is a very generic error and does not tell you anything useful. If you wish to dig deeper, you have two complementary options:
[*] Attach a debugger such as ADPlus to your tm1 process and configure it to dump the necessary traces when the process crashes
[*] Enable verbose logging on whatever sub-component you suspect as the root cause (locks, process, etc.)

Note though that with verbose logging enabled, you will likely see a different crash signature. This is normal. The benefit of implementing both of the above is that you have very good info with which to log a PMR.

[WILDE]

I have not yet resolved the issue - I plan to try a re installation at some point in the near future. This error has happened 4 times this year in production when no processes werre running in tm1. Users were logged into Perspectives and Tm1 web but were not in any applications. In our dev environment it happens more frequently once a week, with nobody even logged in and nothing running..... We are integrated through Cognos BI using SSO.

[Subramanyam]

We are facing similar issue since last week,

No data saving to disk, no error in Tm1server.log, This is happening when executing a schedules chore after updating few dimension and a couple data loaded.


Faulting application name: tm1sd.exe, version: 10.2.20200.55, time stamp: 0x54811378
Faulting module name: TM1Server.dll, version: 10.2.20200.55, time stamp: 0x548120bc
Exception code: 0xc0000005
Fault offset: 0x00000000000699b5
Faulting process ID: 0x1f14
Faulting application start time: 0x01d1012c74ea7a6e
Faulting application path: C:\Program Files\ibm\cognos\tm1_64\bin64\tm1sd.exe
Faulting module path: C:\Program Files\ibm\cognos\tm1_64\bin64\TM1Server.dll
Report ID: 6a6c9ea3-73d9-11e5-80c3-00155d204c06
Faulting package full name:
Faulting package-relative application ID:

Regadrs