Page 1 of 1

Tm1 Server Crash

Posted: Wed May 30, 2012 2:47 am
by andre lie
Hi all,

I run a series of dimension update TI processes via a main TI process using ExecuteProcess functions (9.5.2 FP2, Windows Server 2008, ODBC connection to SQL Server). Sometimes, the TM1 server crashes during execution of one of the TI processes. However if I run the individual TI process when the crash happens, the process could complete successfully. I could also run the whole series of TI processes without any problem some other time.

Whenever the server crashes, I get this message:
E20) Unable to save cube }DimensionProperties. Server 'abc' is going to be terminated and no data will be saved

I wonder if this is because of locking contention on the }DimensionProperties, but not sure how to avoid it if possible as that cube is a control object.

Regards
Andre

Re: Tm1 Server Crash

Posted: Wed May 30, 2012 3:00 pm
by jim wood
Did you set the flag so the process execute waits for the previous to complete?

Re: Tm1 Server Crash

Posted: Wed May 30, 2012 8:06 pm
by Duncan P
I thought that that flag was only on the ExecuteCommand call. Unless of course OP is using TM1runTI.EXE asynchronously in which all bets are off.

Re: Tm1 Server Crash

Posted: Wed May 30, 2012 8:35 pm
by Martin Ryan
Perhaps try the zLock cube idea in this post. Your processes should be executing in sequential order any way, but it's possible they're overlapping and this will prevent that.

Re: Tm1 Server Crash

Posted: Thu May 31, 2012 12:36 am
by andre lie
Thanks for all the replies

The TI processes are indeed supposed to run in sequential order as the main TI process looks like this:

ExecuteProcess('Process 1');

ExecuteProcess('Process 2');
# In the Epilog of Process 2
ExecuteProcess('Process 2a');
ExecuteProcess('Process 2b');

ExecuteProcess('Process 3');
.....
ExecuteProcess('Process n');

The main TI process is execute by a chore. Users do not have access to run the main TI process and its individual processes.

Regards
Andre