Sometimes we may need to restart the TM1 or Cognos Express server, or individual components of it. You might need to do restart TM1 or Cognos Express if it has become particularly non responsive.
Remember that TM1 is an in memory product, so if you just kill the server, you will lose all data entered since the last server based Save (which are scheduled, but still!).
The steps are:
- Connect to the server via Microsoft Terminal Services
- Check Task Manager to see if there are any jobs currently running. If there are TM1 jobs (tm1sd.exe in Processes), wait until they are complete.
- If active jobs, open TM1Top.exe and check what is running (install location/bin64 folder) – if installed.
- Advise users that the server is going to be restarted at a time in no less than 10 minutes time.
- Open Architect or Perspectives
- Login to CXMD and right click on CXMD and select Security/Clients and Groups. In here look for people that are active in TM1, then go see them and ask them to log out.
- In TM1 either run a process that saves data or right click on CXMD and select Save Data. This will save all data currently in memory to disk before you restart (thus saving everyone’s work!).
- Use Start/Restart to restart the entire server, or
- Open Cognos Express Manager (http://servername:19300/cognos_express/manager/) and on the Manager screen, click “Restart All”, or
- If you know a specific component, open Windows Services and select the component and click restart.
- Log back into TM1 or Cognos Express to check if the issue is still prevalent and if so, you have at least tried the most obvious thing – restarting the TM1 server!
- Notify users that Cognos now available again.
You have now successfully restarted your server.