Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

The operator or administrator has refused the request task scheduler

I have scheduled a C# console application in Task Scheduler of Windows 2012 R2. Application will run when executed it manually or Right click on scheduled task and click on Run, but it is failed when triggered by Task Scheduler with below error.

The operator or administrator has refused the request(0x800710E0)

I have followed below steps also after Google search

  1. Selected "Run whether user logged in or not"
  2. Unchecked "Start the task only if the computer is on AC power"
like image 956
Sushmit Patil Avatar asked Mar 29 '16 10:03

Sushmit Patil


People also ask

How do you fix the operator or administrator has refused the request?

Right-click on the application and select Properties. Select the Security tab and click Edit. Under the Permissions, select the user account and check the allowed permissions that apply. If the user isn't available, click on the Add button and add the user.

What is 0x800710E0?

The operator or administrator has refused the request (0x800710E0) Print. Modified on: Mon, 22 Nov, 2021 at 6:58 PM. This error can be given when the scheduled task was not run because it was already running.

How do I enable history in Task Scheduler?

Open Task Scheduler. In the left pane, right click Task Scheduler (Local), then click Enable All Task History.


2 Answers

In my case, the error message "The operator or administrator has refused the request" meant that a previous instance of the task has still been running and the task was configured to not start a new instance if it's already running (the default configuration), so the Task Scheduler refused to start a new instance when the task was triggered.

You can find that option in a select box on the task's Settings tab, under the caption "If the task is already running, then the following rule applies". The default value is "Do not start a new instance".

Task settings dialog

But that error message is pretty confusing. From the other answers, you may see that it may mean many completely distinct errors. As is usual in Microsoft's products.

Tip

It's helpful to check the History tab of a task. That's where I have found out what's actually going on. There was an event "Launch request ignored, instance already running".

like image 53
David Ferenczy Rogožan Avatar answered Oct 03 '22 15:10

David Ferenczy Rogožan


In my case, I had to redo the permissions on the task. Somehow it had lost the domain portion of the username. Instead of `DOMAIN\joeuser' it was just 'joeuser'. After a reset, it worked correctly as it had for the previous year.

enter image description here

like image 27
wruckie Avatar answered Oct 03 '22 15:10

wruckie