A Task That Is Scheduled with the AT Command May Stop After 72 Hours (304288)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Server SP2
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Advanced Server SP2
- Microsoft Windows 2000 Professional SP1
- Microsoft Windows 2000 Professional SP2
- Microsoft Windows XP Professional
- Microsoft Windows XP Home Edition
This article was previously published under Q304288 IMPORTANT: This article contains information about modifying the registry. Before you
modify the registry, make sure to back it up and make sure that you understand how to restore
the registry if a problem occurs. For information about how to back up, restore, and edit the
registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
Jobs that you schedule by using the at command are converted to Task Scheduler tasks. By default, these tasks are set to stop after 72 hours.
CAUSE
Jobs that you schedule with the at command do not have a maximum run time. The behavior of stopping after 72 hours was introduced with Windows 2000. A new registry value has been introduced to override this default value.
RESOLUTIONWindows 2000To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
----------------------------------------------------
03-Oct-2001 14:41 4.71.2195.1 219,408 Mstask.dll
03-Oct-2001 14:40 4.71.2195.1 118,544 Mstask.exe
Using the New Registry ValueWARNING: If you use Registry Editor incorrectly, you may cause serious problems that may
require you to reinstall your operating system. Microsoft cannot guarantee that you can solve
problems that result from using Registry Editor incorrectly. Use Registry Editor at your own
risk. - Start Registry Editor (Regedt32.exe).
- Locate and click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Schedule - On the Edit menu, click Add Value, and then add the following registry value:
Value name: AtTaskMaxHours
Data type: REG_DWORD
Radix: Decimal
Value data: 72 (the default value)
A value of 0 indicates no limit (that is, the task is not stopped).
A value between 1 and 999 indicates the number of hours the task is allowed to run after it starts.
- Quit Registry Editor.
Windows XPTo resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
322389 How to Obtain the Latest Windows XP Service Pack
WORKAROUND
You can edit the maximum run time for a task by using the Task Scheduler tool after you submit the task. The registry value that is listed earlier in this article controls the default run time for tasks that you submit by using the at command.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 3 (SP3) and Microsoft Windows XP Service Pack 1 (SP1).
Modification Type: | Minor | Last Reviewed: | 9/26/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbbug kbfix kbSysAdmin kbWin2000PreSP3Fix kbWin2000sp3fix kbWinXPsp1fix KB304288 |
---|
|