TM1 server instance not saving

[cgaunt]

Hello All,

I have come across a problem, previously un-encountered. I have taken over an existing installation of TM1 9.0SP3. When I elect to save my TM1 server, the server crashes after a few minutes. The TM1s.log file does not rename as one might expect.

I have watched the data directory as the save process takes place. I see the .cub$ files are created and then removed and the .cub files have the correct date and time stamps for me to know that the data is safe. Between the .cub files updating and the TM1s.log file renaming, another file appears called 'saket.set$'. That file does not get removed (I would expect it to rename or be deleted as the save progresses). Immediately after the file appears, the server instance crashes and requires a restart. I have therefore made a connection (in my mind at least) between the 'Saket.set$' file and the instance crashing problem.

Has anyone else seen this problem and found a solution without either upgrading or reinstalling. I am pleased to say that the new version that I have been testing does not have this problem and so I can likely eliminate the environment from the equation.

-Chris

[cgaunt]

Typically, I have found the solution to this a few days after posting. The Saket.set$ file was a red herring. This TM1 instance has a user ID 'Saket.Seth' and the file was the result of the attempted recreation of the user profile during the save process, hence the 'seemingly random' file name. The original account was corrupt however, and that caused the process to fail and abend prematurely.

Resolution, Delete the account and underlying corrupt files, then recreate the user account.

Server now saving as expected without the need for any reinstalls or upgrades.