TM1 Instance is crashing because the process cannot access its own log file

AskAndAnswer · Post by **AskAndAnswer** » Thu Apr 25, 2019 6:21 pm

The issue started after an upgrade to Planning Analytics 2.0.35. One of the instances is constantly crashing with the same error message:

153712 [] FATAL 2019-04-25 10:06:48.917 TM1.System.File TM1 Server Abort: sf_Write() - Write error on file "d:\tm1\dbname\logs\TM1ProcessError_20190425100638_76253712_process_name.log$". Error = error code:32 reason:"The process cannot access the file because it is being used by another process." file:"d:\tm1\dbname\logs\TM1ProcessError_20190425100638_76253712_process_name.log$"
buffer = 0x0000001FB5CA26D0, len= 32751

It looks like TM1 is creating an error log file and immediately locks it for the process that created it. It happens only in one database out of six that are running on the same server.

Any ideas? All your help is greatly appreciated.

dr.nybble · Post by **dr.nybble** » Thu Apr 25, 2019 7:23 pm

Have you checked with Process Explorer that indeed no other process is accessing that file?

AskAndAnswer · Post by **AskAndAnswer** » Thu Apr 25, 2019 8:11 pm

Thank you for your reply. Do you mean Microsoft Process Explorer? It does not exist on the server as of right now. Is there any other way to identify what could lock the file right after it was created by a process?

Wim Gielis · Post by **Wim Gielis** » Thu Apr 25, 2019 8:26 pm

Unless I am mistaken, Dr. Nybble is referring to this utility:
https://docs.microsoft.com/en-us/sysint ... ds/procmon

gtonkin · Post by **gtonkin** » Fri Apr 26, 2019 6:32 am

Process Explorer is also part of SysInternals like ProcMon.
FInd it here: https://docs.microsoft.com/en-us/sysint ... s-explorer

Bakkone · Post by **Bakkone** » Fri Apr 26, 2019 6:49 am

I have this feeling that something changed within PA/TM1 in one of the later versions. I feel like it used to be that I could just turn off an instance. Change the location of the config file etc and everything was fine and dandy.

But as in the problem here. I've noticed that even when shutting down the instance, ie the TM1 server. The system still retains the connection to the "old" data folders and configs. Instead I have to shut down the all of the instances, admin, application servers in cognos config for it to properly release its hold of the data and logs.

So maybe try a full restart?

AskAndAnswer · Post by **AskAndAnswer** » Fri May 10, 2019 9:47 pm

It looks like the new version of TM1 is handling multi-threading differently. The root cause was that the process was in conflict with SaveDataAll process.

Drg · Post by **Drg** » Mon May 13, 2019 1:40 pm

If you change metadata the answer -yes

AskAndAnswer · Post by **AskAndAnswer** » Fri May 17, 2019 3:43 pm

Looks like it's not only metadata that affects it.

TM1 Forum

TM1 Instance is crashing because the process cannot access its own log file

TM1 Instance is crashing because the process cannot access its own log file

Re: TM1 Instance is crashing because the process cannot access its own log file

Re: TM1 Instance is crashing because the process cannot access its own log file

Re: TM1 Instance is crashing because the process cannot access its own log file

Re: TM1 Instance is crashing because the process cannot access its own log file

Re: TM1 Instance is crashing because the process cannot access its own log file

Re: TM1 Instance is crashing because the process cannot access its own log file

Re: TM1 Instance is crashing because the process cannot access its own log file

Re: TM1 Instance is crashing because the process cannot access its own log file