TM1 Forum

Hello,

Our TM1 server will automatically restart everyday @ 7AM. But today the server service was not properly stopped automatically and it was hung with the status "Stopping". Please see the attachment.
The actions as Stop/Start/Restart are disabled.
Anybody please let me know the reason why this happened and solution to fix this.

Thank You

You read the request for assistance guidelines right? If that's the case can you explain why you have provided almost no information whatsoever? We're not clairvoyant.

Reason would be hard to guess here.
What you can try to do in such a case is to go to Task Manager and hard kill tm1sd.exe process.
The risk is, if you have more than one TM1 servers running as serivces, you might not know which one it is.
A hint to figure out the proper one could be RAM consumption shown also in Task Manager.

If you do have more than one instance running as a service, the best way to find out which process to kill from task manager is to open up a command prompt and type This will list out the PID and name of all the services currently running, scan through the list until you see the name of the instance you want to get rid of and note the PID. Then you can either open up task manager, ensure you are viewing the additional column PID (Processor Identifier), then find the correct PID and right click end process or if you're more of a command line kinda person just type where 1234 is the PID of the process you want to kill

Does your TM1 Admin server exist on another box? I've had this when can't reach the admin server.

Sometimes corrupt log files can cause issues i.e. tm1s.log and tm1s_logger.log.

Try this to resolve issue;

1) Backup all log file from your logging directory i.e. compressed zip file.

2) Delete all original log files i.e. ALL files ending in *.log

3) Create two new text files in your logging directory called tm1s.txt and tm1s_logger.txt

4) Rename both of these newly created files tm1s.log and tm1s_logger.log

5) Attempt to restart Tm1 server via windows server.

This may not resolve the issue but it is certainly worth a try.


Regards,
!TM1Rules