Strange Lawson Job Scheduler Issue

laura-patenaude

Had an issue last night that in 25 years working with Lawson I've never seen.  I had a batch job (that's been running for 3 years without issue), that has 66 steps.  On step 26 it failed and went into needs recovery.  Only error msg as "Stopped on Exit 1". Any attempt to recover the job resulted it in going back into needs recovery immediately.  Tried putting a trace on the program to see where it was failing and it wasn't getting into the program.  Appears to be a hiccup in the job scheduler and it "lost it's place".  I had to create another job, with all the remaining steps and run that and that worked fine.  Has anyone seen anything like this happen in the job scheduler?  We are on Version 10 on-premise.  Thx

unknown

I have had numerous times that a 2-step job goes into recovery on the first step, with an "Exit 1" message. This is the step where an outside batch file is executed, and the batch file fails because it did not find the file it was supposed to copy. Failure to copy leads the batch execution stream to terminate with an "Exit 1" error. With us, every time it occurs, it's a misnamed file name parameter. Don't know if this will help, but, start looking at Step 26 and see if it's a batch command going south. Good luck!