Two things come to mind that could the different between normal run and debugging: 1. Timing. If in debugging you do it step-by-step your give your processes more time because of the pauses.
2. The debugger runs your job in the foreground, the normal mode runs it in the background. If you start poorly written processes requiring full access to the Desktop then you may have a difficult time running them in the background. Regarding usage of the Terminal Services. The nature and purpose of the Terminal Server is to provide multiple virtual terminal physically hosted on the same computer. Unless you login in exclusive mode as a system admin, your virtual session is suspended or closed completely after timeout when you logout. If this is the case, no scheduled processes will run after you logout. Either login exclusive and install 24x7 as a system service running under LocalSystem account or even much better do not use Terminal Services to install, configure and control "always-up" processes. With Terminal Services you will have hard time scheduling jobs. : Hi, : I got a funny situation. I have a job scheduled, and it runs, but it stops
: working half way through. However, when I run it through the debug, it
: finishes no problem.
: Why would this be happening? : I've also got jobs that don't fire off even though I have them scheduled.
: I've triple-checked these jobs many times, and I don't understand why they
: aren't firing off at all.
: I'm controlling the server which runs 24x7 through Remote Desktop (Term
: Services). Some other people may also be logged onto the server though
: term services (although not using 24x7 program). Could this cause any
: problems? : Thanks!
|
