The input path contains spaces glitch in ModelBuilder

[RyanWalter]

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:

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

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

[mikeharol]

I am having the same problem using the geoprocessing contour tool.

[RyanWalter]

Still running into this issue in weird ways. I used the Extract By Mask tool this morning and, instead of providing a mask layer, I decided to create new features within the current map to use as the input. When I did this, ArcPro automatically generated a layer and put that as the mask layer. Surprise, surprise - the error appeared. In this situation, we have ArcPro's self-created named layer throwing this issue.

[TSWCD_GIS]

Ran into this issue today, using the DEM Reconditioning tool from the ArcHydro toolbox.

Output path is: C:\Users\sxxxxx.sxxxxx\Desktop\tempgis\tempras.gdb\AgreeDEM

Error is:

374: Failed to execute. Parameters are not valid.
ERROR 010818: The output path contains spaces.
Failed to execute (EucAllocation).
('line 290', 'c:\\program files\\arcgis\\pro\\Resources\\ArcToolbox\\Scripts\\ArcHydro\\demreconditioning.py', '')

[bentonfranklincd]

I'm having the same issue using the Extract by Attributes tool. I've checked the filepaths, renamed the raster, it's happening with the automatic ESRI name too.

[HeatherDee]

I am experiencing this issue as well in the Visibility Geoprocessing tool with a path that contains zero spaces. When I use the same inputs on a colleague's computer, the error does not appear and she is able to run the tool. If it is a Windows issue, I have attached both mine (Dee) and my colleague's (Dessert) system information to help troubleshoot the issue. 

[JasperRomero]

I am running into the same issue - not consistently, but frequently enough that it's getting annoying. For me it's showing up in the IDW tool. Is there a bug report somewhere I can +1? Or should I submit my own bug report? 

[BillGrimm]

@JasperRomero I think just "kudos" the original post

[JasperRomero]

Something worth trying if other folks are having this issue:

I noticed that this problem may occur when I (i) use a click&drag connection in ModelBuilder to connect the input file to the GP tool or (ii) use the dropdown input field in the GP tool to select the input layer, but the same input file throwing the error stops throwing the error if I navigate manually to the input layer wherever it is in the project geodatabase by clicking on the folder icon next to the dropdown field in the GP tool and then browsing to the right file. Curious to know if this fix also works for others - and if so, what that implies about the root cause of the issue.

[JeremyJohnson4]

We are getting the same error.  What seems to have worked for us, at least using one of the geoprocessing tools (Extract Multi Values to Points), instead of choosing the feature class or raster from the drop down or dragging it from the table of contents, rather click the folder and navigate to the location of the feature class or raster and choose it. As I said, this has worked for us.