TM1 Service not Stopping

[MSidat]

Hi,

We have been an issue of late on a particular TM1 Service. We are running 9.5.2 and everynight we have a Stop Service, Backup Service, Start Service routine running which does what it says on the Tin. It has been working fine for a number of months (if not years!).

However a few days ago one of the Services didnt Stop properly and continues not to stop properly everynight. (The Stop service command is ran from a BAT Script which is executed from Scheduled Tasks)

The following is in the Server Logs, there are other Chores which it never actually gets round to deactivating and the server shut down message never appears in the Logs.

At this point the Server cannot be access via the Client or TM1Top, but the Service continues to kick off a couple of chores which we run on the service every hour, and the chores will continue to be kicked off until the Service is killed off via Task manager.

In Windows Services it still shows it as Stopping, and the only way to get it started properly is to kill the task first and Start again.

Nothing has changed in the model, i.e. no rule changes, No abnormal structural changes etc.

Anyone else come across a similiar issue, or can anyone hazard a guess as to a probably cause?

Thanks in advance

Code: Select all

4636   []   INFO   2011-11-26 00:38:05.603   TM1.Server   Closing...
4636   []   INFO   2011-11-26 00:38:05.603   TM1.Server   Saving...
4636   []   INFO   2011-11-26 00:38:05.603   TM1.Server   The server is coming down...
5792   []   INFO   2011-11-26 00:38:05.603   TM1.Server   Terminating housekeeper thread.
4636   []   INFO   2011-11-26 00:38:05.806   TM1.Chore   Deactivating chore: Count User Daily Transfer
4636   []   INFO   2011-11-26 00:38:09.712   TM1.Chore   Deactivating chore: Count User Load xx20
4636   []   INFO   2011-11-26 00:38:12.541   TM1.Chore   Deactivating chore: Count User Load xx50
4636   []   INFO   2011-11-26 00:38:16.869   TM1.Chore   Deactivating chore: Export Master CSR Contract List
4636   []   INFO   2011-11-26 00:38:19.729   TM1.Chore   Deactivating chore: Purge Postscript Directory
4636   []   INFO   2011-11-26 00:38:24.714   TM1.Chore   Deactivating chore: Refresh Subsets
4636   []   INFO   2011-11-26 00:38:26.870   TM1.Chore   Deactivating chore: Set Current Period to Actualisation Status Cube

[Christopher Kernahan]

Why do you stop the service every night? If you run Save Data chores daily, then can't you copy the Data directory post-save and back this up? Is it a matter of recycling memory?

Are you trying to deactivate a chore whilst it is running?

[MSidat]

Hi Christopher,

Yes the main purpose of the restart everynight is to recycle the memory.

Nope, nothing else is happening at the time of stopping a service.

[rmackenzie]

I haven't experienced this problem before... but have you tried to manually deactivate the chore 'Set Current Period to Actualisation Status Cube' ?

[John Hammond]

The stop service command tries to shut the TM1 service down in an orderly manner. However I believe that the stop service command has a time out and does not wait until the shutdown is complete.

1. Is there a job running that means the condition to shut the server down never comes true in time? You could test this by running a long running job on a dummy server and see whether you can shut the service down while it runs.

2. The save to disk may have become very large and not complete before the timeout. Arrange a savedataall before your scheduled shutdown.

3. Unfortunately there is no TM1 call to shut a service down.

This function shuts down a TM1 server running as an application. ServerShutdown cannot be used to shut down a server running as a Windows service.

Syntax

ServerShutDown(SaveData);

HTH