https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/169164&feed=atom&action=history
Microsoft KB Archive/169164 - Revision history
2024-03-29T07:48:48Z
Revision history for this page on the wiki
MediaWiki 1.39.3
https://www.betaarchive.com/wiki/index.php?title=Microsoft_KB_Archive/169164&diff=88765&oldid=prev
3155ffGd: importing KB archive
2020-07-18T15:34:25Z
<p>importing KB archive</p>
<p><b>New page</b></p><div><div id="nsbanner"><br />
<br />
<div id="bannerrow1"><br />
<br />
{|<br />
| Knowledge Base<br />
|<br />
|}<br />
<br />
<br />
</div><br />
<div id="TitleRow"><br />
<br />
= <span id="KB169164"></span>BUG: Daily Tasks May Be Disabled If Activestartdate = 0 =<br />
<br />
<br />
</div><br />
<br />
</div><br />
<div id="nstext" valign="BOTTOM"><br />
<br />
Article ID: 169164<br />
<br />
Article Last Modified on 10/16/2003<br />
<br />
<br />
-----<br />
<br />
APPLIES TO<br /><br />
<br /><br />
<br />
* Microsoft SQL Server 6.0 Standard Edition<br />
* Microsoft SQL Server 6.5 Standard Edition<br />
<br />
<br />
-----<br />
<br />
<div class="notice_section"><br />
<br />
This article was previously published under Q169164<br />
<br />
</div><br />
<div class="notice_section"><br />
<br />
BUG #: 16930 (NT: 6.5)<br />
<br />
</div><br />
<div class="symptoms_section"><br />
<br />
== SYMPTOMS ==<br />
<br />
If you use sp_addtask to create a Transact-SQL daily task with activestartdate = 0, and the task is run successfully at least once, the task will be disabled upon SQL Executive startup if SQL Executive is stopped and not restarted for a sufficient amount of time. The time period varies from 1-5 days, depending on the frequency of the task. This behavior only occurs with Transact-SQL daily tasks, but will occur whether the daily frequency is once, every x minutes, or every x hours.<br />
<br />
</div><br />
<div class="workaround_section"><br />
<br />
== WORKAROUND ==<br />
<br />
To work around this problem, create the task through the SQL Enterprise Manager.<br /><br />
<br /><br />
Insert a valid non-zero value for activestartdate if you are using sp_addtask. The current date in the format YYYYMMDD is best.<br />
<br />
</div><br />
<div class="status_section"><br />
<br />
== STATUS ==<br />
<br />
Microsoft has confirmed this to be a problem in Microsoft SQL Server versions 6.0 and 6.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.<br />
<br />
</div><br />
<div class="moreinformation_section"><br />
<br />
== MORE INFORMATION ==<br />
<br />
The sp_addtask SQL Executive Stored Procedure section of the SQL Server Books Online states:<br /><br />
<br /><br />
activestartdate Specifies the date when this task will first be scheduled. Formatted as YYYYMMDD. The default is 0.<br /><br />
<br /><br />
However, when you create a task through SQL Enterprise Manager, the current date is inserted for activestartdate. Therefore, this problem only occurs if you use the sp_addtask stored procedure to create the task.<br />
<br />
</div><br />
Keywords: kbbug kbusage KB169164<br />
<br />
<div class="footer"><br />
<br />
<br /><br />
<br />
<br />
-----<br />
<br />
[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]<br />
<br />
<span>© Microsoft Corporation. All rights reserved.</span><br />
<br />
<br />
</div><br />
<br />
</div></div>
3155ffGd