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.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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:

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.

Najděte více příspěvků označených jako

Desktop

Accepted answers

All comments

BryanBishop

It did fix it for mine, at least for now. Trying to use Basin tool and no avail, no spaces at all but the error still comes up. Then did what you suggested and it worked. When I added from the drop down, it immediately had the spaces error again. Added directly from geodatabase and it cleared the error and worked again.

TSWCD_GIS

Yep, I have this error occurring every other time I use Pro now. Like you said, closing Pro and reopening tends to fix it for me and has been my go-to work around.

buckeyes82

Put your layer into a layer group and try running it again. In my case, I kept getting Error 010819 whenever I ran Zonal Statistics as Table, but it worked once the layer was placed inside a layer group.

I think it blocked again.

KevinMayall_COH

He's not putting a "1" as the start of an output name. He's putting 1 as a constant value. How a constant value has spaces in it is beyond me.

MollyJordan

We are now struggling with this issue on our custom tools, only when they pertain to raster or DEM type datasets. Is there any update from ESRI regarding this issue? We have ArcPro 3.5 and updated to the most recent patch as on 10/20/25.

Molly

JoabelBarbieri

Nope it didn't fix it

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.

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.

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.

JoabelBarbieri

Error 010819 The input path contains spaces.
same issue here and there's no dam space!!!!!! urg

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.

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.

BillGrimm

@JasperRomero I think just "kudos" the original post

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?

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.

DEE_SystemInfo.png

DESSERT_SystemInformation.png

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.

mikeharol

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

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', '')

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.

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.

danretired

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

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.

Input_raster.png

danretired

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)

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:

danretired

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.

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.

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!

danretired

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

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.