We have a Windows 2000 SP 3 1.6 GHz Xeon Server
dual processors with 3 GB RAM. Periodically, our
scripts will hang in the queue with a Running
status while the logs show the script as finished.
This holds up any scripts that need to run after the
script in the same queue. The first thought was to
bind the Linc reports that the scripts run through BindCPU
or the RunConfig command, but scripts that do not
run any Linc reports or external processes are getting
stuck. What do we need to do to stop scripts from
getting stuck in the queues like this?

Is that random or you see a pattern there? Have you tried to set these jobs run detached using the "detached job" property?

: We have a Windows 2000 SP 3 1.6 GHz Xeon Server
: dual processors with 3 GB RAM. Periodically, our
: scripts will hang in the queue with a Running
: status while the logs show the script as finished.
: This holds up any scripts that need to run after the
: script in the same queue. The first thought was to
: bind the Linc reports that the scripts run through BindCPU
: or the RunConfig command, but scripts that do not
: run any Linc reports or external processes are getting
: stuck. What do we need to do to stop scripts from
: getting stuck in the queues like this?

The jobs sticking in the queue does appear to be
random. I have set up a test on our test server
that eventually causes one of the queues to stick.
I will try the detach property and see if that does
the trick.

: Is that random or you see a pattern there? Have you tried to set these jobs
: run detached using the "detached job" property?