BUG: Weekly Tasks May Fail to Run on the 1st Day of the Month

Last reviewed: April 10, 1997
Article ID: Q145908

The information in this article applies to:
  • Microsoft SQL Server, version 6.0

BUG# NT: 11212 (6.00)

SYMPTOMS

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.

WORKAROUND

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.

STATUS

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: 6.00 end scheduling tasks executive
Keywords : kbbug6.00 kbtool kbusage SSrvGen
Version : 6.00
Platform : WINDOWS
Issue type : kbbug
Resolution Type : No_Fix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 10, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.