The operator or administrator has refused the requ

问题:

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"

回答1:

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.

回答2:

In my case, the error message "The operator or administrator has refused the request" meant that a previous instance of the task has been still running and because there was an option "Do not start a new instance" selected (default state) under "If the task is already running, then the following rule applies" on the Settings tab of the task, Task Scheduler refused to start a new instance.

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.

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

回答3:

Error occurred due to folder permission, I was creating CSV from my application, which was required folder permission to be granted. After giving Full Control to the folder error got resolved.

回答4:

In my case as per having a job setup with Task Scheduler as written about in the "Prevent a Task Scheduler Task from Executing on Setting Updates", I had a job setup to run every "X" minutes for a period of indefinitely.

Upon seeing the dreaded "The operator or administrator has refused the request" for the Last Run Result, I looked over the History tab and see detail indicating that is "missed its schedule".

The Solution

From the Settings tab of the job properties, I simply checked the option "Run task as soon as possible after a scheduled start is missed", and problem resolved; although, I did have to type in the credential again as well.

Note: This started occurring once a server was moved from a redundant backup server once hardware repair was completed back to the original hardware. The OS was Server 2012 R2 and the OS was moved to other hardware while repair was done on the production server but I didn't notice this there—maybe an oversight there though—not sure.

回答5:

I know that @Sushmit-Patil found a solution, but I wanted to add a solution to my similar problem:

It turns out a prior process never exited (it was hanging around in memory because of a defect I had in my code). By default, Windows Task Scheduler won't run the process again if it's already running.

In addition to fixing the defect, in Task Scheduler, under the Settings tab, I set If the task is already running, then the following rule applies: to Run a new instance in parallel

1

回答6:

For me, the solution was to check Run with highest privileges in the properties.

回答7:

In my case my task launches a PowerShell script--and it produced the "The operator or administrator has refused the request (0x800710E0)" error message as seen in the Task Scheduler's task-entry grid. My user name was correct, but when I dropped to a command prompt and simulated the task by running the PowerShell against my .ps1 file, I saw an Avast prompt that flagged my script as suspicious and wasn't allowing it to run. I created an Avast exception and now the task runs without any issue.

回答8:

You can also do this from "settings". Probably earlier instance was already running and launching a new instance failed.