"summarize failed" error when summarizing geodatabase table

3062
7
Jump to solution
03-05-2021 07:30 AM
Labels (3)
EricMartinson
New Contributor III

Hello all-

I'm getting an error when I try to summarize a geodatabase table on an attribute -- see image below. This is a routine operation that I regularly perform on the same type of table in the same environment. I get no error when I perform the same operation on other tables from the same source and of matching schema.

Attempts to resolve:

  • I have thoroughly searched this site and other ESRI sites, as well as the web in general, and get zero hits. (searching under: <"summarize failed" "an error occurred when attempting to complete the operation">)
  • There is no error information produced in Geoprocessing > Results.
  • I have tried exporting the table to a standalone dbf, then performing the summary on that, with the same error.
  • I see no anomalies when I visually inspect the contents of the attribute fields.

Anyone have any troubleshooting ideas? Thanks in advance for any help.

Eric
ArcMap 10.8.1.14362 on current Windows 10

summarize_failed.jpg

0 Kudos
1 Solution

Accepted Solutions
EricMartinson
New Contributor III

Thanks to you both, @MichaelVolz and @JoshuaBixby, for your replies.

Michael: It's a file gdb on a drive in the desktop on which I'm working.

I'm a little bit embarrassed, but mostly mystified, as I have now succeeded with the operation, though I'm clueless as to why:

Prompted by Joshua's question, I tried summarizing on other fields in the same table, with success. So just to be double-triple sure, before posting on that outcome here, I tried the original operation one more time, and it succeeded. But I have no idea why, as I took the exact same steps with the exact same data that in at least ten previous attempts over multiple sessions (exiting ArcMap and restarting it), yesterday and today, yielded the same error. I can only guess that there was or is some intermittent underlying glitch that my French degree did not prepare me to hunt down.

Baffled but content,
Eric

View solution in original post

0 Kudos
7 Replies
MichaelVolz
Esteemed Contributor

Are you working in a file geodatabase, enterprise geodatabase, other?

0 Kudos
JoshuaBixby
MVP Esteemed Contributor

Does it happen when running the tool on any field in the data set or just a specific field?  The fact you exported it to a different data format, DBF, and it still generates the same error is odd.  I was initially thinking some corrupt data, but usually trying to export data would cause that to show itself.

0 Kudos
EricMartinson
New Contributor III

Thanks to you both, @MichaelVolz and @JoshuaBixby, for your replies.

Michael: It's a file gdb on a drive in the desktop on which I'm working.

I'm a little bit embarrassed, but mostly mystified, as I have now succeeded with the operation, though I'm clueless as to why:

Prompted by Joshua's question, I tried summarizing on other fields in the same table, with success. So just to be double-triple sure, before posting on that outcome here, I tried the original operation one more time, and it succeeded. But I have no idea why, as I took the exact same steps with the exact same data that in at least ten previous attempts over multiple sessions (exiting ArcMap and restarting it), yesterday and today, yielded the same error. I can only guess that there was or is some intermittent underlying glitch that my French degree did not prepare me to hunt down.

Baffled but content,
Eric

0 Kudos
JoshuaBixby
MVP Esteemed Contributor

Glad it is working, at least working for now.

MichaelVolz
Esteemed Contributor

The data is stored on a local drive (e.g. c-drive or e-drive) as opposed to a network drive?

At 10.7.x I have resorted to mostly working on file gdbs on a local drive for processing and then copying result to network.  I need to start testing geoprocessing in ArcPro to see if I have problems with processing on network like I do with ArcMap.

0 Kudos
EricMartinson
New Contributor III

Hi Michael-

Everything is on drives in my desktop computer, not networked. Software running on C-drive, data on another internal hard drive.

Eric

0 Kudos
LetaRogers
New Contributor III

I know a few months have elapsed and you've probably figured this all out, but I had this problem when the file name I was giving to the summary table started with a number. So, field 200ft_Buff would not work using that name (I got that error), but x_200ft_Buff worked fine.

0 Kudos