FIX: SQLAgent Job with Recurring Schedule is Disabled Upon Completion of the Schedule for the Day

Article translations Article translations
Article ID: 295378 - View products that this article applies to.
This article was previously published under Q295378
BUG #: 230243 (SHILOH_BUGS)
Expand all | Collapse all

On This Page

SYMPTOMS

If you set up a SQLAgent job to have a recurring weekly schedule, the job executes successfully the first day, but may later become disabled and the job may not run the next day and thereafter.

The following error messages appear in the SqlAgent.out file:
2001-05-18 19:31:18 - + [191] Warning [1]: Possible date calculation spin for Schedule 28
2001-05-18 19:31:21 - + [191] Warning [2]: Possible date calculation spin for Schedule 28
2001-05-18 19:31:25 - + [191] Warning [3]: Possible date calculation spin for Schedule 28
2001-05-18 19:31:29 - + [191] Warning [4]: Possible date calculation spin for Schedule 28
2001-05-18 19:31:33 - + [191] Warning [5]: Possible date calculation spin for Schedule 28
2001-05-18 19:31:33 - ! [192] Date calculation spin detected for Schedule 28
2001-05-18 19:31:33 - + [162] Internal request (from SetJobNextRunDate [reason: schedule will not run again]) to deactivate schedule 28

CAUSE

SQLAgent tries to calculate the day when the job needs to run next and fails on the current date.

RESOLUTION

SQL Server 2000

To resolve this problem, obtain the latest service pack for SQL Server 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
290211 INF: How to Obtain the Latest SQL Server 2000 Service Pack

SQL Server 7.0

To resolve this problem, obtain the latest service pack for Microsoft SQL Server 7.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301511 INF: How to Obtain the Latest SQL Server 7.0 Service Pack

WORKAROUND

Create a separate schedule for every day and have multiple schedules per job.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

SQL Server 2000
This problem was first corrected in SQL Server 2000 Service Pack 1.

SQL Server 7.0
This problem was first corrected in Microsoft SQL Server 7.0 Service Pack 4.

Properties

Article ID: 295378 - Last Review: October 30, 2003 - Revision: 3.2
APPLIES TO
  • Microsoft SQL Server 2000 Standard Edition
  • Microsoft SQL Server 7.0 Standard Edition
Keywords: 
kbbug kbfix kbsqlserv2000sp1fix KB295378

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com