I've got synchronous jobs running that get all mangled when spawning occurs. Is there a way to prevent spawning or have 24x7 flag it somehow such that I could kill/restart 24x7 when it occurs?
v. 3.4.21

I am not sure I undestand what you mean. Do you mean jobs that never complete or something else?

: I've got synchronous jobs running that get all mangled when spawning occurs.
: Is there a way to prevent spawning or have 24x7 flag it somehow such that
: I could kill/restart 24x7 when it occurs?
: v. 3.4.21

: I am not sure I undestand what you mean. Do you mean jobs that never complete
: or something else?

If I click to close 24x7, a window pops up that says "1 spawned process is still running...". This indicates that an error & hence "spawning" has occurred. Under normal conditions, I click to close & I get the normal exit confirmation message.

The jobs that 24x7 fires off can not run at the same time. They must run sequentially, & yet "spawning" seems to fire off multiple instances of the process & the system becomes unstable & has to be re-booted in the morning. When spawning occurs I'd rather have 24x7 terminate & have the 24x7Monitor.exe application that the programmer wrote re-start it.

At least then, I could get the system to survive the night.

: If I click to close 24x7, a window pops up that says "1 spawned process
: is still running...". This indicates that an error & hence
: "spawning" has occurred. Under normal conditions, I click to
: close & I get the normal exit confirmation message.

: The jobs that 24x7 fires off can not run at the same time. They must run
: sequentially, & yet "spawning" seems to fire off multiple
: instances of the process & the system becomes unstable & has to be
: re-booted in the morning. When spawning occurs I'd rather have 24x7
: terminate & have the 24x7Monitor.exe application that the programmer
: wrote re-start it.

: At least then, I could get the system to survive the night.

Viewing the log, I see Error 32. The file cannot be copied because it is still being used by another process. Is there a way to setup an inidcator to tell when the file is no longer in access & ready to be copied? I've increased the wait, but continue to get the error. It happens about twice in the night (15 hour period) for a job that runs every 5 minutes.

1. Check these jobs are set to run in the same queue and set to run synchronous. This will ensure they run sequentially only.
2. To verify a file is locked or free you can use the following code logic

OnErrorResumeNext
FileOpen ..., file_number
OnErrorStop
IfThen file_number, PROCESS_IT
// ...handle locked file problems here ...

PROCESS_IT:

3. The FileCopy.exe utility in most cases can copy locked files. For more info and to download please see
http://www.softtreetech.com/24x7/archive/44.htm

: Viewing the log, I see Error 32. The file cannot be copied because it is
: still being used by another process. Is there a way to setup an inidcator
: to tell when the file is no longer in access & ready to be copied?
: I've increased the wait, but continue to get the error. It happens about
: twice in the night (15 hour period) for a job that runs every 5 minutes.