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.

[DanPatterson]

All I can see is the name and not the full path in your screen grab.  Can you confirm that the full path is space free

[KatyAppleton1]

The error is that the path has spaces, not just the filename (which is all that is visible in the screenshot). I see that you said you tried writing the input file to a folder and geodatabase path with no spaces anywhere present - but that is what I would be double checking.

Is there a chance your save location could be specified in different ways (e.g. a mapped network drive)? Is there a way to get ModelBuilder to show the file path in full?

Just generally, this suddenly seems to be an error in 3.4 whereas it was not in earlier versions. Very frustrating!

[RyanWalter]

I can confirm that there are no spaces in the file path and I had never had this issue before the beginning of March 2025. I have tested this with other rasters saved to C:\Test\nospaces.gdb\rastername

Error still occurs

I have uninstalled and reinstalled ArcPro. Error still occurs. I have updates to the newest version of the software. Error still occurs.

Sometimes, if I open this tool in another ArcPro project, it works just fine - even with filepaths with spaces.

When this problem occurs in ModelBuilder, it also occurs in the Extract by Mask Tool outside of MB. It depends on the day if it wants to behave or not. Incredibly frustrating and I have done everything in my power to fix it - still no luck.

[DanPatterson]

There are only 7 bugs listed for modelbuilder in arcgispro 3.4

Esri Support Search Results

I would contact tech support since they may not have received any reports or they are still assessing it before putting notification on the public facing site.

[DaveronSmith]

As you mentioned, this is a wider issue, not just in modelbuilder, but also in geoprocessing toolbox. Here it is replicated with nothing but the input constant 1 for the Con tool in both modelbuilder and geoprocessing:

 

 

[DanPatterson]

Why are you putting a "1" as the start an output name?

This can fail for many reasons, but if the tool doesn't know whether the output raster will be an esri grid or a tiff, it might do the check first and since esri grids cannot begin with a number, it may just throw the closest error in its path.

My recommendation is to click on the folder icon beside the output and input names,  from there navigate to the folder or geodatabase where you want your raster to go.  The recommended output from esri is to specify outputs as *.tif files in a folder.  After selecting the folder, you should be able to enter a filename (not beginning with a number) with a specified file extension (eg *.tif)

Again, recommended practice would be to navigate to and select the destination location, specify the filename with extension ensuring that the output path doesn't contain spaces and the output filename doesn't begin with a number, contain spaces and has a specified file extension (unless you want an old-school esri grid for some reason) 

[BillGrimm]

I'm getting the same error trying to use Extract by Mask in geoprocessing--see below. The path is G:\gis_data\elevation\elev_dem30_bath_2015\dem30_bath_16.

[DanPatterson]

So is it an esri grid then?   And is 'G' a local drive?

Try Copy raster to get it into *.tif format, which is the raster format that esri recommends now

[RyanWalter]

I filed this bug with ESRI a few months ago. He mentioned they hadn't seen the bug before but he filed something internally. I still occasionally run into the issue, but less so these days. Sorry to see that others are still finding it. The ESRI technician I spoke with seemed to believe Windows was the culprit, not ArcPro. I haven't heard anything more since late March, 2025.