topic Re: Python script as sheduled task (ArcGIS Pro) in Python Questions

Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Sun, 12 Dec 2021 00:18:27 GMT

Is anyone able to run a script through Windows Task scheduler using ArcGIS Pro? As a test I have an extremely simple script (just copying a feature) that runs fine within ArcGIS Pro.

import arcpy
arcpy.management.CopyFeatures("C:\CityScripts\ScheduledTasks\SafewatchCameras\Data\General.gdb\SafewatchCameras", "C:\CityScripts\ScheduledTasks\SafewatchCameras\Data\General.gdb\SafewatchCamerastemp2", None, None, None, None)‍‍‍‍

I setup the Task Scheduler as recommended by the ArcGIS Pro help and while the Task completes successfully nothing happens with the script.

Put in a call to ESRI tech support but they said it was a Windows issue and therefore couldn't work on it.

Scott

Re: Python script as sheduled task (ArcGIS Pro)

MichaelVolz — Fri, 14 Sep 2018 13:58:05 GMT

Is this script being run on a desktop machine or a Windows Server? What is the operating system?

Re: Python script as sheduled task (ArcGIS Pro)

JoshuaBixby — Fri, 14 Sep 2018 15:07:53 GMT

To put it kindly, that response from Esri Support is rubbish (I had some other word choices but wasn't sure if the upcoming profanity filter would block them!).

I notice you are using non-escaped file paths. It is best to use either escaped paths or raw strings to prevent Python from misinterpreting any backslashes in your strings. Does your script file run properly if you run it outside of a scheduled task?

Have you tried running a Python script with no ArcPy calls but calling it the same (using C:\...\propy)?

Re: Python script as sheduled task (ArcGIS Pro)

RichardFairhurst — Fri, 14 Sep 2018 15:15:32 GMT

You should be using propy.bat, not just propy. This works for me:

Program/script:

"c:\Program Files\ArcGIS\Pro\bin\Python\scripts\propy.bat"

Add arguments (optional):

"C:\Users\Owner\Documents\Test.py"

I also agree that you should be using a raw string for the path and file name arguments in Python.

Re: Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Fri, 14 Sep 2018 16:09:47 GMT

Richard,

It throws an error when I run it like this.

Re: Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Fri, 14 Sep 2018 16:11:04 GMT

Michael,

Windows Server 2012 Standard.

Re: Python script as sheduled task (ArcGIS Pro)

MichaelVolz — Fri, 14 Sep 2018 16:17:47 GMT

How about calling python.exe from it's installed location? For me it would be:

C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\python.exe would be the Program/script

and the py file would be the Add arguments.

Is the task configured to "Run with highest privileges"?

Re: Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Fri, 14 Sep 2018 16:25:06 GMT

Joshua,

Yeah I agree, I was pretty disappointed. If we were three hours into the call and getting nowhere that would be one thing. Or at least maybe point me somewhere in the right direction.

I notice you are using non-escaped file paths. It is best to use either escaped paths or raw strings to prevent Python from misinterpreting any backslashes in your strings. You lost me here. I know enough Python to be dangerous but not sure what this means.

Does your script file run properly if you run it outside of a scheduled task? Had trouble testing this. I've been using PyScripter on this machine to run our other scripts (which are all ArcGIS 10.3, 2.x versions) and I don't understand how to test using the Python install that comes with Pro.

Re: Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Fri, 14 Sep 2018 16:29:32 GMT

Same error.

This is how we (successfully) run all of our ArcMap based python scripts though.

Re: Python script as sheduled task (ArcGIS Pro)

MichaelVolz — Fri, 14 Sep 2018 16:38:51 GMT

Here is another threads related to this issue:

Python 3.x Scheduled Task Fails

It provides insight on the problem, but I'm not sure it has been resolved.

Re: Python script as sheduled task (ArcGIS Pro)

RichardFairhurst — Sun, 12 Dec 2021 00:18:29 GMT

It means you have to rewrite your script to be:

import arcpy
arcpy.management.CopyFeatures(r"C:\CityScripts\ScheduledTasks\SafewatchCameras\Data\General.gdb\SafewatchCameras", r"C:\CityScripts\ScheduledTasks\SafewatchCameras\Data\General.gdb\SafewatchCamerastemp2", None, None, None, None)‍‍

Notice I added an r in front of both your file paths. That makes it a raw string so that Python does not interpret the slashes as escape characters.

The set up I recommended was taken from the Esri website that explains how to Run Standalone Scripts. It works for running scripts on my local machine.

Re: Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Fri, 14 Sep 2018 16:55:18 GMT

Oh, that's what those are

Re: Python script as sheduled task (ArcGIS Pro)

JoshuaBixby — Fri, 14 Sep 2018 17:20:59 GMT

Not to ask the obvious, but you do have Pro configured for either offline use or to automatically sign in? And, has the profile/user/service that is running the scheduled task ever logged into Pro before?

Re: Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Fri, 14 Sep 2018 20:30:26 GMT

Yeah this is definitely related. When I select "Run only when user is logged on" it'll run. I wonder if it's OS as your first question alluded to? It seemed in that thread that people who were running Windows 2016 didn't have an issue.

Also, separately, what a rabbit hole. How is this not something that Tech Support doesn't want to jump into and solve and/or direct people to the appropriate resources?

Re: Python script as sheduled task (ArcGIS Pro)

MichaelVolz — Fri, 14 Sep 2018 21:32:45 GMT

Do you have Windows Server 2012 or Windows Server 2012 R2?

Re: Python script as sheduled task (ArcGIS Pro)

ThomasColson — Sat, 15 Sep 2018 20:54:00 GMT

The big question is, does the script run when using the account that will run it in task scheduler (right click run as)? Ever since I moved all my task scheduler stuff to Pro, nothing but a nightmare of scripts randomly failing, etc. I currently have one bug open related to pro py running as a scheduled task. Same scripts have worked fine in Arcmap for years. So it's not a windows issue. Also, has your IT person set this task up for you? There are a lot of permissions flaming hoops you have to jump through to get a scheduled task to run, and most users login does not allow it to run if you're logged off.

Re: Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Mon, 17 Sep 2018 18:31:40 GMT

It does appear to be an operating system issue as I ran it on another serving that's running Windows 2016 and it was successful. Seemingly everything else was the same (admin rights, etc.) I sent a message to our IT dept for some clarity as I'm not sure if there might be something specific to us or if it's specific to Windows 2012.

Re: Python script as sheduled task (ArcGIS Pro)

MichaelVolz — Mon, 17 Sep 2018 18:54:28 GMT

It's great that you were able to determine that it's the Windows Server OS that is the issue. It would appear then that organizations planning to upgrade their Windows Server environments to using Pro based python 3.x scripts will need to upgrade their servers to Windows Server 2016. I don't think ESRI has this in their documentation as a dependency.

Re: Python script as sheduled task (ArcGIS Pro)

AllanBenvin_yyc — Mon, 17 Sep 2018 20:46:14 GMT

Make sure that the account the job is running under has a named user account with AGOL or if it is a service account then configure your batch server as a Concurrent Use license. This will eliminate the licensing issues on the batch server.

Re: Python script as sheduled task (ArcGIS Pro)

City_of_Greenville__SCGIS — Tue, 18 Sep 2018 18:36:52 GMT

Yep, user is named user and has admin rights. Still doesn't work on 2012.