JobControl (fatal error from @Coordinator)

esivaprasad · Post by **esivaprasad** » Thu Jun 21, 2012 7:29 am

Hi,
Daily we will run some same sequences.
Till last friday it ran fine without any warning/errors.
But from 3 runs, one sequence is failing with the error that

" JobControl (fatal error from @Coordinator): Sequence job will abort due to previous unrecoverable errors ".

If we compile all jobs which are in that failing sequence,its runnng fine.
Similar type of issues came to some other sequences .
every time compiling all jobs in that failure sequence its difficult .
Is there any other way to come out of this frequently geeting error

"JobControl (fatal error from @Coordinator): Sequence job will abort due to previous unrecoverable errors".
Thanks in advance for all support.

chulett · Post by **chulett** » Thu Jun 21, 2012 7:32 am

There must be more information available. Are there any other messages? What about in the jobs that the sequence runs, are they failing?

priyadarshikunal · Post by **priyadarshikunal** » Thu Jun 21, 2012 9:09 am

Look at an entry in log starting with "Summary of sequence run" and at the details in there. I am sure you can find some useful lines in there.

ray.wurlod · Post by **ray.wurlod** » Thu Jun 21, 2012 4:38 pm

Are the subsidiary Job activities set up for "reset if required, then run"?

esivaprasad · Post by **esivaprasad** » Fri Jun 22, 2012 12:33 am

priyadarshikunal wrote:Look at an entry in log starting with "Summary of sequence run" and at the details in there. I am sure you can find some useful lines in there.

Thanks for your info.
Please find the log info which starts Summary of sequence run step

"REPORTSEQUENCEOthersDailySERVERJOB..JobControl (@Coordinator): Summary of sequence run
03:29:05: Sequence started
03:29:05: Load0001SQESupervisorMgrDirDM (JOB Load0001SQESupervisorMgrDirDM) started
03:29:29: Load0002WorstCaseLabCodeDriver (JOB Load0002WorstCaseLabCodeDriver) started
03:29:30: Load303405ProgramParts2DM (JOB Load303405ProgramParts2DM) started
03:29:32: Load303404PartCPNTDM (JOB Load303404PartCPNTDM) started
03:29:34: jDM16645AllDriverProgram (JOB jDM0005AllDriverProgram) started
03:29:34: Exception raised: @jDM0005AllDriverProgram, Error calling DSRunJob(jDM0005AllDriverProgram), code=-99 [General repository interface 'other error']
03:29:34: Exception raised: @Coordinator, Error calling DSWaitForJob(), code=-99 [General repository interface 'other error']
03:29:34: Sequence failed"

esivaprasad · Post by **esivaprasad** » Fri Jun 22, 2012 12:37 am

chulett wrote:There must be more information available. Are there any other messages? What about in the jobs that the sequence runs, are they failing? ...

Hi ,

Thank you for information.
if that sequence starts and ciompleted successfully, in that sequence eaxch job running fine ,without any warning/ errors.

chulett · Post by **chulett** » Fri Jun 22, 2012 7:18 am

esivaprasad wrote:03:29:34: Exception raised: @jDM0005AllDriverProgram, Error calling DSRunJob(jDM0005AllDriverProgram), code=-99 [General repository interface 'other error']
03:29:34: Exception raised: @Coordinator, Error calling DSWaitForJob(), code=-99 [General repository interface 'other error']
03:29:34: Sequence failed"

These are the errors that should have been reported. If you haven't already, try doing an exact search for "General repository interface" and then filter out the ones that just tell you to search, you'll find ones that show people have successfully dealt with this.

Anything that fails and then runs fine after being restarted is typically having some kind of resource issue.