I have a job that is set to run every five minutes
from 10/26/2004 at 10:00am until 1999 at 11:00pm.
The job ran the first day I added it then simply
stopped running at 00:00:38 the next day. The
interval is set to run from 12:00am to 11:59pm.

We are running version 3.4.22 and are experiencing
a wide range of problems. Are there known issues
with this release?

: I have a job that is set to run every five minutes
: from 10/26/2004 at 10:00am until 1999 at 11:00pm.
: The job ran the first day I added it then simply
: stopped running at 00:00:38 the next day. The
: interval is set to run from 12:00am to 11:59pm.

: We are running version 3.4.22 and are experiencing
: a wide range of problems. Are there known issues
: with this release?

I meant 9999....

I am not sure that 9999 is a valid year number. Please try 2999 instead. If you set the end date to all zeroes the schedueler will internally use 1/1/3000 as the end value. I believe this is the maximum supported date value.

Also check if the job appears in the Job Monitor as pending.

: I meant 9999....

: I am not sure that 9999 is a valid year number. Please try 2999 instead. If
: you set the end date to all zeroes the schedueler will internally use
: 1/1/3000 as the end value. I believe this is the maximum supported date
: value.

: Also check if the job appears in the Job Monitor as pending.

We had it scheduled for 9999 but it still did not work . Another job that is not working has a 01/01/2006. Do you have any other suggestions.

Do they appear in the job monitor?
What appears in the "next start date/time" columns in the job details view?

: We had it scheduled for 9999 but it still did not work . Another job that is
: not working has a 01/01/2006. Do you have any other suggestions.

: Do they appear in the job monitor?
: What appears in the "next start date/time" columns in the job
: details view?

I have done all of the basic troubleshooting.
One thing weird that I am noticing is that it will run automatically sometimes. Meaning it ran automatically for a few days then didn't run for a week.
We quite often have to restart because this product tends to hang up jobs quite a bit.

Do you think the startup process is corrupt?