REG : Job Status = 99 Error

Vinodanand · Post by **Vinodanand** » Tue Jul 04, 2006 4:17 am

Hi,

I've been getting this error only for this job .The job is a multi instance job and i've tried tried clearing the status file , compiling the job and rerunning but still i get this General Server error. Can anyone help me resolving the same.Please find the error message below

Job name:EligPxiLoadFileExtractSeq.TEST_1
Event #:29
Timestamp:7/4/2006 2:51:09 AM
Event type:Info
Message:
EligPxiLoadFileExtractSeq.TEST_1.JobControl (DSWaitForJob): Job EligPxiFileNameCoalitionJob.1832 has finished, status = 99 (Not running)
[/b]

ArndW · Post by **ArndW** » Tue Jul 04, 2006 4:23 am

Is this a job sequence or does it have Job Control code? It seems to be issuing a call to DSWaitForjob() that is returning the error.

Vinodanand · Post by **Vinodanand** » Tue Jul 04, 2006 6:01 am

yes its a sequence calling the server job which does not run. Even though the server job is a multi instance job it does not show the status in the director as finished.The detail log for the server job is given below..

(EligPxiLoadFileExtractSeq) <- EligPxiFileNameCoalitionJob.1832: Job under control finished.

chulett · Post by **chulett** » Tue Jul 04, 2006 6:06 am

So... this is a Sequence job calling a multi-instance Server job? Once or many times? How are you handling the uniqueness that the Invocation ID needs? Any chance that it is running into itself?

If you have more in the way of error messages, post them. The ones that surround this one, for example or any from the other log.

Vinodanand · Post by **Vinodanand** » Tue Jul 04, 2006 6:41 am

chulett wrote:So... this is a Sequence job calling a multi-instance Server job? Once or many times? How are you handling the uniqueness that the Invocation ID needs? Any chance that it is running into itself?

If you have more in the way of error messages, post them. The ones that surround this one, for example or any from the other log.

A surrogate key is assigned to the invocation ID . As its a running sequence number handling of the invocation ID does not seem to be a problem. All other multi instance server jobs are running fine except for this one.

chulett · Post by **chulett** » Tue Jul 04, 2006 6:46 am

Ok... then what's different about this one? Must be something. And how about those log messages, anything else worth sharing?

kumar_s · Post by **kumar_s** » Tue Jul 04, 2006 8:17 am

What is the status of the job EligPxiFileNameCoalitionJob.1832 in director?