topic Re: Python 3.x Scheduled Task Fails in ArcGIS Pro Questions

Python 3.x Scheduled Task Fails

mpboyle — Thu, 29 Jun 2017 16:33:32 GMT

I am in the process of migrating a scheduled task from ArcMap to ArcGIS Pro that exports maps to PDFs on a daily basis. I have the python script written, and it executes as expected when running through an IDE (PyCharm) using the python executable delivered with ArcGIS Pro (..\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\python.exe).

When I try executing the same script through Windows Task Scheduler, I can tell the script is running because a .txt file is generated to log processes, however, at some point the script is failing as the maps are not being exported. The task scheduler returns a code of 0xFFFFFFFF and I haven't found anything of substance for this code. There are no warnings or errors in the task history either to give any clues.

We have several other tasks that are running just fine using python 2.7 along with ArcMap/ArcGIS Desktop using my domain account, so the username I'm using has sufficient permissions to execute a task.

I also have ArcGIS Pro setup to login automatically, which again, works fine through the IDE. I tried using a Single Use license, with the same result.

If I comment out all the ArcGIS Pro / arcpy functions, the script will execute as expected through Task Scheduler (creates a log, and sends an email). It seems to be specific to the arcpy functions.

Is anyone running a Windows Task Scheduler task using ArcGIS Pro projects successfully? If so, am I missing something? Is there some sort of permission setting I'm missing? Any ideas of where to look...?

Re: Python 3.x Scheduled Task Fails

MichaelVolz — Thu, 29 Jun 2017 17:04:18 GMT

I don't believe this will work in versions previous to Pro 2.0.

Take a look at this thread:

https://community.esri.com/thread/197214-python-351-script-wont-run-via-windows-task-scheduler-when-user-logged-off

Re: Python 3.x Scheduled Task Fails

mpboyle — Thu, 29 Jun 2017 17:35:06 GMT

I am using ArcGIS Pro 2.0 (Single Use Advanced)...and after reading through the thread, my script will work ONLY when the task is set to 'Run only when user is logged on'. If I try to execute the script using 'Run whether user is logged on or not' it will fail.

Thanks for pointing me in the direction of the other thread.

Re: Python 3.x Scheduled Task Fails

MichaelVolz — Thu, 29 Jun 2017 17:38:32 GMT

Do you have the ability to spin up a Windows Server 2016 server to see if the scheduled task would work there if not logged onto the server?

Re: Python 3.x Scheduled Task Fails

Zach_Robinson — Thu, 03 Jan 2019 17:58:52 GMT

I can also only run py3 scripts in Windows Task Scheduler when the task is set to Run only when user is logged on. It sounds like from this thread and others that upgrading to Windows Server 2016 is the only sure way to resolve the issue. Hopefully ESRI releases guidance soon.

Re: Python 3.x Scheduled Task Fails

MichaelVolz — Thu, 03 Jan 2019 18:18:35 GMT

What kind of machine are you using when running this script (workstation, server, other)?

Re: Python 3.x Scheduled Task Fails

Zach_Robinson — Thu, 03 Jan 2019 18:20:50 GMT

Running Windows Server 2012 R2

Re: Python 3.x Scheduled Task Fails

MichaelVolz — Thu, 03 Jan 2019 18:23:18 GMT

Is this a machine you are currently running ArcMap's python 2.7 based scripts from in Windows Task Scheduler?

Does your organization support Windows Server 2016 at this time?

Re: Python 3.x Scheduled Task Fails

Zach_Robinson — Thu, 03 Jan 2019 18:29:43 GMT

Yes, I run a handful of py2.7 scripts in task scheduler from the server machine. They run fine with the option Run whether user is logged on or not set to True. I also have left Run with highest privileges unchecked when running 2.7 scripts and they run without issue.

And no, our city does not yet support Windows Server 2016.

Re: Python 3.x Scheduled Task Fails

DarylHochhalter — Fri, 07 Aug 2020 13:50:35 GMT

I have the same issue running Python 3 task on Windows server 2019. I have actually attempted to use only when user is logged on, but that really isn't an option anyway. Running the same scripts as a task using Python 2.7 works fine. I can run the scripts in python 3 manually on the same machine, but not as a task. Wondering if it could have to do with the Conda environment and the fact that the system PATH info might be pointing to arcpy for the 2.7 environment?

Re: Python 3.x Scheduled Task Fails

Arne_Gelfert — Tue, 11 Aug 2020 13:38:42 GMT

Assuming the original question was address a while back. So Daryl Hochhalter‌ ...

I've run into various issues with this but ultimately got it working and now have scheduled tasked for arcpy jobs running on Win Server. Typically I have found:

Use a service account to run the job.
Make sure service account has logon as service privileges.
Make sure the service account get can a Pro license (named or concurrent, depending on your version of Pro)
Start up ArcGIS Pro at least once using the service account to set up that account's environment.
Make sure you can import arcpy when running the script manually.
Make sure you're Python path is correct or you put in the whole path to the conda Python install in any batch files that gets executed in task scheduler.
Don't forget about this process when you upgrade/change license servers or make Portal changes.

Re: Python 3.x Scheduled Task Fails

SolanaFoo2 — Wed, 19 May 2021 07:54:22 GMT

How do you "make sure the service account can get a Pro license"? How do you configure that? We have named user licenses tied to our AGOL organization.