I am running 24x7 version 3.4.5 registered on a Windows XP Pro system. I have a scheduled JAL script that runs 8 separate VB script jobs.
(I also have a similar one that runs 20 VB script jobs.)

Some of the VB script jobs are marked to run detached, others are not. None of the jobs run asynchronous. When run on this system, everything works fine; however, when they are run on our test server, which has 24x7 version 3.4.10a, the JAL job goes into the queue and sits there with a status of "Running".
The queue monitor says:
Queue |Job#|Time Queued |Priority|Status |JobID|Job Name |Time Job Started |Size |Size in Q|Ratio|
[default]|1 |7/15/2003 15:15:00|Normal |Running|134 |Run Weekly Report|7/15/2003 15:15:01|1,706|762 |55.3%|

The job started 7/15/2003 15:15:00; it is currently 7/16/2003 08:45:00, and this job is still in there with a whole lot of other ones behind it.

The server is a Windows 2000 SP 3 1.6 GHz Xeon Server dual processors with 3 GB RAM.

I have been having this problem regularly. I will schedule a job, 24x7 will be counting down to execution, the time will reach zero, there's a pause, and then that's it: job in queue forever until I kill 24x7. If I click Run Now, everything works fine on both systems, but that kind of defeats the purpose of scheduling...

Do you have any ideas?

24x7 is waiting for the operation system (more specifically from the Windows Scripting Host) to report that the process is completed, but it does not get that message. As a result the job state remains running and the job itself remains staying in the queue.

Here is what I would like to suggest as a workaround:

1. Copy scripts from your VBS jobs to external files with .VBS extension
2. Change type of each of these jobs from "run script" to "run program or document file". Select saved .VBS files as documents to run.
3. Set each job to synchronous and set some reasonable timeout value. In case if your VBScript hangs the job will kill it after the specified timeout value.

This should get your going and make your system more reliable than it is now.

: I am running 24x7 version 3.4.5 registered on a Windows XP Pro system. I have
: a scheduled JAL script that runs 8 separate VB script jobs.
: (I also have a similar one that runs 20 VB script jobs.)

: Some of the VB script jobs are marked to run detached, others are not. None
: of the jobs run asynchronous. When run on this system, everything works
: fine; however, when they are run on our test server, which has 24x7
: version 3.4.10a, the JAL job goes into the queue and sits there with a
: status of "Running".
: The queue monitor says: Queue |Job#|Time Queued |Priority|Status |JobID|Job
: Name |Time Job Started |Size |Size in Q|Ratio|
: [default]|1 |7/15/2003 15:15:00|Normal |Running|134 |Run Weekly
: Report|7/15/2003 15:15:01|1,706|762 |55.3%|

: The job started 7/15/2003 15:15:00; it is currently 7/16/2003 08:45:00, and
: this job is still in there with a whole lot of other ones behind it.

: The server is a Windows 2000 SP 3 1.6 GHz Xeon Server dual processors with 3
: GB RAM.

: I have been having this problem regularly. I will schedule a job, 24x7 will
: be counting down to execution, the time will reach zero, there's a pause,
: and then that's it: job in queue forever until I kill 24x7. If I click Run
: Now, everything works fine on both systems, but that kind of defeats the
: purpose of scheduling...

: Do you have any ideas?