topic Re: How to automate the workforce scripts with Windows Scheduler in ArcGIS Workforce Questions

How to automate the workforce scripts with Windows Scheduler

LaneHartman — Tue, 20 Nov 2018 20:50:59 GMT

I'm looking for some guidance on modifying the assignment workforce scripts so I can use them with the windows scheduler and have them run in the background. The scripts work great when I run them from the Python Command Prompt, but I'm not sure how to switch to Windows Scheduler automation. Just running the script as is in WinSch doesn't seem to work. Craig Gillgrass‌ Aaron Pulver‌

Thanks

Re: How to automate the workforce scripts with Windows Scheduler

GeorgeKatsambas — Tue, 20 Nov 2018 20:55:15 GMT

I am having the same problem since switching to window 10, task scheduler wont schedule a python script either, some sort of security I believe. hope someone can answer also.

Re: How to automate the workforce scripts with Windows Scheduler

Anonymous User — Mon, 26 Nov 2018 16:08:44 GMT

What types of errors or logs are generated. You need to make sure that the script is using the correct python interpreter.

This is what my test task looks like (Windows Server 2016):

Make sure you are running with a user that has the correct permissions (depends what you want to do).

Make sure you set the full path to the python environment that has the ArcGIS API for Python installed in my case this is "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\python.exe"

Make sure you add an argument with the full path to the script you want to run. In my case this is "C:\Users\<my-username>\some_script.py". Add any other arguments your script by expect.

I would test that the task can be run manually from within the Task Scheduler. Then if that's working, add a trigger to schedule it.

Hope that helps,

Aaron

Re: How to automate the workforce scripts with Windows Scheduler

LaneHartman — Mon, 26 Nov 2018 17:24:24 GMT

Aaron,

Thanks, I think this will work. The python environment paths were where I was hung up on. I'll let you know what I find.

Re: How to automate the workforce scripts with Windows Scheduler

LaneHartman — Mon, 03 Dec 2018 16:15:57 GMT

Aaron,

The create assignments by csv script works great using this method, but I can't get the assignment monitor script to work using the the same method. Does this have something to do with the loop that script has in it?

Re: How to automate the workforce scripts with Windows Scheduler

MichaelVolz — Mon, 03 Dec 2018 16:16:59 GMT

George:

Have you resolved your problem on your Windows 10 desktop machine with running the python based Windows Scheduled Task?

Re: How to automate the workforce scripts with Windows Scheduler

Anonymous User — Mon, 03 Dec 2018 16:18:56 GMT

Yeah that script was mostly for a demo. You have to modify it to remove the loop (since you will schedule it to run every 1 minute or whatever).

Re: How to automate the workforce scripts with Windows Scheduler

GeorgeKatsambas — Mon, 03 Dec 2018 16:50:07 GMT

No, when I add the python script windows 10 requires a password, when its scheduled to run and no password entered it wont run.

Re: How to automate the workforce scripts with Windows Scheduler

GeorgeKatsambas — Mon, 03 Dec 2018 17:06:29 GMT

This keeps on popping up, only with python in task scheduler?

Re: How to automate the workforce scripts with Windows Scheduler

MichaelVolz — Mon, 03 Dec 2018 17:10:04 GMT

Do you have both ArcMap and Pro installed on the Windows 10 machine? If so, did you call the correct python environment to run?

Did the python Windows Sch. Task ever run on this computer?

Re: How to automate the workforce scripts with Windows Scheduler

LaneHartman — Mon, 03 Dec 2018 18:34:34 GMT

Haven't had your specific issue. This was more script related. I've been able to run them on this machine with the "Run whether user is logged on or not" option on and "Run with highest privilege" checked. Also had to make sure I was using the correct path to the ArcGIS Pro python environment in the Action dialogue box.

Re: How to automate the workforce scripts with Windows Scheduler

LaneHartman — Mon, 03 Dec 2018 20:14:16 GMT

Ok, this modification of the assignment_monitor.py script runs fine from the command prompt without looping, but I still can't get it to work from Windows Scheduler. What am I missing here?

Re: How to automate the workforce scripts with Windows Scheduler

Anonymous User — Mon, 03 Dec 2018 22:04:52 GMT

My hunch is that you need to define the full path to the config file on line 149:

config.read("config.ini")

Windows Task Scheduler may be running the script from another directory so it might not find that file.

Re: How to automate the workforce scripts with Windows Scheduler

LaneHartman — Tue, 04 Dec 2018 14:25:52 GMT

Defining the full path to the config.ini file didn't seem to do anything. I did notice that it's not writing anything to the log file either when I attempt to run the script from Windows Scheduler. I've attached screenshots of the Windows Scheduler tabs in case there is an issue there. It is set up like the create_assignments_from_csv.py script (which works well from Windows Scheduler) without the additional arguments that that script requires. Are there some additional arguments besides the script file and path to it?

Re: How to automate the workforce scripts with Windows Scheduler

daveostrander — Thu, 21 Feb 2019 21:23:36 GMT

Hi Aaron,

How would the arguments look in the Task Scheduler? I am used to running batch files that call python and list the arguments directly in the batch, but just opening cmd and running the example code isn't working for me. The scripts only appear to work when running in the Anaconda Prompt. Since the script works just fine when running it manually, I guess I need to open the Anaconda Prompt within Task Scheduler, but then just need direction on how to add the following arguments.

-u username -p password -org "https://<org>.maps.arcgis.com" -project-id "038a1926d2d741dc8acabefd5b2cc5d3" -log-file "../log.txt" -where "1=1"

I am including the full path to the script as the first parameter as you advised, but not sure how the quotes affect task scheduler. So far I am loading them into the argument text box exactly as the example shows in the line above/on your Git site.

Any help would be appreciated.

Re: How to automate the workforce scripts with Windows Scheduler

GeorgeKatsambas — Thu, 21 Feb 2019 22:21:25 GMT

I had python scripts that ran perfectly in task scheduler, once we went to windows 10 task scheduler will no longer run the scripts as scheduled as its a security feature in W10 that would always require a login credential of an administrator. Are you using windows 10 and an administrator to your machine?

Re: How to automate the workforce scripts with Windows Scheduler

daveostrander — Thu, 21 Feb 2019 23:09:22 GMT

That's a good question. I am running Windows Server 2016, and have noticed that privileges seem to matter a lot more on this new OS. So, when I run the script manually using Anaconda Prompt or Python Command Prompt I always need to right click and "run as administrator" in order for the script to succeed; if not it seems to fail when attempting to write to the log file on C:. My task is set to run with highest privileges, but not sure if that equates to run as administrator or not. That said, I am an administrator on this server. Just verified that by pulling up my account settings on the machine and can see the Administrator title below my username.

Re: How to automate the workforce scripts with Windows Scheduler

Anonymous User — Fri, 22 Feb 2019 02:19:04 GMT

You should be able to just add the following to the "Add arguments" text box:

C:\Users\username\some_script.py -u aaron -p password ...

Re: How to automate the workforce scripts with Windows Scheduler

daveostrander — Fri, 22 Feb 2019 15:39:59 GMT

That is what has been so frustrating, is that it should be just that simple. So, I have now fixed the issue, but still have questions. I had installed pro, and then later installed python using the Anaconda Distribution. I was under the impression that I could use either python installation interchangeably, right? When I setup my task I pointed my "Program/Script" text box to C:\ProgramData\Anaconda3\python.exe, which did not work. I am not sure if it is a factor, but the default location that Anaconda 3.7 installs, also happens to be within a hidden folder (ProgramData). It wasn't until I changed the "Program/Script" section of Task Scheduler to "C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\python.exe" that it worked. All arguments were passed in without quotes, and everything is now working as expected. So why can't I execute from python.exe in the Anaconda3 folder?

Also, I am still having trouble running the workforce scripts straight from a standard Command Prompt. Each time I try to run the script from there I get an Import Error for module import_ssl (see below). Again, I haven't modified the underlying script (delete_assignments.py). Instead, I am just passing the parameters through. Any ideas on why this doesn't work? Is there something obvious that I am missing?

Anyway, thanks for all your help on this Aaron!

Re: How to automate the workforce scripts with Windows Scheduler

daveostrander — Fri, 22 Feb 2019 18:06:22 GMT

It appears that the issues I was having were related to my system environment variables. With all of the installs of python floating around it was a bit confusing setting this up. On my server machine I have Python 2.7 installed with ArcGIS Desktop, Python 3.6.6 installed with ArcGIS Pro, and Python 3.7.1 installed with Anaconda. I also have a ArcGIS Pro clone that installs python in yet another location.

So, I have reset my system environment path variable to C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3, C:\Program Files\ArcGIS\Pro\bin\Python\Scripts, and C:\Python27. At this point everything appears to run correctly no matter which command line I use. Are these the recommended path variable settings? Previously I had the paths set to C:\ProgramData\Anaconda3, C:\ProgramData\Anaconda3\Scripts, and C:\Python27.