Task Scheduler error 0x800710E0
Recently while setting up some scheduled tasks on my Windows 2012 R2 machine, I ran across a strange error that I had not seen before. I solved the problem with one little checkbox.
So I was happily setting up some scheduled tasks to make metrics queries at regular intervals, and everything seemed to be working fine. After configuring the task, and doing a test run, everything worked fine. The exit code in Task Scheduler came back as "The operation completed successfully", and the metrics appeared in the database. Everything seemed fine.
After getting the jobs set up, I locked the machine, and stepped away for lunch, which would give the jobs time to "cook", gathering more metrics so I could verify the graphs were being built correctly.
Lo, upon return from lunch, I was greeted with the following error in Task Scheduler:
The operator or administrator has refused the request (0x800710E0).
After searching around, I discovered the problem doesn't have any consistent contributing factors, although it does seeme to happen with Hyper-V virtual machines more often then others.
Resolving the issue was pretty easy, though.
- Open Task Scheduler
- Double click the task that is experiencing the error
- Go to the Conditions tab
- If there is not already a check in the Start the task only if the computer is on AC Power box
- Clear the box labelled Stop if the computer switches to battery power
- Clear the Start the task only if the computer is on AC Power box
- Click Ok. Enter credentials if prompted
Give it a test run by right-clicking the task and clicking Run. To give it a better test, log off the machine, and let the task run at its regularly scheduled time. So if it scheduled to start next at 15:30:00, wait until 15:35:00 to log back in and check the "Last Run Result" field for the job, in Task Scheduler. It should now be coming back as The operation completed successfully. (0x0).
Hope this helps someone!
About this post
Viewed: 5,848 times
No comments have been added for this post.
You must be logged in to make a comment.