The output path contains spaces. - Is this a bug?

[C_McNamara]

[DanPatterson]

probably not directly related,but there are a few errors associated with 010819 number relating to how the input data sets are accessed

BUG-000179464 for ArcGIS Pro

in short, navigate to the folder containing the raster or the location of the raster in a geodatabase... don't select the layer name, but navigate to the source data.  esri grids don't work if the source folder contains spaces

[C_McNamara]

The Dan! My input dataset is perfectly fine - not getting an error for my input surface raster. The error is coming from a numeric input parameter value associated with a Percentile Value(s) that contours will be evaluated for. The default value is 90, which is what you see inside the image. 

[DanPatterson]

I saw that, but it is the error number that is being thrown regardless of the spatial analyst tool being used.  I couldn't tell if your raster was an esri grid or a raster in a geodatabase (since there is no *.tif extension, for example).  If it is an esri grid, then the path cannot contain spaces.

The fact that the red x occurs on the line where the percentage threshold is located isn't related to the error message.

There is nothing related to that particular tool in the public facing suppor site, only errors relating to spatial analyst tools and that particular error number.  Tech Support may have access to non-public causes for this error if my suggestion still doesn't pan out.

Good luck

[RhettZufelt]

do you still get the error when you click the folder button and browse to the input surface, and NOT select it from the dropdown?

 R_

[DanPatterson]

suggested previously already.... in short, navigate to the folder containing the raster or the location of the raster in a geodatabase.

[RhettZufelt]

saw that, but response had no indication that it was tried.

[Robert_LeClair]

As Dan suggested, Esri GRID's do not support spaces in the file path as referenced here - 010819: The input path contains spaces.—ArcGIS Pro | Documentation

Perhaps export the raster out to a geodatabase raster, then try the workflow again.