• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Question Scheduled Task Error

Erick_Gomes

New Pleskian
Hello guys,

all scheduled tasks created, are returning error


Code:
AuthorizationManager check failed.

+ CategoryInfo : SecurityError: (:) [], ParentContainsErrorRecordException

+ FullyQualifiedErrorId : UnauthorizedAcces

Anyone have any suggestions?
 
Last edited:
What is your OS and Plesk version there? I suppose it is unsupported by Plesk Windows Server 2019, right?
 
The problem is related to unsupported Windows Server 2019 Software Requirements for Plesk

Hy Igor,

thanks for answering.

I spent the day breaking my head to figure out how to make it work.

and fortunately I managed to make it "work".

Below is the command line created automatically by the Plesk Task Scheduler:

/c ""C:\Program Files (x86)\Plesk\admin\bin\runtask.exe" "--user=userdomain" "--application=powershell" "--parameters=-ExecutionPolicy ByPass -File \"C:\Program Files ^(x86^)\Plesk\Additional/Scheduler/fetch_url.ps1\" https://www.domain.com/test.asp""

Here's the changed line that's working "perfectly"

/c ""C:\Program Files (x86)\Plesk\admin\bin\runtask.exe" "--user=system" "--application=powershell" "--parameters=-ExecutionPolicy ByPass -File \"C:\Program Files ^(x86^)\Plesk\Additional/Scheduler/fetch_url.ps1\" https://www.domain.com/test.asp""

See that I have changed only the user

It seems to be a permission problem

Does it have any automatic way to change the user of this command line? Or only by hand?
 
Back
Top