Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
11,117 questions
Task scheduler does not run as scheduled
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 7.000000000000001%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
まなぶ
0
Reputation points
The following symptoms are occurring.
I looked for the cause, but I couldn't find any similar content that could resolve the cause, so I would like to consult with you on how to resolve the issue.
【environment】
Windows Server2012R2→Windows Server2019
*Upgrades were performed using AWS SSM Automation.
[Events that are occurring]
① When a task registered in the task scheduler is executed according to schedule, the status becomes "Start request has been queued" and the process does not progress in one direction.
② When connecting remotely, the message "An internal error has occurred" is displayed and remote connection is not possible.
【Frequency of occurrence】
①Forever
②Sometimes
[Things I tried]
① If you run the registered task manually, it will run normally.
② Restarting the server will improve the problem.
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(115.19999999999999, 80%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESL%3C/text%3E%3C/svg%3E)
Sachith Lakmal 21 Reputation points2023-11-13T06:23:03.3366667+00:00 - Does your task is on Ready State?
- Have you checked whether the task has been enabled. This happened to me a couple of times
- Does you service account or user account have elevated permission to run the task?
- Go to the task history & check for errors
-
まなぶ 0 Reputation points
2023-11-13T08:17:36.31+00:00 Thank you for answering.
1.The scheduled time has come in the ready state and the state is "Start request has been queued". It's normal until it runs.
2.It was enabled.
3.It was allowed.
4.There are no errors. I'm having trouble because there are no errors.
Sign in to comment