After some research, I realize that the problem
documented in my post "Semaphore ignored... " on
9/2/2003 is really the same problem that Bill Richardson
mentions in his "Job Hung in Queue as Running".
In my case the job that is shown as running does not
exist anymore (I know what the PID was for the job
and it doesn't appear in the task manager).

Also, moving each job to a separate queue will help
because the hung job will not affect others. But it
will still jam up the queue that it runs in .

This is happening for one of 5 customers only; the
other 4 are not having problems. This customer is
running Win2000 SP3.

Also this seems to be similar to the post
"Job hangs after they are finished 9/22/2003". In that
post the response was to install an MS application as
a fix for this problem.
Was there a incorrect DLL version at fault here? If so,
can you say which it was and what the correct DLL versions
should be?
Thanks for your support....

Unfortunately I do not know exactly which DLL or DLLs are responsible for this. These DLLS and not loaded directly from 24x7, they are actually dependencies of some other MS system DLLs. The way to fix is to install MS Office or other significant MS application that updates and synchronizes all system DLLs.

A good indicator if a system may have the job hanging problem is to temporary enable job status display option in Tools/Options/Log. If the little status window hangs after a job run, this indicates a good chance that asynchronous jobs may also hang. If this happens to you and you cannot install Office on your computer, convert all jobs to synchronous jobs. This helps to avoid queue jamming issues.

: After some research, I realize that the problem
: documented in my post "Semaphore ignored... " on
: 9/2/2003 is really the same problem that Bill Richardson
: mentions in his "Job Hung in Queue as Running".
: In my case the job that is shown as running does not
: exist anymore (I know what the PID was for the job
: and it doesn't appear in the task manager).

: Also, moving each job to a separate queue will help
: because the hung job will not affect others. But it
: will still jam up the queue that it runs in .

: This is happening for one of 5 customers only; the
: other 4 are not having problems. This customer is
: running Win2000 SP3.

: Also this seems to be similar to the post
: "Job hangs after they are finished 9/22/2003". In that
: post the response was to install an MS application as
: a fix for this problem.
: Was there a incorrect DLL version at fault here? If so,
: can you say which it was and what the correct DLL versions
: should be?
: Thanks for your support....

I changed the job status options as you recommended
and found that a job HUNG almost immediately.
The litte window did not hang but the job in the
queue ended and stayed in RUNNING status.

Thinking this is a fluke, I killed 24x7 (its the
only way to clear this problem BTW, please see
Bill Richardsons post below) and restarted.

It did the same thing again.

Was this what was expected. My understanding was that
the little job status window should not have been
cleared.

I disabled the job status option and restarted and
the queues process normally now (at least until the
next random problem).

Please comment on this.

Sorry I really have no comments at this time. Hope this will not happen again. Please let us know if that happens again.

: I changed the job status options as you recommended
: and found that a job HUNG almost immediately.
: The litte window did not hang but the job in the
: queue ended and stayed in RUNNING status.

: Thinking this is a fluke, I killed 24x7 (its the
: only way to clear this problem BTW, please see
: Bill Richardsons post below) and restarted.

: It did the same thing again.

: Was this what was expected. My understanding was that
: the little job status window should not have been
: cleared.

: I disabled the job status option and restarted and
: the queues process normally now (at least until the
: next random problem).

: Please comment on this.