I'm running into issues when trying to schedule a Geoprocessing tool to run at a later time. I receive this error when trying to schedule the tool:
Tool runs with no issues when done manually.
Would appreciate any help or guidance.
Just upgraded to Pro 2.5.1
Solved! Go to Solution.
Hello everyone,
Thanks to Hugh B ' s help troubleshooting the problem, we have found and addressed the bug in Pro 2.6 Beta 2. The issue is with per-user installs of ArcGIS Pro 2.5, or configured installs that do not write registry settings to the LOCAL_MACHINE folder.
If anyone is experiencing this and would like to test the fix, and other capabilities, provided in the ArcGIS Pro 2.6 Beta program, please send me a notice: dflater@esri.com. If you need to stay using ArcGIS Pro 2.5, the only solution available now is to install using the per-machine option.
Drew
You are following these instructions? particularly the "Note" issues?
Schedule geoprocessing tools—ArcGIS Pro | Documentation
Yes, I have followed that guide and made sure to adhere to the Notes included
sorry, you will have to narrow down your case from the known bugs associated with that error message then from the Support page
Hello Hugh B,
We have tried to troubleshoot this problem with others as well. Can you try these steps and answer a few questions?
Drew,
Thank you for your reply.
Let me know if you need any additional information.
Thanks very much Hugh B, I think we're getting somewhere. I will try to reproduce your configuration.
In the mean-time, can you upload the contents of that "Get Count _ xxxx" folder? It should contain the task.py file and a task.xml file. The task.py contains the actual executable used to run scheduled tools outside the application, and the task.xml contains a description of the scheduler properties. Since you didn't mention task.xml maybe the creation of this file is what is failing...
Drew,
Yes, there is only the task.py file in the folder (no XML). Please see attached screen shot for a copy (paths removed).
Hello everyone,
Thanks to Hugh B ' s help troubleshooting the problem, we have found and addressed the bug in Pro 2.6 Beta 2. The issue is with per-user installs of ArcGIS Pro 2.5, or configured installs that do not write registry settings to the LOCAL_MACHINE folder.
If anyone is experiencing this and would like to test the fix, and other capabilities, provided in the ArcGIS Pro 2.6 Beta program, please send me a notice: dflater@esri.com. If you need to stay using ArcGIS Pro 2.5, the only solution available now is to install using the per-machine option.
Drew