I had all my 24x7 jobs stop being dispatched by the service.
The jobs had been getting dispatched for several days without problem.
No 24x7 errors were logged; the service was still started, and the 2
24x7 EXEs still showed up in Task Manager. I'm at v3.3.8 and
running on Win2K Server. I can send you the schedule log and stat log,
but nothing interesting is in there, other than seeing when the last
job was dispatched.

Anything else I can check? What can I do to troubleshoot a recurrence?

Thank you.

Did the process hang or service paused?
Is the service status "paused"?
Do you see in the task Manager 24x7 using any CPU?

: I had all my 24x7 jobs stop being dispatched by the service.
: The jobs had been getting dispatched for several days without problem.
: No 24x7 errors were logged; the service was still started, and the 2
: 24x7 EXEs still showed up in Task Manager. I'm at v3.3.8 and
: running on Win2K Server. I can send you the schedule log and stat log,
: but nothing interesting is in there, other than seeing when the last
: job was dispatched.

: Anything else I can check? What can I do to troubleshoot a recurrence?

: Thank you.

The service status was "started". It's hard to tell in task manager
if 24x7 is using CPU, because it generally shows 0% except
when it is executing a job. And of course in my situation, no
jobs were being dispatched. To get things going again, I stopped
and restarted the 24x7 Service.

: Did the process hang or service paused?
: Is the service status "paused"?
: Do you see in the task Manager 24x7 using any CPU?

Try to find which job ran last. If that happens again check if it is again the same job and if yes, set that job to run detached, otherwise try to find if there is a job or time pattern leading to the job engine stop.

: The service status was "started". It's hard to tell in task manager
: if 24x7 is using CPU, because it generally shows 0% except
: when it is executing a job. And of course in my situation, no
: jobs were being dispatched. To get things going again, I stopped
: and restarted the 24x7 Service.

Thank you for your help thus far. All of my jobs are running detached.
In fact, I detached all my jobs in order to troubleshoot a memory leak
within 24x7. I still have this leak, albeit at a slower rate than when the
jobs were not all detached. The leak grows after a job runs. When job
dispatching was stopped, 24x7.exe's mem usage was 29,096KB as reported
in Task Mgr. That is not that large.

: Try to find which job ran last. If that happens again check if it is again
: the same job and if yes, set that job to run detached, otherwise try to
: find if there is a job or time pattern leading to the job engine stop.

How big is that memory leak?

: Thank you for your help thus far. All of my jobs are running detached.
: In fact, I detached all my jobs in order to troubleshoot a memory leak
: within 24x7. I still have this leak, albeit at a slower rate than when the
: jobs were not all detached. The leak grows after a job runs. When job
: dispatching was stopped, 24x7.exe's mem usage was 29,096KB as reported
: in Task Mgr. That is not that large.