I have a 24x7 job that looks for a trigger file on another machine and kicks into action when it finds the trigger
file. It is set up to look for the trigger file in the job's properties, but not to delete, rename, or move it. It is
set to look for the trigger file every 1 minute. I was running this on a Win 2k server and it worked fine. Now, I have
the same script running on a Win XP server and I am having problems. It seems to see the trigger file, start the job,
then immediatly see the trigger file again, and start the job again - sometimes even 3 times. I can't figure out why it's
doing this. I've tried making the job synchronous and have tried detached and not detached.

Any suggestions would be greatly appreciated.

Check the job properties again (use the Properties page). I bet the timing is set to 1 second or something like that instead of 1 minute. Or somehow you got multiple instances of 24x7 scheduling engine running concurrently and each finding the same file. Check the Task Manager. If you have terminal services enabled, disable them.

: I have a 24x7 job that looks for a trigger file on another machine and kicks
: into action when it finds the trigger
: file. It is set up to look for the trigger file in the job's properties, but
: not to delete, rename, or move it. It is
: set to look for the trigger file every 1 minute. I was running this on a Win
: 2k server and it worked fine. Now, I have
: the same script running on a Win XP server and I am having problems. It seems
: to see the trigger file, start the job,
: then immediatly see the trigger file again, and start the job again -
: sometimes even 3 times. I can't figure out why it's
: doing this. I've tried making the job synchronous and have tried detached and
: not detached.

: Any suggestions would be greatly appreciated.