I'm running the 24x7 scheduler but when I go to execute
a job, the job doesn't run and I get a message in the
schedule.log stating:

Job Started
Process finished with exit code 128
Job Finished

I bounced the service and recreated the job and I'm
still getting this error.

Any suggestions?

Thanks,
Brian

: I'm running the 24x7 scheduler but when I go to execute
: a job, the job doesn't run and I get a message in the
: schedule.log stating: Job Started
: Process finished with exit code 128
: Job Finished

: I bounced the service and recreated the job and I'm
: still getting this error.

: Any suggestions?

: Thanks,
: Brian

24x7 actually attempts to run the specified program. It is just the program terminates quickly with the exit code 128 which is why you don't see it running.

Find out from the program documentation or program vendor what code 128 means.

My guess, it is some kind of a security or network access issue. Starting processes from services is sometimes very tricky. Services have lots of limitations and all started processes inherit all these limitations. For example, common mistake is usage of network share mappings. With services you can only use UNC file names.

: 24x7 actually attempts to run the specified program. It is just the program
: terminates quickly with the exit code 128 which is why you don't see it
: running.

: Find out from the program documentation or program vendor what code 128
: means.

: My guess, it is some kind of a security or network access issue. Starting
: processes from services is sometimes very tricky. Services have lots of
: limitations and all started processes inherit all these limitations. For
: example, common mistake is usage of network share mappings. With services
: you can only use UNC file names.

Thanks, for the reply. I'll let you know if we get
it resolved.

: Thanks, for the reply. I'll let you know if we get
: it resolved.

Just letting you know this one has been resolved.
I think the problem was due to the windows scheduler
not working (diabled or hung). Anyway a reboot of the
server started the windows scheduler back up and Job
Manager(24x7) is now working again.

Thanks,

Brian