The operator or administrator abandoned the request task scheduler

Question

I planned a C # console application in the Windows 2012 R2 Task Scheduler. The application will start when it is executed manually or right-click on the scheduled task and click Run , but when the task scheduler starts with an error below, it does not work.

The operator or administrator declined the request (0x800710E0)

I followed the steps also after google search

• Selected " Run whether the user has been registered or not
• Unchecked " Run the task only if the computer is turned on as a power source

Answer 1

The error occurred due to folder permission, I created CSV from my application, which required folder permission. After giving full control , the folder error was resolved.

Answer 2

In my case, I had to redo the permissions for the task. Somehow, he lost the domain part of the username. Instead of 'DOMAIN \ joeuser', it was just 'joeuser'. After the reset, everything worked correctly, as in the past year.

Answer 3

In my case, the error message "The operator or administrator rejected the request" meant that the previous instance of the task was still working and because the option "Do not start a new instance" (the default state) was selected in the section "If the task is already running, then on the tab The following rule applies to the task “settings”: the task scheduler refused to start a new instance.

But this error message is rather confusing. From the other answers you can see that this can mean a lot of completely different mistakes. As usual in Microsoft products.

It is useful to check the History tab of the task. That's where I found out what was going on. The event "Startup request is ignored, instance is already running."

Answer 4

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

It turns out that the previous process never ended (it hung in memory due to a defect in my code). By default, Windows Task Scheduler does not start the process again if it is already running.

In addition to fixing the defect in the task scheduler, on the Settings tab, I set "If the task is already running", the following rule applies: start a new instance in parallel

1

Answer 5

In my case, my task runs the PowerShell script and displays the error message "The operator or administrator rejected the request (0x800710E0)", as shown in the task scheduler input grid. My username was correct, but when I went to the command line and simulated a task, running PowerShell for my .ps1 file, I saw the Avast prompt, which marked my script as suspicious and did not allow it to run. I created an Avast exception and now the task runs without problems.

Answer 6

In my case, according to setting up a task using the task scheduler, as described in "Preventing the Task Scheduler from completing tasks when setting up updates," I had the task set to run every "X" minutes for an indefinite period of time.

Seeing the terrible "Operator or administrator rejected the request" for the result of the last run, I looked at the History tab and see the details that it "missed its schedule."

Decision

On the " Settings " tab in the task properties, I just checked the " Run the task as soon as possible after skipping the scheduled launch " box, and the problem was solved; although I also had to enter my credentials again.

Note. This started after the server was moved from the backup backup server after the hardware recovery was completed back to the original equipment. The operating system was Server 2012 R2, and the operating system was transferred to other equipment, while the repairs were carried out on the production server, but I did not notice it there - maybe there was an oversight - I'm not sure.

Answer 7

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