We've been using the 24x7 Scheduler for several
months now as a Windows service. A few times the
scheduled jobs will stop executing completely
while the service is still up and running. When I
view the 24x7 log to investigate the last entry
normally I see a 'job finished' entry (i.e. there is
no hung process). Any ideas on this?

In reviewing the posted messages I also noticed a
problem with running scheduled jobs twice
(unintentionally) simultaneously. We have experienced
that problem also. You advised that version 3.4 was
pending and that it would eliminate the problem.
When will version 3.4 be available? We are running
version 3.3 right now. Will an upgrade to 3.3.8
help any with my first problem? Thanks. Rick

If this happens again, please check in the Task Manager for existence of 24x7srv.exe and 24x7.exe. Both processes should be running.
Also check how many threads and handles are allocated by 24x7. You may need to customize Task Manager view and to add these columns to the display. If the number of threads or handles is excessive it can cause 24x7 to hang as it will not be able to allocate new resources for new jobs. If this is the case you will need to find which jobs lead to resource leaking and set these jobs to run detached.

PS. V3.4 is coming by the end of this week.

: We've been using the 24x7 Scheduler for several
: months now as a Windows service. A few times the
: scheduled jobs will stop executing completely
: while the service is still up and running. When I
: view the 24x7 log to investigate the last entry
: normally I see a 'job finished' entry (i.e. there is
: no hung process). Any ideas on this?

: In reviewing the posted messages I also noticed a
: problem with running scheduled jobs twice
: (unintentionally) simultaneously. We have experienced
: that problem also. You advised that version 3.4 was
: pending and that it would eliminate the problem.
: When will version 3.4 be available? We are running
: version 3.3 right now. Will an upgrade to 3.3.8
: help any with my first problem? Thanks. Rick

: If this happens again, please check in the Task Manager for existence of
: 24x7srv.exe and 24x7.exe. Both processes should be running.
: Also check how many threads and handles are allocated by 24x7. You may need
: to customize Task Manager view and to add these columns to the display. If
: the number of threads or handles is excessive it can cause 24x7 to hang as
: it will not be able to allocate new resources for new jobs. If this is the
: case you will need to find which jobs lead to resource leaking and set
: these jobs to run detached.

: PS. V3.4 is coming by the end of this week.

I've set up the offending jobs to run in 'detached' mode.
That seemed to work for awhile until this past weekend
when the scheduler service stopped executing jobs again.
This morning I checked and both 24x7srv.exe and 24x7.exe
were running but nothing had executed since 5:00 PM on
Saturday (we have one job execute every 10 minutes). The
event log shows nothing unusual and indicates that the
last job at 5:00 PM on Saturday finished successfully.
Any ideas on this? Perhaps it is somehow having heartburn with
the .exe that is scheduled to run - a FoxPro program
that is mapped from a network server (i.e. not local).

Also, I don't see version 3.4 yet out on your web site...

Since you run 24x7 as a service and cannot use the Queue Monitor, use the Windows Explorer
to check how many files you have in the job queue directories (C:\Program Files\24x7 Automation 3\Queue\...) If you see some files there it means that one or more synchronous jobs hanged holding the entire queue. File names match job IDs so you can easily find which job is causing the problem.

Please also check in the task manager how many handles and threads are allocated to 24x7.exe. If the number is too excessive this would indicate that the system ran out of resources (number of handles and threads is limited to each application and cannot exceed 32K).

: I've set up the offending jobs to run in 'detached' mode.
: That seemed to work for awhile until this past weekend
: when the scheduler service stopped executing jobs again.
: This morning I checked and both 24x7srv.exe and 24x7.exe
: were running but nothing had executed since 5:00 PM on
: Saturday (we have one job execute every 10 minutes). The
: event log shows nothing unusual and indicates that the
: last job at 5:00 PM on Saturday finished successfully.
: Any ideas on this? Perhaps it is somehow having heartburn with
: the .exe that is scheduled to run - a FoxPro program
: that is mapped from a network server (i.e. not local).

: Also, I don't see version 3.4 yet out on your web site...