In version 3.4.21 a job will show the correct last run date but
the job log shows a different date for the last activity.

I have seen similar behavior when activating the log to
nt event log option.

I run on windows 2000, servicepack 4,
24x7 3.4.21 with site license.
mdac 2.7 SP1
internet explorer 5.5
all windows updates have been applied
the server is part of a windows 2000 native domain.

How big is the difference?

: In version 3.4.21 a job will show the correct last run date but
: the job log shows a different date for the last activity.

: I have seen similar behavior when activating the log to
: nt event log option.

: I run on windows 2000, servicepack 4,
: 24x7 3.4.21 with site license.
: mdac 2.7 SP1
: internet explorer 5.5
: all windows updates have been applied
: the server is part of a windows 2000 native domain.

: How big is the difference?

Several jobs where run on 24-09-2004 according to
the last run status. but in the job log it did not
show anything after 22-09-2004.

3 questions:

1. Do they all run at the same time?
2. Do you have any jobs accessing or wrinting to the log filedirectly?
3. What is the last backup time of the schedule.log file and how does it correlate to the job run time?

: Several jobs where run on 24-09-2004 according to
: the last run status. but in the job log it did not
: show anything after 22-09-2004.

: 3 questions: 1. Do they all run at the same time?
: 2. Do you have any jobs accessing or wrinting to the log filedirectly?
: 3. What is the last backup time of the schedule.log file and how does it
: correlate to the job run time?

The jobs run at different times. There is a minimum of 15 minutes interval

there are no jobs accessing or writing to the log file directly
the schedule.log has a current date and time.

now that I do not use the nt event logging feature I can read the job logging just fine.

Please email to support@softtreetech instructions on how to reproduce this issue. If this is a bug we will fix it.

: The jobs run at different times. There is a minimum of 15 minutes interval

: there are no jobs accessing or writing to the log file directly
: the schedule.log has a current date and time.

: now that I do not use the nt event logging feature I can read the job logging
: just fine.