Failed to open temp file for processing tm1rawstore.<DateTime>
Posted: Mon Sep 11, 2023 3:32 am
Hello,
I have a monitoring message log on our tm1 production service for a few weeks now and I get a recurring error from TM1.Audit.PostProcessor with message "Failed to open temp file for processing tm1rawstore.<DateTime>". It follows with error from TM1.Server with message "sf_DeleteFile: Error on file "s:\tm1data\horizon\data\tm1rawstore.<DateTime$>". Error = error code:32 reason:" The process cannot access the file because it is being used by another process."
This error first occurred on Sunday, August 20, 2023 at 03:53 am and is still happening to this day. I get these error messages after the TM1.Chore process of savedata is running. But at the end of the TM1.Chore process, it will always show message from TM1.Server, "sf_SafeDeleteFile() SUCCEEDS after 1 retries, "s:\tm1data\horizon\data\tm1rawstore.<DateTime$>""
One more thing, this tm1rawstore error entails tm1 application memory usage. It is gradually increasing and there is no sign that it will stabilize at any point like before. So in this situation I have to restart tm1 server every day.
Another fact, whenever I try to restart tm1 server, tm1 server's service status is still stuck in stopping state. I check windows services and command prompt using sc queryex syntax and there are no other tm1 servers running on my production server (because there is only one tm1 server running on my production server) . So to fix the problem I rebooted the machine so I could restart the tm1 service.
I compared the tm1s.cfg and tm1s-log.properties files of my save data before and after this error occurred. The only difference is in the last tm1s.cfg, I add RawStoreDirectory to specify tm1rawstore folder on tm1s.cfg and reduce memory size from 2000 MB to 10 MB on tm1s-log.properties as IBM recommends, but the problem persists.
I've been working on this issue with IBM for 19 days and need more insight if anyone is experiencing the same problem as me.
What causes this error to appear in the message log? and how did I resolve this error?
For your information we are using TM1 version 2.0.910.5 on our production server.
I have a monitoring message log on our tm1 production service for a few weeks now and I get a recurring error from TM1.Audit.PostProcessor with message "Failed to open temp file for processing tm1rawstore.<DateTime>". It follows with error from TM1.Server with message "sf_DeleteFile: Error on file "s:\tm1data\horizon\data\tm1rawstore.<DateTime$>". Error = error code:32 reason:" The process cannot access the file because it is being used by another process."
This error first occurred on Sunday, August 20, 2023 at 03:53 am and is still happening to this day. I get these error messages after the TM1.Chore process of savedata is running. But at the end of the TM1.Chore process, it will always show message from TM1.Server, "sf_SafeDeleteFile() SUCCEEDS after 1 retries, "s:\tm1data\horizon\data\tm1rawstore.<DateTime$>""
One more thing, this tm1rawstore error entails tm1 application memory usage. It is gradually increasing and there is no sign that it will stabilize at any point like before. So in this situation I have to restart tm1 server every day.
Another fact, whenever I try to restart tm1 server, tm1 server's service status is still stuck in stopping state. I check windows services and command prompt using sc queryex syntax and there are no other tm1 servers running on my production server (because there is only one tm1 server running on my production server) . So to fix the problem I rebooted the machine so I could restart the tm1 service.
I compared the tm1s.cfg and tm1s-log.properties files of my save data before and after this error occurred. The only difference is in the last tm1s.cfg, I add RawStoreDirectory to specify tm1rawstore folder on tm1s.cfg and reduce memory size from 2000 MB to 10 MB on tm1s-log.properties as IBM recommends, but the problem persists.
I've been working on this issue with IBM for 19 days and need more insight if anyone is experiencing the same problem as me.
What causes this error to appear in the message log? and how did I resolve this error?
For your information we are using TM1 version 2.0.910.5 on our production server.