topic sudden path issues problems in ArcGIS Pro Questions

sudden path issues problems

rudbeckia — Sat, 09 Aug 2025 00:36:08 GMT

Hello,

what might cause sudden path issues, i understand spaces/naming/length. this is concerning tools that were running fine, and things being saved in the same place with same character/length that suddenly give a path error

thoughts?

Re: sudden path issues problems

DanPatterson — Sat, 09 Aug 2025 01:04:46 GMT

Pro version? locally stored data sources? network? cloud?

existing projects? same with a new project same data? new project different data source?

and a sample of the error would be useful.

Re: sudden path issues problems

rudbeckia — Sat, 09 Aug 2025 14:56:22 GMT

pro version
network stored
existing project, havent have trouble with this error until now
same project, same file, same path, same tool, only difference is one letter changed in the path, an A to a B
error message :Error 010819 The input path contains spaces.

Re: sudden path issues problems

DanPatterson — Sat, 09 Aug 2025 15:31:05 GMT

this strangeness has been noted recently

Zonal statistic as table always error with 'The in... - Page 2 - Esri Community

some of the issues can't be replicated but one or two have found issues with any form of punctuation in the data path or even the project path containing spaces even though the data did not.

Tech Support is your best option. Also see if working with locally stored data and a new project will at least allow you to continue working past this issue.

Re: sudden path issues problems

RTPL_AU — Mon, 11 Aug 2025 00:43:50 GMT

Have the same problem and have reported it to the locals. Using 3.5.2 currently. It started with 3.5 (I skipped 3.4).

The problem, as far as my testing has gone, is not related to the actual location of the data - we've been able to use spaces in paths for a long time, but it seems to be something that gets broken in a path stored in the project.

In every manifestation of the error, I could navigate to the source data using the folder browser, but if the data is chosen from the GP Tool drop-down or dragged in from a map, you will get the error.

If you open a new instance of Pro and run the Geoprocessing Tool (no map or data added to a map) by browsing to all your datasets, the tools should work fine.
Adding the data to a map and running the GP Tool should be fine but if you save it all as a new project, then close Pro, open a new instance, load the project and then try to run the tool by adding data from the map, you will see the error.

Re: sudden path issues problems

RichardMarountas — Thu, 11 Sep 2025 18:04:27 GMT

I started getting "010819: The input path contains spaces" issues after installing patch 3.5.3. I was able to resolve it by re-installing the patch by going to MyESRI and downloading the patch manually rather than doing the automatic update in ArcGIS Pro. Once I did that it starting working normally again.

Re: sudden path issues problems

Woosh_AP — Thu, 30 Oct 2025 14:45:24 GMT

I found that if I "browse" for the file instead of dragging it in from the Contents pane, I don't seem to get the error.

Re: sudden path issues problems

Woosh_AP — Fri, 16 Jan 2026 06:58:48 GMT

Update to my previous post. This seemed to work in Pro 3.5 but it does not work at all in 3.6, nor does moving the data to a file without spaces. I have had to use "Zonal Statistics as Table" in other software. Really frustrating. I suspect this is a bug.

Re: sudden path issues problems

SteveLowman — Tue, 27 Jan 2026 15:44:05 GMT

Just to add info to the topic

Recently
I had a user who create/clipped a dem into a file geodatabase.
They then went to use TIMES command to change elevation from meters to feet, and reproject to SPC.
The error they got was that there were spaces in the path and the command failed.
I was puzzled at first as I do this all the time and have never had the error.
So we re-ran the clip only this time putting the output in a directory as a TIF file, which I typically do.
Then the TIMES command worked as expected, with spaces in the path.

Not sure why it makes a difference but apparently it does. File Geodatabase did not work, directory at or below same level did work with TIF file. So spaces in path was only an issue with the GEODATABASE and not the TIF using the same command.