I have a couple of jobs scheduled to run an EXE every Monday - Friday at 8:40 AM and 4:00 PM respectively. These sometimes run at the scheduled time, and sometimes don't. Many times, they run at some other unrelated time. Other times they don't run at all.

These jobs are Async, running on the local host, set for Daily with Mon-Fri days of the week checked. They are scheduled to start at 08:40 AM and 4:00 PM. The "Skip this job" option is not set.

This week, the 8:40 AM job did not run Mon-Wed at all, and kicked off on Thurday at 12:36 AM. The log only shows the Thursday job starting and stopping. No other entries. The 4:00 PM job has not run at all this week.

These are not the only two jobs doing this. Also, there are some jobs running as scheduled without problem. This problem has been occasionally showing itself over the last two or three months.

I am running version v3.1.3 of 24x7. The EXE is dated 11/7/01 10:10 PM and the libs are dated 12/14/01 8:37 AM. This is on an NT 4.0 Server.

Where would I be able to look to see why this job is not being initiated by 24x7?

Was the job database migrated from an older version of 24x7?
Did you make any changes in the existing jobs recently ("last two or three months") or perhaps created a new job?

: I have a couple of jobs scheduled to run an EXE every Monday - Friday at 8:40
: AM and 4:00 PM respectively. These sometimes run at the scheduled time,
: and sometimes don't. Many times, they run at some other unrelated time.
: Other times they don't run at all.

: These jobs are Async, running on the local host, set for Daily with Mon-Fri
: days of the week checked. They are scheduled to start at 08:40 AM and 4:00
: PM. The "Skip this job" option is not set.

: This week, the 8:40 AM job did not run Mon-Wed at all, and kicked off on
: Thurday at 12:36 AM. The log only shows the Thursday job starting and
: stopping. No other entries. The 4:00 PM job has not run at all this week.

: These are not the only two jobs doing this. Also, there are some jobs running
: as scheduled without problem. This problem has been occasionally showing
: itself over the last two or three months.

: I am running version v3.1.3 of 24x7. The EXE is dated 11/7/01 10:10 PM and
: the libs are dated 12/14/01 8:37 AM. This is on an NT 4.0 Server.

: Where would I be able to look to see why this job is not being initiated by
: 24x7?

The jobs were created in the previous 2.x version of 24x7.

I changed a couple of settings within the jobs since the upgrade to the new version. For instance, I checked the "notify on error" option. Other than than, all is the same.

: Was the job database migrated from an older version of 24x7?
: Did you make any changes in the existing jobs recently ("last two or
: three months") or perhaps created a new job?

I know several other people who experienced similar problem after migrating from version 2 and making some changes in the scheduled jobs. As far as I know, deleting and recreating "bad" jobs fixed the problem for them, so try recreating these two jobs and let us know if it doesn't help.

: The jobs were created in the previous 2.x version of 24x7.

: I changed a couple of settings within the jobs since the upgrade to the new
: version. For instance, I checked the "notify on error" option.
: Other than than, all is the same.

Creating a new job "based on" the old job did not work. The new job also ran at sporadic times.

Creating a new job and re-entering all information, then deleting the old jobs did work.

Thanks.

: I know several other people who experienced similar problem after migrating
: from version 2 and making some changes in the scheduled jobs. As far as I
: know, deleting and recreating "bad" jobs fixed the problem for
: them, so try recreating these two jobs and let us know if it doesn't help.

An update. After recreating the jobs with the New job option, they started on time for a couple of days. However, 48 hours later they were off schedule. One job was scheduled to run at 4:00 PM everyday. On 2/6 it ran at 4:05 PM. On 2/7 it ran at 10:37 PM. Another job is to run at 8:40 AM everyday. On 2/6 it ran at 8:45 AM. On 2/7 it ran at 11:50 AM. All jobs are set to run syncronously with a 5 minute timeout. (None have ever timed out.)

I enabled another job a few days ago that had been disabled for a long time. It is scheduled to run at 11:00 PM everyday. On 2/6 it ran at 11:19 PM and on 2/7 it ran at 10:12 AM.

I looked at some of the other jobs to s One is scheduled to run every 10 minutes everyday, all day. Scanning the job log, the incremental differences in minutes between each start look like this:

30, 28, 18, 19, 14, 20, 14, 18, 18, 14, 18, 13

Looking at the Job Execution Log, there were no other jobs executing between the increments above (which might have delayed there start.)

Could it be this entire 24x7 database is internally corrupted?

: I know several other people who experienced similar problem after migrating
: from version 2 and making some changes in the scheduled jobs. As far as I
: know, deleting and recreating "bad" jobs fixed the problem for
: them, so try recreating these two jobs and let us know if it doesn't help.

No it cannot be corrupted. You are running synchronous jobs. It looks like something keeps your jobs in a queue, perhaps some other job or jobs. Please consider sending your job database file and the complete log schedule.log to support@softtreetech.com we can investigate your situation. Also please include files from the "Performance Data" directory. It is better to zip them into one ZIP file before sending.

: An update. After recreating the jobs with the New job option, they started on
: time for a couple of days. However, 48 hours later they were off schedule.
: One job was scheduled to run at 4:00 PM everyday. On 2/6 it ran at 4:05
: PM. On 2/7 it ran at 10:37 PM. Another job is to run at 8:40 AM everyday.
: On 2/6 it ran at 8:45 AM. On 2/7 it ran at 11:50 AM. All jobs are set to
: run syncronously with a 5 minute timeout. (None have ever timed out.)

: I enabled another job a few days ago that had been disabled for a long time.
: It is scheduled to run at 11:00 PM everyday. On 2/6 it ran at 11:19 PM and
: on 2/7 it ran at 10:12 AM.

: I looked at some of the other jobs to s One is scheduled to run every 10
: minutes everyday, all day. Scanning the job log, the incremental
: differences in minutes between each start look like this: 30, 28, 18, 19,
: 14, 20, 14, 18, 18, 14, 18, 13

: Looking at the Job Execution Log, there were no other jobs executing between
: the increments above (which might have delayed there start.)

: Could it be this entire 24x7 database is internally corrupted?