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; } } }

Error 000229 when trying to Clip

GIS1

Hi friends,

I am experiencing a weird issue. We have a layer that seems fine. It is visible in our map and we are able to manipulate it in many ways. However, when trying to clip it out given a shapefile, we get the following error:

Error 000229 Cannot open blah blah blah

The ESRI help is not very helpful on this:
http://help.arcgis.com/EN/arcgisdesktop/10.0/help/index.html#//00vp00000005000229.htm

Obviously, the data exists, we can see it on our map. Furthermore, performing the same clip on a different computer works just fine. It's just this one computer that seems to be experiencing this issue.

Any ideas?

Thanks!

Find more posts tagged with

Accepted answers

All comments

MikeLintott

Same error here while exporting to CAD.
Anybody?

GIS1

Getting this again, totally different computer and set of data. Error message and documentation is of no help trying to figure this one out...

RichardSlater1

I'm getting this same error except when trying to merge datasets. It's very annoying and can't find any explanation for it. The data is added to arcmap, displays without issue and appears in the drop down list of the tool, but as soon as you run the tool it gives the error 000229. After the tool has failed, when ticking the layers on and off I get the red exclamation mark signalling a broken data link, but the source location is as it should be.

I managed to get the merge to work by exporting the datasets into a new gdb. Any ideas what the problem is though? Are the files corrupted in some way and are there other ways to resolve it?

MattSidor

I'm having the same problem with the Dissolve tool on a polygon feature class. Incredibly frustrating. ArcGIS Help files, as usual, provide no troubleshooting steps.

BrendanJackson

I was also having problems with this- I got the error message when trying to do an Erase.

After some playing around, I discovered that it had something to do with one of the features being in a file geodatabase, and the other a regular shapefile in a folder. I found that either importing the shapefile into the geodatabase, or exporting the geodatabase feature to a shapefile fixed the error.

BrentBrock

Add me to the users frustrated with this error. I've been plagued by it ever since upgrading to 10.1. I'm seeing it with pretty much any of the analysis tools (clip, erase, dissolve...). All inputs are shapefiles so I'm not seeing the same geodatabase issues as others. But it seems to have something to do with the way layers in the TOC are passed to tools. If you try to drag a layer from the TOC into the tool and it doesn't work, then you know you will get the error. But browsing to the shapefile on the file system instead of trying to input a TOC layer works. The other thing that works is to close and reopen the map doc, after which the tools work again for a little while and then stops again. Both work arounds are frustrating but at least browsing directly to the sources saves time over constantly restarting the mdx.

RandyMcGregor

Include me among the EXTREMELY frustrated. Also, I think it is new with 10.1. I'm getting it a LOT, when the layer is perfectly valid and points to a perfectly valid data source. I just sent a support request regarding it. In my particular situation (today), I'm getting it when rerunning results, but not when running the tool directly.

RandyMcGregor

I believe 10.1 has serious problems with feature layers.

Another issue I'm having is that if you move a layer from one data frame to another, tools do NOT work on it at all, the claim being that the layer does not exist. It is trying to access the layer in the data frame from which you copied the layer and since that frame isn't the active one, it can't access THAT layer. This I think is quite reproducible. When I move a data layer to a different data frame, I HAVE to rename it.

Also, and this is a very old problem that I had hoped would be fixed by now. If you have, say, three layers with the same name (I know... you shouldn't) and pick the third one as input into the tool, the tool process the first layer with that name. Not a bug, but something that reflects a certain, shall we say, lack of sophistication regarding the relationship between a particular layer and its associated data on disk.

RandyMcGregor

One more message.

This topic is very dear to my heart.

In some (all?!) cases, restarting the mxd makes it go away.

For awhile...

Robert_LeClair

One possibility for the Error 000229 code is after installing SP1 for Desktop Background Geoprocessing (64-bit) AND storing one's data in a Personal for MS Access geodatabase, the clip operation will fail. You may read more about this at: http://resources.arcgis.com/en/help/main/10.1/index.html#//002100000040000000

If this is not the case, then I would recommend calling Esri Support Services (Desktop) to create an incident so that an analyst may resolve the error.

Regards,

Robert LeClair
Esri-Denver

JoshThompson1

I suspect that this issue it may very well be related to how the layer is named in the ArcMap TOC. As a test, I would suggest trying to run the tool from ArcCatalog/ArcToolBox rather than running it from ArcMap. That way you will avoid any TOC layer name issues.

If you are successful with the ArcCatalog method, then the next test in debugging the error caused by running it through ArcMap would be to rename the layer in your TOC to something very simple.

Josh

gregmohler

What you get from esri:
"The data is not accessible. It is likely either invalid or not available."
I got this error from a permissions issue from an IDLE window (no arcmap/toolbox/catalog/toc). The SDE database connection doesn't give me access to view/edit/etc the feature classes, hence the not available error. Changing the path to something knowingly wrong gives the usual error000732:"...does not exist or not supported"
Also had problems at home with Windows being wonky about permissions.
edit: My admin guy just ran the script on the files I couldn't access

RobThomas

I've had this problem with clip, joins, and selections when performing geoprocessing in the Python Command Window. Everything runs fine in ArcGIS 10.0, so this is definitely a 10.1 bug. It occurred before and after installing SP1 for Desktop Background Geoprocessing (64-bit). The error occurs on shapefiles and feature classes (GDB). I can run some commands referencing a layer and have it work fine, close ArcMap, open later to run the same commands and receive the error...Sometimes the error would appear for a different layer that didn't give me a problem before. Nothing change in the TOC or with the layers. FRUSTRATING...

My workaround...Every time I received the error I was referencing a grouped layer. Being grouped didn't cause the problem, as it occasionally worked with the same grouped layer, but errors only occurred on a grouped layers. If I moved the layer outside of the group the errors always went away. I've tried several ways to reference the layer (e.g. r'GROUP\lyr', 'GROUP\lyr', 'lyr) but could not find a solution.

As someone else mentioned, sometimes restarting ArcMap helps too.

TimothyPierce

Running 10.1. First time encountering this problem for me. In this case, navigating to the feature classes for Input Features and Clip Features did the trick (as opposed to drag/drop or using drop-down menus). Thanks for the workaround, blbrock.

RandyMcGregor

I'm getting this same error except when trying to merge datasets. It's very annoying and can't find any explanation for it. The data is added to arcmap, displays without issue and appears in the drop down list of the tool, but as soon as you run the tool it gives the error 000229. After the tool has failed, when ticking the layers on and off I get the red exclamation mark signalling a broken data link, but the source location is as it should be.

I managed to get the merge to work by exporting the datasets into a new gdb. Any ideas what the problem is though? Are the files corrupted in some way and are there other ways to resolve it?

I get this error periodically, and I simply don't get it. The file that it "can't open" is perfectly fine, and it is not being editied, so a lock is not the issue (there should not be a lock on it, anyway). It cannot be used as an input. What would prevent a file from being usable as an input?

KieranParsons

I still receive this annoying, pointless, frustrating error message, when all I want to do it union two simple datasets.

Did anyone find a solution? Seems like ESRI won't help.

ChrisErtel

It has definitely got something to do with data being grouped in the TOC.

Come on ESRI, fix this!

EricaMcCormick

I tried many of the helpful and thoughtful suggestions here, but this one was the culprit for me (running 10.2). As soon as I moved them out of a group, Erase worked. Thanks for the troubleshooting!

I've had this problem with clip, joins, and selections when performing geoprocessing in the Python Command Window. Everything runs fine in ArcGIS 10.0, so this is definitely a 10.1 bug. It occurred before and after installing SP1 for Desktop Background Geoprocessing (64-bit). The error occurs on shapefiles and feature classes (GDB). I can run some commands referencing a layer and have it work fine, close ArcMap, open later to run the same commands and receive the error...Sometimes the error would appear for a different layer that didn't give me a problem before. Nothing change in the TOC or with the layers. FRUSTRATING...

My workaround...Every time I received the error I was referencing a grouped layer. Being grouped didn't cause the problem, as it occasionally worked with the same grouped layer, but errors only occurred on a grouped layers. If I moved the layer outside of the group the errors always went away. I've tried several ways to reference the layer (e.g. r'GROUP\lyr', 'GROUP\lyr', 'lyr) but could not find a solution.

As someone else mentioned, sometimes restarting ArcMap helps too.

Anonymous User

I was getting the same error when trying to Clip. I turned off background processing and voila, no more error! Hope this can help someone!

Cheers,
Brendan

DavidCampbell

I was getting this error in modelbuilder. Trying to dissolve and pass the result on to an add field. It wouldn't pass saying it didn't exist. As my output from the tool I had %value%\Name. The output appeared in its correct file folder but would not pass. After playing around, I tried adding '.shp' to the output name and it passed. Not sure if that is too basic and everyone new that, but just in case....

MichaelRobinson1

Same issue. Trying to Dissolve line SHP file. Fails with error 000229.
Fails with either Geoprocessing Tab and with Dissolve selected from toolbox
ArcMap 10.2.1, Win 7

No write access issue to folders which seems to be a common problem.

Solution appears to be to move the file out of the group layer(folder) it is in and put in directly under the main layer.
Works fine then. Not sure what causes this but at least there is a work around for this problem.

ChrisRobinson

Receiving this error while trying to field calculate two records in a table by concatenating the letters "HY-" and the object ID into an ID field. The layer is not in a group, first layer in the TOC and the layer resides in an enterprise geodatabase. Using ArcGIS desktop 10.2.1. Have tried removing the layer and re-adding it but did not work. It did work once I opened up a new arcmap document and pasted the layer there and tried the field calculate.

Chris

DavidCampbell

Ran into this problem again; I have already posted, but I just want to make sure people know....

PUT .SHP TO THE END OF YOUR FILE NAME WHEN CREATING AND THE ERROR GOES AWAY.

JasonSchroeder

My error was resolved because I was inserting a space into the name of the feature class. I ran some Python to remove the space from my variable and this fixed the issue. I was inserting the values from a field into a variable, and naming the feature class from the variable. Unfortunately, some of the values had spaces in them.

See following thread: http://gis.stackexchange.com/questions/92254/renaming-a-variable-input-to-replace-spaces-with-underscores-to-be-used-in-an-ou

It would be nice if ArcGIS would account for this problem - either by automatically inserting underscores for spaces, or by giving an error that makes sense.

JenniferSexton

I am getting this error from the python window when trying to run MakeFeatureLayer_management.

Running 10.2.1 with windows 7 and oracle11g - was not having this problem on 10.1.

None of the solutions I've seen (which are few) have solved this problem so any information is greatly appreciated.

AmandaBishop

I am getting the Union Error #000229 - Unable to open source layer

I have tried several solutions to no avail:

1. Copying the datasets to another file location (desktop, shared network drive, etc.)

2. Renaming the geodatabase and the source files

3. Exporting the source files as shapefiles (.shp)

4. Completely restarting a new project and inserting the files and retrying the Union.

NOTHING has worked! Its ironic because this is simple geoprocessing task that was set up in a tutorial through ESRI.

I have contacted ESRI support and waiting for a call. I will repost if I get a solution.

AmandaBishop

To all those who are interested, I have not spoken with ESRI Support yet, but me and my team have come up with a solution to this issue:

Personal geodatabases have been phased out for computers running 64 bit versions of ArcGIS:

http://resources.arcgis.com/en/help/main/10.1/index.html#//00vp0000002t001324

All of the new computers are 64 bit, and a lot of the older CAD/power machines are 64 bit.

The solution is to create File Geodatabases and export the data you need to a shapefile then import it as a feature class to your new file geodatabase. Go to your project or open Catalog, run the Union tool using the new feature classes (you will have to reset the data source in your project). Remember to store your output in a separate file geodatabase. I don't believe the Union tool will allow you to store the output in the same field geodatabase as the feature classes being processed.

Happy GISing!

ArnoldBijlsma1

I had the same error message when running a Python script containing an Intersect and then a SpatialJoin. I enabled Background Processing in the Geoprocessing Options (no idea why it was off) and suddenly it worked.

GinoMellino

You have helped someone...me! I was getting error 000229 trying to batch merge and buffer 10 or so layers and had tried various work-arounds including removing them from grouplayers but nothing worked. Clicked background processing off and it worked flawlessly. Thank you for posting this!

mrmark

Thanks tojthompson88 - in my case at least it was fixed by change the way things were named in the Table of Contents (ToC). Specifically, the layers that were failing were in a Group -- with a space in the name. ArcGIS 10.3.1 with 64-bit background geoprocessing on. I use underscores EVERYWHERE but the ToC. Now including the ToC.

TheoFaull

Be careful there are no lock files on the layer. Sounds like an access issue to me.

KeithWright1

Helped me, too. A tip o' the compass to you! I was mystified as to why a simple "clip" would not work, especially since my feature classes were entirely accessible and not grouped. Couldn't figure out what on Geo was going on (of course this is ESRI, and their "help" was anything but...).

Then I read Brendan's post: found and un-selected the "background processing" box, which I had never ticked (but which was ticking me off), and suddenly the clip worked.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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