TM1 Forum

Hi guys,

I'm running a TM1 instance as an application and the option to shut it down from architect is always greyed out as per the attachment. If I choose to close the TM1 server application window I get prompted if I'd like to save - I answer yes - but it just hangs there.... doesn't close gracefully. I end up getting .rej files in the logging directory so I'm assuming a server crash.
I thought I'd be able to do a gradeful shutdown using architect (I'm an admin on this data server). Any ideas on why I can't select to shut down the server from architect? thanks.

This option to shut down a server is only avaliable for your Local Server (not to be confused with a server running locally). You cannot use it to close a TM1 server that runs as an application or one that runs as a service.

As to your actual issue - data saves can sometimes take a long time if the model is big. Are you sure the service is not trying to complete the save? How big is your model? How many changes are there? Also, the rej files would suggest that you choose 'No' when asked if you want to save data, as this is when they get created.

Hi Qml,

The server is a "server running locally" instead of the local server
The model is really small - less than 20MB.
What I've discovered is that whenever I choose to close the window and get prompted to save (and I choose yes), the title bar changes to "TM1S.... instance name...(Not Responding)" and even if I wait for over 10 minutes for this small model to close and save data it just sits in this state and I have to kill it and start again. Any clues as to why it's behaving like this. It's a dev environment so I can take it down as often as I need to but would like to know why it's behaving like this, thanks.

PS, the .rej files were old, they weren't from these incidents recently so these files can be ignored.

Have you tried running TM1Top against it to see what is going on in it when you are shutting down?

Thanks Duncan, I'll try that when I run it as an application again. I ended up running it as a service just to avoid having to kill it but when I've cleared my to do list I'll try that out to see what's happening, thanks for the suggestion.