I am using a single 24 x 7 VBScript to run several
Crystal Reports under CR 9. When I run the job with
Run Now, *all* of the reports successfully complete.
However, when I schedule the job, only *two* of the
reports complete, and 24 x 7 says the job is
completed.

I am looking for the reason that the job would work
fine when Run Now, but not when scheduled.

[funny, when I previewed this message, it had my
correct email address, but said I was Ryan Pieszak!]

Not to get off topic, but I just ran a test message, and the preview said I was "Merrick Stemen".
As far as the schedule vs. run now, I remember reading in the forum somewhere, or perhaps in the software help, that there is definitely a difference between the two. If you haven't already, do a search in the forums, I think that's how I read about this issue. Wish I could tell you more.
The real Ryan Pieszak

: I am using a single 24 x 7 VBScript to run several
: Crystal Reports under CR 9. When I run the job with
: Run Now, *all* of the reports successfully complete.
: However, when I schedule the job, only *two* of the
: reports complete, and 24 x 7 says the job is
: completed.

: I am looking for the reason that the job would work
: fine when Run Now, but not when scheduled.

: [funny, when I previewed this message, it had my
: correct email address, but said I was Ryan Pieszak!]

Thank you. I did find this:

"Run Now" is for job testing and immediate run. It is always synchronous and always runs "outside of job queues" in the foreground. Because of that if a "run now" job hangs it will hang the scheduling engine and no jobs will run until the scheduler is restarted. However, jobs that are already running will continue to run until finish or killed. Jobs already queued will stay in their queues forever.

I will look into this now. I am also having jobs that hang forever whether I run them scheduled or not. I may need to do a reinstall.

: Not to get off topic, but I just ran a test message, and the preview said I
: was "Merrick Stemen".
: As far as the schedule vs. run now, I remember reading in the forum
: somewhere, or perhaps in the software help, that there is definitely a
: difference between the two. If you haven't already, do a search in the
: forums, I think that's how I read about this issue. Wish I could tell you
: more.
: The real Ryan Pieszak

Set the job to run synchronous.

: Thank you. I did find this: "Run Now" is for job testing and
: immediate run. It is always synchronous and always runs "outside of
: job queues" in the foreground. Because of that if a "run
: now" job hangs it will hang the scheduling engine and no jobs will
: run until the scheduler is restarted. However, jobs that are already
: running will continue to run until finish or killed. Jobs already queued
: will stay in their queues forever.

: I will look into this now. I am also having jobs that hang forever whether I
: run them scheduled or not. I may need to do a reinstall.

: Set the job to run synchronous.

Ok. I have set the job to run synchronous, but I also had to turn-off detached in order to get all eight reports to run. When it was still detached, it only ran two reports.
Also, when I run it detached, and it only prints two reports, 24 x 7 adds another clock icon to the systray. Each one says it is running the job, but the log reports that the job is finished. These icons stay in the systray until I kill the processes.

Every detached job is run by a separate instance of 24x7. Each instance in turn creates it's own icon in the system tray to indicate a presense of 24x7 job engine. If the job terminates abnormally for example when the job script calls TeminateProcess or other "Terminate" method that causes the processing to abort the left-over 24x7 icon remains in the system tray

: Ok. I have set the job to run synchronous, but I also had to turn-off
: detached in order to get all eight reports to run. When it was still
: detached, it only ran two reports.
: Also, when I run it detached, and it only prints two reports, 24 x 7 adds
: another clock icon to the systray. Each one says it is running the job,
: but the log reports that the job is finished. These icons stay in the
: systray until I kill the processes.