Scheduling Geoprocessing fails with no error messages

[JonahRemigio]

Hi! Having huge issues using the scheduler in ArcGIS Pro (64-bit) for geoprocessing, and there is hardly any knowledge online about the scheduler itself. I'm just trying to run the Raster Calculator with the scheduler, which of course sounds very simple. However, trying to perform this simple task has led to literal weeks of scouring forums.

Basically, I have two .tif files stored on my local computer. Not a on VM, not on a server, they're stored locally. My code simply compares the intersection of certain values:

("2001.tif" == 0) & ("2023.tif" ==1)

In this example, I'd be looking for specific pixels that have a value of 0 in 2001, and a value of 1 in 2023. Easy!

Now if I just run this off the bat, there's no issues. It's for a country-sized area, so it takes some time, but no problems come up. However, the second I try to run this through the scheduler, nothing works. The command will run for about 0.2 seconds, fail, and will say "There are no messages." leaving no way of knowing what's gone wrong.

Here is an exhaustive list of everything I've tried:

• Rebooted computer
• Reinstalled ArcGIS
• Turned on log XML feature of geoprocessing (it doesn't write a log when it "fails")
• Remove spaces from source .tif names
• Remove numbers from source .tif names and resulting .tif names
• Moved files to other local folders
• Unchecked "Read-only" in properties of folders with source files and resulting files
• Checked Windows Credential Manager to see if Python or ArcGIS needed credentials to operate a schedule (dead end, neither ArcGIS, Python, or Esri were in the list)
• Looked into Windows Task Scheduler (doesn't help, since the process doesn't start, it doesn't create a task)
• Tried finding a way to turn off background processing (there is no way... I'm on Pro which is 64x and is built on background processing)
• Made sure my Processing Extent was correct (either Default or Union of Inputs)
• Made sure my Output Coordinate System is correct
• Made sure I have access to Spatial Analyst
• Authorized ArcGIS Pro to work offline
• Made sure Python is up-to-date
• Made sure ArcGIS is up-to-date (in fact, I tried this in two different versions and still had this issue)
• Made sure to have .tif at the end of the output raster name
• Made sure my RAM is all good (have a ton of memory on this device so it should not be an issue, CPU and GPU are also definitely good enough)

I am out of options. I've tried everything I can. At this point, it seems like the scheduler is loaded with issues and there is hardly any support for it. Any help would be much appreciated, because otherwise I'll need to calculate around 100 raster calculations and zonal statistics manually.

[DavidPike]

Are you sure that it doesn't exist in task scheduler? A task should exist if it was created on a schedule.  I'd adjust the settings to run it as admin.

Also in your raster calculator I'd ensure that the Datasets are referenced rather than the Layers.

[JonahRemigio]

It wouldn't even start Python, let alone create a task which I found weird. Tried running on admin and making sure things were referenced but still ran into the issue.

A solution was found by @BarryNorthey which just involves recreating the process in the Model Builder. Once you do that, you can go into the Catalog, Toolboxes, and then under your project you can find your model to Open and then schedule as needed.

Just a note for anyone reading this in the future, if it doesn't seem like your Scheduled task is running (the icon doesn't change), just check Task Manager and look for a Python process. ArcGIS will create a separate process for each scheduled task running at a time.

[BarryNorthey · Accepted solution]

ArcGIS Pro 3.1.1. I tried a simple raster calculation that ran fine on its own but it would not schedule for reasons unknown. I created a simple model in Model Builder that did the exact same thing and scheduled it to run as a model (every 5 minutes for testing) and it worked OK. Don't know why but it might work for you. I used the full dataset path to the raster and %t% at the end of the output raster name to create unique output names.

Schedule a Model Run

[JonahRemigio]

Thanks! Turns out if you just recreate your process in the Model Builder, it'll run. For anyone else trying this in the future, adding the %t% to your file name did not seem to fix the issue for me.

Seems like Esri may need to fix the scheduler and add more online support. Hopefully this thread helps someone in the future.

[Matt-Goodman]

I'm running into the same issue. I actually have a simple geoprocessing tool that has run in the scheduler every day for nearly 70 days without any issue. But now it just won't work when run in the scheduler. It returns a non-specific error.

What's most confounding is that if you r-click the scheduled task and choose 'open' and then run it as a regular geoprocess, it runs just fine. 

[DavidPike]

From what I remember, The python script references the APRX which was open when the task schedule was created in ArcGIS Pro.  Would be an idea to check that script and see what it's referencing, as if you opened a new project or .mapx and created a scheduled task without then saving the project - it would point to some non-existent temp location and fall over.

Is a service account set in Windows Task Scheduler?  If so then you can have obvious issues with file permissions and drive mappings.  Try checking the 'run with highest privileges' button or whatever it is also.

[DavidFotheringham1]

I just wanted to say this answer fixed all my problems!

I just couldn't work out why a bunch of toolboxes I'd made were not working on a schedule and the issue was I originally ran them through a blank aprx which I then didn't save. I now have an aprx that is named 'For Scheduling' for any future times where I need to schedule a geoprocessing service. 

[CarlMorrison]

See if this helps  https://support.esri.com/en-us/bug/the-error-message-permissionerror-errno-13-permission-d-bug-00014... 

[Bud]

Someone ought to submit a case to support.