A Task That Is Scheduled
with the AT Command May Stop After 72 Hours
Microsoft Knowledge Base Article: 304288 - 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. Access Denied When
Attempting to Start the Task Scheduler
Microsoft Knowledge Base Article: 259907 - When
you attempt to start the Task Scheduler using
the Services program under Administrative Tools,
you may receive an "Access denied" error message.
Access Denied Connecting
to Novell Server Under AT Scheduler
Microsoft Knowledge Base Article: 149408 - When
the AT Scheduler is used to run a job under the
System account that connects to a Novell server,
the following error message appears:
Applications Started
with AT Are Not Interactive
Microsoft Knowledge Base Article: 121562 - The
Windows NT AT command does not load applications
interactively even though the System Account Allow
Service to Interact with Desktop check box is
selected for the Scheduler service. The AT command
does load the application in the background, but
you are not able to see or interact with the application
in any way.
AT Tasks Cannot Be
Viewed Using the Task Scheduler Tool
Microsoft Knowledge Base Article: 220149 - When
you schedule a task using the AT tool at a command
prompt, the task appears as being scheduled in
the Task Scheduler tool. When you schedule a task
using the Task Scheduler tool, the task does not
appear when you run the the AT tool at a command
prompt.
Mstask.exe Does Not
Run Scheduled Jobs
Microsoft Knowledge Base Article: 272022 - Intermittently,
the Mstask.exe process may stop running scheduled
jobs. To cause Mstask.exe to run the jobs again,
you must stop and restart the Task Scheduler service.
Additionally, a job status may be displayed as
"Running" even though the job is not run again.
"Service Is Not Responding
to the Control Function" Starting the Scheduler
Service
Microsoft Knowledge Base Article: 227404 - If
the Task Scheduler service is stopped and you
later attempt to start it, you may receive the
following error message:
Task Scheduler Service
Must Be Started with System Account
Microsoft Knowledge Base Article: 223170 - When
you attempt to start Task Scheduler, you may receive
the one of the following error messages:
Task Scheduler and
AT Command Display Inaccurate Information for
Pending Jobs
Microsoft Knowledge Base Article: 268902 - After
you schedule a job by using the at command,
the list of pending jobs displays inaccurate information
Task Scheduler Service
Starts Automatically After Upgrade
Microsoft Knowledge Base Article: 234632 - After
you upgrade your Microsoft Windows NT 4.0-based
computer to Windows 2000, the Task Scheduler service
starts automatically, and this occurs even if
you previously disabled this feature.
Troubleshooting AT
Command Using /k Switch
Microsoft Knowledge Base Article: 142040 - One
way to troubleshoot a batch job that is scheduled
to run using the AT command is to type the following
at the MS-DOS command prompt:
Using the SCOPY Command
with AT or WinAT scheduler
Microsoft Knowledge Base Article: 140972 - The
SCOPY command from Windows NT Resource Kit is
used to copy files and folders to and from Windows
NT File System (NTFS) partitions with the security
of the folders and files intact. The format for
the command is: scopy <Source> <Destination>
[/o] [/a] [/s]
Windows 2000 Does
Not Have Any Default Tasks in the Scheduled Tasks
Folder
Microsoft Knowledge Base Article: 226262 -
After you install Windows 2000 Professional or
Windows 2000 Server, you do not have any default
tasks in the Scheduled Tasks folder.
|