topic Re: File Already Exists (Though It Actually Does Not) in ArcGIS Pro Questions

File Already Exists (Though It Actually Does Not)

NadiaNoori1 — Mon, 20 May 2019 13:20:47 GMT

Hello all,

I keep receiving 'WARNING 000725' that states the data set I am creating already exist and what I make now will overwrite it. However I do not have an existing data set anywhere and all that I create are put in new geo-databases that doesn't have these supposed preexisting data set. I never created these layers before and I get this error almost every time I clip, reclassify or create anything really.

Why do I keep receiving this warning?

Thank you,

Nadia

Re: File Already Exists (Though It Actually Does Not)

KoryKramer — Mon, 20 May 2019 13:30:00 GMT

Are you in ArcMap or ArcGIS Pro? Does this happen in a new map/new mxd/new project (depending on which application)?

Does it still happen if you reboot your machine?

Can you provide a screenshot of the example path that the geoprocessing tool is writing to, and make sure to refresh the Catalog Pane/Catalog window and show a screenshot of the output location expanded...

Re: File Already Exists (Though It Actually Does Not)

RobertBorchert — Mon, 20 May 2019 13:44:28 GMT

I see your using ArcGIS Pro. Have you tried compressing your database?

Re: File Already Exists (Though It Actually Does Not)

NadiaNoori1 — Mon, 20 May 2019 13:51:40 GMT

Hello Mr. Kramer, thank you for your response.

I am using ArcGIS pro 2.3.2 and this happens anytime I create a new map or project in any new folders. I have actually switched from a pc to a laptop and started anew though I still see this same warning. My outputs are still being generated so there isn't a problem there, though I don't think I should be seeing this warning as often as I do. I have included the screenshots and pathways below.

The pathway for the output begin created: C:\Users\nnoori\Documents\NNoori_InVEST\Project\InVEST_SCGrasslandBird_2019\GB_LULC_19.gdb\stu_energy_c_Clip

The warning received: WARNING 000725 Output Raster Dataset: Dataset C:\Users\nnoori\Documents\NNoori_InVEST\Project\InVEST_SCGrasslandBird_2019\GB_LULC_19.gdb\stu_energy_c_Clip already exists.

Thank you!

Re: File Already Exists (Though It Actually Does Not)

NadiaNoori1 — Mon, 20 May 2019 14:05:46 GMT

Hello Mr. Borchert, I have not tried to compress my geodatabase. I am unsure of how this will aid in avoiding the warning? I will start a compression right now.

Re: File Already Exists (Though It Actually Does Not)

NadiaNoori1 — Mon, 20 May 2019 14:11:51 GMT

I have tried to compress the database twice and it failed both times. Though it said some of my layers have compressed successfully though majority has not and those include some rasters I made. This is the error it gives me on the fail message, file GpCDFCompressFGDB.cpp, line 334: Saving of data file to file geodatabase has failed (file COM_utils.cpp, line 69: Unspecified error; (code 80004005).

Re: File Already Exists (Though It Actually Does Not)

RobertBorchert — Mon, 20 May 2019 14:14:18 GMT

Well the obvious answer is that you already have a feature dataset or table in your database with the same name.

But you have checked that.

Compression will often remove phantom's (so to speak) from your system.

Re: File Already Exists (Though It Actually Does Not)

RobertBorchert — Mon, 20 May 2019 14:21:31 GMT

So you might have a larger issue with the database itself. Judging by the snapshot you have a number of raster's in the DB

Are there any Map Services running on your machine? You may need to stop services to compress.

I have also found it sometimes problematical to compress a DB from catalog. A work around can be to create a model in catalog for the compress and save it as a python script you can double click on to compress it.

Re: File Already Exists (Though It Actually Does Not)

PegGronemeyer2 — Thu, 16 Apr 2020 16:06:20 GMT

Has this been resolved? (And why would I want to compress a db to fix this error?) Is it a bug? I use Pro 2.5.0

I am seeing the exact same msg as in original post. And since I just renamed what was already not a duplicate I still get "000258: Output <value> already exists" no matter what I name the output feature class.

I am just beginning to use Pro instead of AM...

Thank you,

Peg

Re: File Already Exists (Though It Actually Does Not)

ChrisTruty — Sun, 31 May 2020 14:44:23 GMT

I have the same issue. I cannot create a new feature class (ArcGIS Pro v2.5.1) as it says whatever name I pick, it says it already exists. When I try to compress it says I cannot compress as I get an 'unspecified error.'

file C:\ArcGIS\Geoprocessing\Geoprocessing\Compress\GPCDFFunctions\COM_utils.cpp, line 69: Unspecified error; (code 80004005)
Failed to execute (CompressFileGeodatabaseData).

Thank you

Re: File Already Exists (Though It Actually Does Not)

curtvprice — Sun, 31 May 2020 14:56:59 GMT

These do look like bugs which I recommend reporting.

Two workarounds for you to try:

1. Keep raster names <= 13 characters. A commonality I'm seeing here are long raster names. This has to do with historical limitations in some tools.

2. I have always gotten better raster processing performance (and avoided weirdness) by using file based rasters, that is, esri grid, or these days, .tif, stored in a folder. I think gdb rasters are great for read but not as good for writing.

Re: File Already Exists (Though It Actually Does Not)

ChristianHaugwitz — Mon, 21 Dec 2020 11:47:19 GMT

I know this is an old thread, but I had the same issue today and the same error message in arcgis 2.6.1 while running polygon to raster.

The reason turned out to be that I had unsaved changes to the Polygon I was converting to Raster.

So after saving all edits I could succesfully convert the polygon to Raster.

So the issue is that ArcGIS has very confusing errormessages, the error message should state that the polygon has pending edits and therefore it cant be converted.

Re: File Already Exists (Though It Actually Does Not)

MartyRyan — Wed, 03 Mar 2021 17:59:10 GMT

I am finding the same error in red. It is telling me that a new folder I created moments ago "already exists" and apparently cannot be the output location for the process I want to run. This makes no sense - I could see if I were trying to put the data in an already-existing folder and it was warning me of that fact. How can the location I have just designated as an output location be invalid?

Re: File Already Exists (Though It Actually Does Not)

RobynMyers — Thu, 21 Jul 2022 00:26:02 GMT

Hi Nadia,

I am getting the exact same "Warning" in a brand new Geodatabase (no data in it). I am importing CSV data using the XY Table to Point, and letting ArcGIS Pro set the name of the Output Feature Class - it uses in the Input name 2017_Moja_August05.csv and changes it to c_2017_Moja_August05_XYTableTo Point and THEN flags it with a yellow triangle with an explanation point Warning 000725 - file already exists. But it adds it just fine, there is only one copy of it, and it works just fine. So in my case this appears to be a bug.

Good luck! - Robyn

Re: File Already Exists (Though It Actually Does Not)

stevenlom — Tue, 16 Apr 2024 19:49:59 GMT

Commenting to say that this issue still persists in ArcPro 3.2.0. I have a raster in the project geodatabase that can be seen when put onto the map (it's a raster extent), deleted from the geodatabase (followed by a refresh) only to return. No rasters can be named in its place and it cannot be overwritten or renamed. I'm at a loss for a solution to get rid of this raster.