Select to view content in your preferred language

Cannot export feature classes or use tools with output path

228
5
Jump to solution
4 weeks ago
Labels (1)
RogierMeerlo
New Contributor

Hi everyone,

For an assignment I have to create a shape file from an existing feature class. I tried to use the "Feature Class to Shapefile" tool, but it always gives me an error. It seems to shorten the path to the Output Folder, whatever I try. I have tried to select the designated folder manually and I tried copy pasting the path into the Output Folder field, but ArcGIS Pro always immediately cuts the path up into a shortened non-existing path. I think this makes the tools fail. I have checked the length of the path, it is under 200 characters every time, so that shouldn't be the problem. Is anyone familiar with this problem?

It gave me this error code:

Failed to convert: [feature class name]. ERROR 000210: Cannot create output I:[shortened file path].shp.
Failed to execute (CopyFeatures).

Also, I cannot create new feature classes in existing geodatabases. When I try this I get a blank error with no error code. When I try to export a feature class it gives me this error:

ERROR 999999: Something unexpected caused the tool to fail. Contact Esri Technical Support (http://esriurl.com/support) to Report a Bug, and refer to the error help for potential solutions or workarounds.
CreateFeatureClassName: The workspace I:[shortened file path] does not exist.
Failed to execute (ExportFeatures).

I'm using ArcGIS Pro desktop version 3.2.3.

Thanks in advance for the help!

0 Kudos
2 Solutions

Accepted Solutions
JesseCloutier
Esri Community Manager

Hi @RogierMeerlo, we appreciate you sharing a potential bug with the broader Esri Community; however, Esri does not actively track software defects posted here. The official channel for investigating and validating bugs is Esri Technical Support. All customers experiencing a potential software bug should leverage technical support to report and investigate the issue.

By reporting bugs through technical support, Esri can better track the scope and impact of the issue across all our customers and better prioritize it with our product teams. Our teams can also investigate the issue more thoroughly to see if there is a solution, workaround, or patch to get you back up and running as soon as possible.

As a reminder, Esri Community is primarily a self-service support platform where Esri users can ask or answer each other’s questions, share feature requests, and collaborate to solve problems with GIS.

*Note that this is a scripted message prompted when posts allude to a potential product bug.

Jesse Cloutier
Community Manager, Engagement & Content

View solution in original post

0 Kudos
RogierMeerlo
New Contributor

Thanks for all the suggestions! one of my colleagues came through with the answer. We are working with a network drive for our projects and apparently i was only granted access to one of the lower folders in which the project was seated. 

Weirdly this meant that ArcGIS Pro couldn't traverse the higher folders to get to the lower one for the export but could see the location of both shapefiles and .gdb's in the catalog window. 

Best regards,

Rogier

View solution in original post

0 Kudos
5 Replies
JesseCloutier
Esri Community Manager

Hi @RogierMeerlo, we appreciate you sharing a potential bug with the broader Esri Community; however, Esri does not actively track software defects posted here. The official channel for investigating and validating bugs is Esri Technical Support. All customers experiencing a potential software bug should leverage technical support to report and investigate the issue.

By reporting bugs through technical support, Esri can better track the scope and impact of the issue across all our customers and better prioritize it with our product teams. Our teams can also investigate the issue more thoroughly to see if there is a solution, workaround, or patch to get you back up and running as soon as possible.

As a reminder, Esri Community is primarily a self-service support platform where Esri users can ask or answer each other’s questions, share feature requests, and collaborate to solve problems with GIS.

*Note that this is a scripted message prompted when posts allude to a potential product bug.

Jesse Cloutier
Community Manager, Engagement & Content
0 Kudos
MikeVolz
Frequent Contributor

Are you required to use a shapefile?  How about saving to a file geodatabase?

When you mention "shortened path", are you sure it's actually shortening the path?  Most tools only show the full path while you're editing that field.  Otherwise, they just show the file name.

For example:

Full value stored in the output: "C:\ProjectData\outputfeature.shp"

Display value when you don't have the output field selected: "outputfeature.shp"

The next thing to check would be whether you have the necessary file permissions to save a file into whatever folder you're targeting.  If it's a University or similar large organization's server, for example, you might be trying to save outside the space designated for your user.

 

Also, while irrelevant to the topic at hand, anytime shapefiles are mentioned, I feel obligated to raise the suggestion to consider whether you need shapefile, or whether the requestor is using the term in the generic "GIS data" sense.  See https://switchfromshapefile.org/ for more information on the ups & downs of shapefile in the modern GIS ecosystem(s).  That link is often slow to update its security certificates, so if you get odd warnings and don't feel comfortable, try back in a few days.

------------------------------
M Reed
"The pessimist may be right oftener than the optimist, but the optimist has more fun, and neither can stop the march of events anyhow." — Robert A. Heinlein, in Time Enough for Love
RogierMeerlo
New Contributor

Thanks for all the suggestions! one of my colleagues came through with the answer. We are working with a network drive for our projects and apparently i was only granted access to one of the lower folders in which the project was seated. 

Weirdly this meant that ArcGIS Pro couldn't traverse the higher folders to get to the lower one for the export but could see the location of both shapefiles and .gdb's in the catalog window. 

Best regards,

Rogier

0 Kudos
MikeVolz
Frequent Contributor

I clearer error message in ArcGIS Pro from ESRI about permissions would have made finding this solution so much easier.