I am running version 2.4.15 of 24x7. I have several JAL script jobs that having been running fine for about a month. Most run once daily, but I have one that is scheduled to run every 5 minutes. They are all non asynchronous jobs. For some reason, they will no longer run when scheduler. If I use the 'run now' option, they run fine. They will just not kick off when scheduled to do so. If I update the properties of a job to run in the future, the properties indicate the job has been updated. I am running 24x7 as a service. Any clue?

Enable logging for that job so in the job log you can see messages like "job started", "job error", etc...

Does the job have "end date" defined? If yes, is it in the past?

Is the job enabled?

: I am running version 2.4.15 of 24x7. I have several JAL script jobs that
: having been running fine for about a month. Most run once daily, but I
: have one that is scheduled to run every 5 minutes. They are all non
: asynchronous jobs. For some reason, they will no longer run when
: scheduler. If I use the 'run now' option, they run fine. They will just
: not kick off when scheduled to do so. If I update the properties of a job
: to run in the future, the properties indicate the job has been updated. I
: am running 24x7 as a service. Any clue?

: Enable logging for that job so in the job log you can see messages like
: "job started", "job error", etc...

Logging is enabled for all 25 or so jobs.

: Does the job have "end date" defined? If yes, is it in the past?

There are over 25 jobs. None have an end date.

: Is the job enabled?

All jobs are enabled.

: Logging is enabled for all 25 or so jobs.
do you get "job started" event logged?

: There are over 25 jobs. None have an end date.
Every job has an end date and time. Please click on a job and switch to the Properties view (second tab) scroll down and check the end date. By default (if you never touched it) end date should be 1/1/3000

: All jobs are enabled.
Does the "not-running" job have "skip late" option enabled or "disable on error"
If "skip late" option is enabled what value do you have for the maximum delay.

By the way, did I understand you correctly that just one job that was previously running doesn't run anymore and all other jobs run fine?

: do you get "job started" event logged?
: Every job has an end date and time. Please click on a job and switch to the
: Properties view (second tab) scroll down and check the end date. By
: default (if you never touched it) end date should be 1/1/3000
: Does the "not-running" job have "skip late" option
: enabled or "disable on error"
: If "skip late" option is enabled what value do you have for the
: maximum delay.

: By the way, did I understand you correctly that just one job that was
: previously running doesn't run anymore and all other jobs run fine?

No, you misunderstood. None of the jobs are running. All 29 to be exact have just stopped being kicked off by the timer event. BTW, when I click on the Properties tab the end date is blank for every 29 of these jobs.

Are you running 24x7 version 1 or 2 by any chance? If yes, check that you don't have a synchronous jobs running forever and holding the other. Such job should have "job started" event logged in the job log and no "job finished".

: No, you misunderstood. None of the jobs are running. All 29 to be exact have
: just stopped being kicked off by the timer event. BTW, when I click on the
: Properties tab the end date is blank for every 29 of these jobs.

: Are you running 24x7 version 1 or 2 by any chance? If yes, check that you
: don't have a synchronous jobs running forever and holding the other. Such
: job should have "job started" event logged in the job log and no
: "job finished".

I am running version 2.4.15. I have checked and there are no jobs running. In fact, the machine was rebooted and the problem persists.

: I am running version 2.4.15. I have checked and there are no jobs running. In
: fact, the machine was rebooted and the problem persists.

I've run into that type of problem a couple of times on a version 3 system. What I found was that if I hit F4 and walk through the entire Job Properties Wizard, that seems to knock these jobs loose. Try looking at the 'Monitor' first to see if these jobs are truly scheduled, then review again after walking the wizard and don't forget to click 'Save'.