BUG: Weekly Tasks May Fail to Run on the 1st Day of the MonthID: Q145908
|
If you create a weekly task to run on each day of the week, the NextRunDate
in the systasks table is incorrectly set to the end of the month. Instead
of setting the next run date to the first day of the following month, the
date is set to the last day in the month plus one day.
This is also true if the first of the month falls within a range of days
that is scheduled on a weekly basis. For instance, if the first of the
month falls on Wednesday, and a weekly task is scheduled to run Monday,
Tuesday, Wednesday, and Thursday, the NextRunDate will be set to the last
day in the month plus one.
When a task is to be run for each day in the week, set the frequency to
daily, not weekly.
If the task is to be run for only part of the week, modify the task from
weekly to on-demand or one-time. Then modify the task back to weekly,
adding days, frequency, and duration information back to the task. This
will need to be done on the first of each month for those tasks where the
first of the month falls on a day that is specified in the range of days in
the weekly task.
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.0. We are researching this problem and will post new information
here in the Microsoft Knowledge Base as it becomes available.
Additional query words: end scheduling tasks executive
Keywords : kbtool kbusage SSrvGen kbbug6.00
Version : 6.00
Platform : WINDOWS
Issue type : kbbug
Last Reviewed: March 24, 1999