What is the job type?
Are you running ".exe" files? if yes, enable "run as detached" option and try running the job.
It is calling to a .bat file. The .bat calls some other files and orders the job within the application's internal scheduler. The job stays running in the scheduler but it gets "marked dead" the error right before the fork failure said it had reached max run iterations (maxcheckloops).
The agent itself will let jobs run as long as they take -- minutes, hours, days, etc.
Is this a Windows or Linux box?
It is a Windows box. This job continues to run even after Control-M marks it dead. It errored that max iterations (Maxloopcheck) had been reached. This is the ONLY job that we have that does this and I can sit and watch it complete within the application well after it was marked "not good" by Control-M.
Hi Robert, FORK failure in windows is due to the permission issue. Please provide permission to the path, where the script is executing for the user(service account). Try to find the permission before and after success/failure of the job.
Hello Robert, I got a similar issue, do you have any suggestion?
Thanks in advance.
If there is a communication failure, Control-M won't mark those jobs as failed. Rather it will say unknown status.
Job status is tracked by agent itself and later on passed to the server.
Whats annoying here is that there seems to be 3-4 solutions almost similar to each other, this is not a straight forward solution it seems.
In simple terms , what does this error even mean?
does it mean that while the program .exe or batch file was running , there was a problem during its journey and thus the error message?
So in the middle of the journey
Vikas Jha seems to put it simple.
I have checked permission on my machine which i am running this job and the run as user has the privilege.
I have tried to change the job to run as a script, which appears to be like Control-M 7 where you can make the job type a "job" not a "command" is this right?
so i have a job - this is the command:
D:\Apps\AMZ\BatchIDRequest.exe %%BUSINESS_DATE ZA
I tried to run that now as a Script
File path: D:\Apps\AMZ
File name: AMZBatchIDRequest.exe
I have tried to add/append to the SET tab these extra parameters:
PARM1 with value %%BUSINESS_DATE
PARM2 with value ZA
The fork failure message has gone away but now i get a message:
13:41:36 2018/06/14 JOB FAILED TO EXECUTE DUE TO USER ENVIRONMENT 5112