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 100014 Code Failed

IrelandHackman

I've been working with my coworker trying to figure out why she can't use the "Summarize Within" tool in her project.

We've tried shortening the names of the fields, shortening the name of the output layer, creating a new geodatabase, trying to summarize just a selection of the data (as her current data layers have thousands of entries), unchecking the "Add shape summary attributes" box. Nothing. We've even tried writing to a different location on the computer that has a shorter destination name. That didn't work either.

She's also tried saving and restarting the project, restarting the computer. Still nothing. Her version of Pro is currently 3.2, maybe that's the issue?

We referenced this post as well as various others on the blog and I just wish we could figure out what the issue was. The only thing that was helpful was this bug post I found.

Any insight into this issue would be much appreciated.

Find more posts tagged with

Accepted answers

Robert LeClair

Thank you for the information. So in studying this item, I did see one Esri Support case where the error code was misleading. It had nothing to do with the field lengths at all and was a projection issue with the data. You may want to verify/check the projections and transformations being used for the input feature classes and see if that is the issue.

Maybe (or maybe not) related - there is BUG-000172797 - "When using the Summarize Within tool in Modelbuilder or from geoprocessing tools, the process fails and returns the error, ERROR 100014: Summarize Within failed. Failed to execute (Summarize Within)" This was logged at 3.4 and is under consideration.

All comments

IrelandHackman

Yes, this was the result of a Clip GP tool. And to rename the attribute columns, we tried multiple ways. We tried renaming it within the attribute table manually (changing the aliases [which in hindsight, might not do much]) and we also tried creating a brand-new field with a shorter name and copying the data to that new field.

These changes were applied to the point layer, not the hexagon tessellation layer.

Robert LeClair

Thank you for the response. You mentioned one dataset was clipped - is this the result of a Clip GP tool or something else? What was your workflow to manually rename the attribute columns? Was this for the CSV file or the GDB feature class?

IrelandHackman

I just double-checked and there were no joins performed on the dataset, but the one was clipped. Could that be the issue? We also manually renamed the attribute columns, in an attempt to fix any potential length issues.

I also double-checked with her and she said that both datasets had over 60k entries, "if not more". I don't think that having that many entries would make it fail. Run slowly, for sure, but not fail. We tried running the tool on a selection (much smaller) from the dataset and that failed as well.

One layer was a simple point layer (slightly edited to remove bad data) and the other was an H3 hexagon tessellation polygon layer.

Robert LeClair

Are there any JOINs on your dataset? If so, field length on the JOIN table could also be the issue. Export the JOIN to a new feature class and attempt the workflow again.

danretired

You have tried all the referenced suggestions and the bug, so I would copy the source geodatabase to a computer with a newer version of Pro to test. Otherwise contact Tech Support since something may apply to Pro 3.2 that has been addressed already

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.