The input path contains spaces glitch in ModelBuilder

RyanWalter · ‎03-05-2025

Have run into an error I have never seen before nor have any clue how to resolve at this stage. ModelBuilder is telling me the input dataset I have has spaces in it. As you can see from the screenshot, no it does not.

I have tried to:

Restart Arc
Save the model as a new version
Write the input file to a folder and geodatabase path with no spaces anywhere present
Change the name of the input dataset on a re-export to a singular word
Restart my computer
Uninstall and reinstall ArcPro

All to no avail. Would love guidance, been doing this for 8 years and never seen something like this happen.

JasperRomero

@JoabelBarbieri does the solution suggested by myself and @JeremyJohnson4 work for you as well? Would be interesting to know if that is the fix, maybe that will allow someone at Esri to diagnose the issue and correct it.

dribrats

I am running into this issue as well, but it is occurring on custom scripts that I've written. These scripts have worked for years without issue and have started failing with this error in the last couple of months. At first I thought it was because they had some legacy ArcPy code in there that was no longer playing nicely with Pro, but after re-writing several of them using the latest API, I'm still running into the issue. For me, the common denominator seems to be Spatial Analyst tools. I have confirmed that the error does not occur consistently. I'll think that I've fixed it because the script will run successfully, only for the issue to crop up again on a subsequent run. I can also confirm that the input paths used NEVER contain any spaces. (such an antiquated requirement anyway). I'll let you know if I'm able to sleuth out a solution.

MinhazulIslam919

I encountered the same issue with "Error 010819: The input path contains spaces", while there is not a single space in the path, actually. Interestingly, closing the map document and ArcGIS Pro, and then reopening them, sometimes makes the error disappear. However, if I continue to use the same tool afterward, the error reappears.