Greetings:

There was a similar post to this one last month from a fellow named Lewis.

I'm now running version 3.3.0 on Windows2000Pro, PentiumII-233MHz, 384MB RAM.

Several jobs are scheduled, not disabled, but never run. Logging is enabled for ALL jobs, but there are NO entries in the log 'Started' or otherwise. All of my jobs are JAL.

What's making these jobs STOP???

Thanks!

Neil.....

Greetings

Please check that you have free room in the job queue to which those jobs are assigned. If the queue is full or waiting for some run-away job to terminate new jobs will stay in that queue as long as the job queue is busy.

You can use the Queue monitor to check on that.

: Greetings: There was a similar post to this one last month from a fellow
: named Lewis.

: I'm now running version 3.3.0 on Windows2000Pro, PentiumII-233MHz, 384MB RAM.

: Several jobs are scheduled, not disabled, but never run. Logging is enabled
: for ALL jobs, but there are NO entries in the log 'Started' or otherwise.
: All of my jobs are JAL.

: What's making these jobs STOP???

: Thanks!

: Neil.....

: Greetings: There was a similar post to this one last month from a fellow
: named Lewis.

: I'm now running version 3.3.0 on Windows2000Pro, PentiumII-233MHz, 384MB RAM.

: Several jobs are scheduled, not disabled, but never run. Logging is enabled
: for ALL jobs, but there are NO entries in the log 'Started' or otherwise.
: All of my jobs are JAL.

: What's making these jobs STOP???

: Thanks!

: Neil.....

Neil,

We experienced the same thing that you describe. All jobs scheduled to run, not disabled but never would run. Logging enabled... All jobs JAL. I could run each job using the 'Run now' command, they just wouldn't kick off automatically.

By trial and error, we discovered that the database DAT file had somehow become corrupt. By restoring the file from backup, everything began running successfully. It probably was not corrupted by 24x7, but there was no other posting that mentioned a corrupted database file before.