Maxl Automation for sequential calc scripts - just stops without giving any error

Question

Hi,
I was running an automation for calculations using MaxL. by scheduling the Steps.bat in the task scheduler of windows.
_________ Steps.bat ___________
StartMaxl Steps.mxl
_________ Steps.mxl ___________
Login .....
Sppol on to log.log
Execute calculation 'DB'.'DB'.StepA1;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepA2;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepA3;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepA4;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepA5;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepA6;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepA7;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepA8;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepB1;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepB2;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepB3;           Iferror 'StopError';
Execute calculation 'DB'.'DB'.StepB4;           Iferror 'StopError';
define label 'StopError';
exit;
Not when I check the log file on execution it shows ...
___________________ Log.log _______________________
MAXL> execute calculation 'DB'.'DB'.'StepA1';
OK/INFO - 1012579 - Total Calc Elapsed Time for [StepA1.csc] : [173.87] seconds.
OK/INFO - 1013274 - Calculation executed.
MAXL> execute calculation 'DB'.'DB'.'StepA8';
OK/INFO - 1012579 - Total Calc Elapsed Time for [StepA8.csc] : [2000.00] seconds.
OK/INFO - 1013274 - Calculation executed.
MAXL> execute calculation 'DB'.'DB'.'StepB1';
OK/INFO - 1012579 - Total Calc Elapsed Time for [StepB1.csc] : [1200.00] seconds.
OK/INFO - 1013274 - Calculation executed.
MAXL> execute calculation 'DB'.'DB'.'StepB2';
If you see the last line - it just halts - doesn't show any error or any other message. And the task in the windows task scheduler keeps showing the task as running - without any error there as well.
Any ideas on why it is just going to a limbo (no sessions also appear on EAS console)
Ankur

Answer 1

Yes the script can be manually executed. Also if I again put a mxl file starting from the step where it last stopped - it continues execution normally. (i.e. executes StepB2 as well and continues executing)
And today's execution result - I kept monitoring the server, it ran for 3hrs and then halts after around 80% of the steps with 20% were still remaining. I created a new Mxl to start from the last 20% and it ran successfully again.
@Amarnath : Restart database ?
I checked the logs - and this is what I can see (modified the big fields to show what the logs are showing)
[Wed Oct  9 09:54:43 2013]Local/....... Ankur.....
Calculation executed
[Wed Oct  9 09:54:43 2013]Local/DB///47450147858752/Info(1013210)
User [Ankur.....@Native Directory] set active on database [DB]
[Wed Oct  9 09:54:43 2013]Local/DB/DB/Ankur......
Received Command [Calculate] from user [Ankur......@Native Directory]
[Wed Oct  9 09:54:43 2013]Local/DB/DB/Ankur......
Received Command [Calculate] from user [Ankur......@Native Directory] using [StepB2.csc]
[Wed Oct  9 10:24:59 2013]Local/DB///47341561242320/Info(1002035)
Starting Essbase Server - Application [DB]
[Wed Oct  9 10:24:59 2013]Local/DB///47341561242320/Info(1200480)
Loaded and initialized JVM module
[Wed Oct  9 10:24:59 2013]Local/DB//47341561242320/Info(1200445)
External [GLOBAL] function [@ESSBASEALERT] registered OK
[Wed Oct  9 10:25:01 2013]Local/DB//47341561242320/Info(1019008)
Reading Application Definition For [DB]
So indeed the essbase server is starting again - but why ?
Ankur