Select to view content in your preferred language

sudden path issues problems

83
4
Friday
rudbeckia
Emerging Contributor

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?

0 Kudos
4 Replies
DanPatterson
MVP Esteemed Contributor

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.


... sort of retired...
0 Kudos
rudbeckia
Emerging Contributor

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.

0 Kudos
DanPatterson
MVP Esteemed Contributor

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.


... sort of retired...
0 Kudos
RTPL_AU
Honored Contributor

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.



0 Kudos