Job control fatal error (-14)

Amit_111 · Post by **Amit_111** » Mon Jul 07, 2008 4:44 am

Hi All,

we have been receiving this error "Job control fatal error (-14)" for last 2-3 days. I searched this forum and found out that this error generally comes when the CPU and Memory is overloaded.

But we checked our CPU and Memory utilization which was normal and not overloaded but still we received this error. The CPU Utilization was around 70% and the Memory Utilization was around was also around 60-70%.

Is there any other reason for this error other that Overloading of CPU.

Thanks in Advance.

ray.wurlod · Post by **ray.wurlod** » Mon Jul 07, 2008 4:53 am

Did you check while the job was starting, or at some other time?

Timeouts can be caused by lots of other things, like failure to connect to a database.

Amit_111 · Post by **Amit_111** » Mon Jul 07, 2008 7:23 am

Hi Ray,

Actually we monitored the time frame for almost 2 hours to see if at any moment the utilization is 100% but no where it went up to the 100 mark so we just wondered if there are any other reasons also due to which this error is shown.

Thanks.

chulett · Post by **chulett** » Mon Jul 07, 2008 7:29 am

It doesn't need to be 100% to cause this error, just 'busy enough' to cause the job to take longer than the timeout value to start. And from what I recall, that value is 60 secods.

Amit_111 · Post by **Amit_111** » Mon Jul 07, 2008 7:57 am

Hi Craig,

Yes, the time out is 60 Seconds but still I am not getting that if the CPU and Memory is free what are the other possible reasons which would stop the DS Server from executing a DS Job and throwing the Error (-14) and the timeout error.

Thanks.

kcbland · Post by **kcbland** » Mon Jul 07, 2008 8:24 am

One other circumstance back on 6.0 was when you tried to run a non-multi-instance enabled job as a multi-instance via job control. Since you didn't state this as the case, it's probably a server resources.

You may wish to try the Microsoft solution and reboot the server to take care of any questions regarding the state of the server. Consider upgrading to 7.5 and applying the patches that allow you to change the timeout value to something higher.

John Smith · Post by **John Smith** » Mon Jul 07, 2008 7:32 pm

How many jobs are you running at a point in time concurrently? Perhaps you are utilising all the resources in your server and some of the jobs waited too long (1 minute) to start up and therefore aborted?

Amit_111 · Post by **Amit_111** » Mon Jul 07, 2008 11:04 pm

When the execution of job started the CPU/Memory utilization in that time frame was 70%. May be as stated by Craig, the new jobs waiting to start might be requiring more resources then what ever is free and hence getting timed out even though the utilization is not 100%.

Thanks.