topic Re: There was an error trying to process this table. in Data Management Questions

There was an error trying to process this table.

JustinTomei — Thu, 18 Jul 2013 17:31:59 GMT

I have a dataset of about 32000 addresses I have been trying to geocode. Time after time I keep getting the same error message, the one in the title of this thread. I have changed names of columns, tried making it a dbf, tried removing everything but the address information, splitting the data in half to make it smaller. Regardless of what I do i get anywhere from 1%-5% done and I get the error.

Any ideas?

Thanks.

Re: There was an error trying to process this table.

JoeBorgione — Thu, 18 Jul 2013 18:36:32 GMT

I have a dataset of about 32000 addresses I have been trying to geocode. Time after time I keep getting the same error message, the one in the title of this thread. I have changed names of columns, tried making it a dbf, tried removing everything but the address information, splitting the data in half to make it smaller. Regardless of what I do i get anywhere from 1%-5% done and I get the error.

Any ideas?

Thanks.

As long as you've made all the field names one word with no special characters, you should be good there. (Typically it'll bail out right at the get-go if thats the problem.)

My guess is somewhere you've got a <null> value in on of your address records. Personally, I'd make sure the address table is within some flavor of geodatabase. That way all your data and results can be in the same place.

Re: There was an error trying to process this table.

AnthonyMosinski — Wed, 24 Jul 2013 00:17:47 GMT

I am as well having this problem I have a data set of over 250,000 address. I have tried to do the entire table but that gets no where. Thus I am breaking the data out into sets of 10,000 at a time then seeing how many run then deleting them out of the excel file then running what is left of the 10,000 until I have geocoded all 10,000. I continue to get the error and I would love to know if there is a solution to this error as well as if there is a way I can run a bigger batch or is it easier to just keep breaking them up.

I have deleted all unnecessary columns in the excel file I only have street address (#s and street name), city, state, zip and a unique ID so I can match everything back up after I merge all the shapefiles.

Any help with this would be great thank you.

Re: There was an error trying to process this table.

TOMKONG — Wed, 24 Jul 2013 00:51:59 GMT

I am as well having this problem I have a data set of over 250,000 address. I have tried to do the entire table but that gets no where. Thus I am breaking the data out into sets of 10,000 at a time then seeing how many run then deleting them out of the excel file then running what is left of the 10,000 until I have geocoded all 10,000. I continue to get the error and I would love to know if there is a solution to this error as well as if there is a way I can run a bigger batch or is it easier to just keep breaking them up.

I have deleted all unnecessary columns in the excel file I only have street address (#s and street name), city, state, zip and a unique ID so I can match everything back up after I merge all the shapefiles.

Any help with this would be great thank you.

After the ESRI has upgraded the ArcGIS data model from coverage to shapfile to geodatabase, the geoprocessing tools couldn't deal with the large dataset input.
But the old coverage geoprocessing tools can handle the large dataset input, so you need:
1. Installing the ArcInfo workstation in your PC first (then load the coverage tool in, or you can use command line to run)
2. Convert your all input data to coverage format.
3. Run coverage geoprocessing tool.
(Often it happens when you run shapfile or geodatabase geoprocessing tool, it will give a message about lack of memory. Actually it is not the memory issue).

When I deal with large dataset input, I always switch to run coverage geoprocessing model under ArcInfo workstation.

Re: There was an error trying to process this table.

JoeBorgione — Wed, 24 Jul 2013 12:58:54 GMT

Are you suggesting converting an excel spreadsheet into a coverage? I'm a little confused by that if you are.

I routinely geocode hundreds of thousands of addresses without any bail outs, seizures, or other malfunctions. I'm sticking with my story; excel is a great spreadsheet. I use it all the time to bill my clients and pay my taxes. When it comes to actually making my living, I use data bases. Back in the day Info ruled as a data base; that was then this is now.

Re: There was an error trying to process this table.

PeterHanmore — Fri, 26 Jul 2013 14:19:42 GMT

We got this error frequently when building our custom locators. For us, the error is actually triggered by the ArcGIS desktop geocoding tool timing out after exactly 1 minute from the time the batch of addresses was submitted. If the arcgis geocoding service cannot process all the addresses in the batch (and return a response) within 1 minute, the ArcCatalog / ArcMap geocoding tools will time out.
You can mitigate this issue by decreasing the suggested batch size (at the cost of some performance) so that fewer addresses need to be geocoded within 1 minute. We also found that for some reason, multiline (addresses broken into street + city fields) geocoding is significantly slower than single line (unparsed) geocoding. I have not found any way to change the behaviour of ArcCatalog so that it will wait longer than 1 minute before timing out. If anyone else knows, I'd love to hear how you do it.

Re: There was an error trying to process this table.

KimOllivier — Tue, 06 Aug 2013 02:31:05 GMT

People seem to be having some serious problems geocoding a small file of one million records!
You should never have to split a table for geoprocessing since it is a serial process. Unless you are trying to use a server geocoder for batch. In this case the app posts all the records across and back again, not really likely to be fast enough before a timeout.

As a benchmark, I expect to be able to geocode addresses at the rate of at least 1M/hour and sometimes up to 6M/hour on my desktop machine. My typical file contains half a million addresses. I have the reverse performance experience with single line versus batch processing, single line slows down to one tenth the speed because zone indexes cannot kick in.

Therefore I hope you can keep looking for the non-obvious error that is causing the problem for you.
My laptop has no trouble geocoding any size file, so it is not the size of the machine.

It is likely that indexes are essential for normal use. Do you have parts of your address that can be indexed to allow the geocoder to break up the search? Such as state, zip or city?

Any geoprocessing across a network drive is a mistake! This includes geocoding. Networks are just not fast enough with all the packing and unpacking to send each request in a reasonable time. Put your geocoder, source and output on the same local machine on a local drive. I understand this will break "corporate policies" nearly everwhere, but do a demo to show the problem to your administrator. You will have to copy-process-replace. This will also apply if you are using a remote database using SDE.

I personally copy any source from a spreadsheet, shapefile or text file to a local filegeodatabase table. That enables indexing and unlimited sizes and makes it easy to put back in an enterprise database. You have complete control over the field types, null values and other unexpected data that will trip up the geocoder. Null values are sure to cause indexing to fail.

It is very hard to set up a custom locator properly, I have yet to make them work properly myself after trying to tweak the defaults. The default timeout in my locator is 100 seconds, but who wants to wait for that for each failure? If it takes even a millisecond it is too long, so I set it for 1 second. If timing out is a problem, then indexing is not kicking in.

If indexing is not running, why not? Either the reference does not have suitable indexes being built or you are throwing address candidates at it that do not have indexable components, eg no state when the locator expects a state.

Re: There was an error trying to process this table.

KevinPark — Thu, 08 Aug 2013 19:18:24 GMT

I am still having issues. I am trying to geocode five years worth of data with roughly 20K records in each year, working for ArcGIS Desktop 10 Service Pack 5 (ArcInfo license).

I have tried the 10.0 North America Geocode Service and 10.0 US Streets Geocode Service.

When I try to geocode from the csv file I get the message "There was an error trying to process this table" with no further information.
When I try to geocode from after converting to a geodatabase table I get a variety of different error messages, including
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt" or
"No resource could be found at that address"

But I don't understand because I got two years of data to work. There is nothing different about the remaining three.

Re: There was an error trying to process this table.

JoeBorgione — Thu, 08 Aug 2013 19:37:17 GMT

I am still having issues. I am trying to geocode five years worth of data with roughly 20K records in each year, working for ArcGIS Desktop 10 Service Pack 5 (ArcInfo license).

I have tried the 10.0 North America Geocode Service and 10.0 US Streets Geocode Service.

When I try to geocode from the csv file I get the message "There was an error trying to process this table" with no further information.
When I try to geocode from after converting to a geodatabase table I get a variety of different error messages, including
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt" or
"No resource could be found at that address"

But I don't understand because I got two years of data to work. There is nothing different about the remaining three.

Any chance you can provide one of the csv's that bail out?

Re: There was an error trying to process this table.

KevinPark — Thu, 08 Aug 2013 19:47:25 GMT

Any chance you can provide one of the csv's that bail out?

Afraid not because of confidentiality issues.

I got another error message though from using the geodatabase table: something about bad syntax, but I was using the dialogue box.

Re: There was an error trying to process this table.

KevinPark — Fri, 09 Aug 2013 09:35:52 GMT

I was able to geocode three years, 90% of a fourth before failing, but only 10% of the fifth year. I didn't change anything. The databases have the same format. I can't figure out why it sometimes works and sometimes doesn't.

Re: There was an error trying to process this table.

JoeBorgione — Fri, 09 Aug 2013 14:47:04 GMT

Kevin-

If you haven't tried this already, open your (pre-geocoded) address table and sort ascending on the address field. Examine the top rows. If they look okay sort the address field in descending value, and examine the the top rows. This is what I do when things go south on me. The objective is to isolate odd address strings including <null> values etc.

Re: There was an error trying to process this table.

BruceHarold — Sun, 11 Aug 2013 01:07:13 GMT

Hi
things should not be this hard, can everyone please open support calls, but be prepared to supply locators plus data.
I suspect timeout issues. Kim you are a special case - contact me.
Bruce

Re: There was an error trying to process this table.

ChidiEzeolu — Tue, 27 Aug 2013 17:53:50 GMT

I recently installed ArcGIS 10.2. With this version, I have been unable to Geocode addresses from an excel worksheet. I don't think it's a file size issue since I've tried to Geocode with only 3 rows and get the same error. I didn't have this issue in the previous version and I'm using the same data. I've tried multiple solutions provided in the ESRI forums, such as 1) moving my data to a local drive rather than network drive; 2) trying a Microsoft update hotfix (http://support.esri.com/en/knowledgebase/techarticles/detail/41119); 3) changing the output location (http://forums.arcgis.com/threads/82696-Setting-out-points-on-a-map). I also tried repairing my ArcGIS 10.2 install. Unfortunately, none of these solutions have worked in resolving the issue.

Since ArcGIS 10.2 uses World Geocode Service, I was thinking of doing what Kevin did and try 10.0 North America Geocode Service and 10.0 US Streets Geocode Service.

Re: There was an error trying to process this table.

Nanobi_ — Tue, 27 Aug 2013 18:12:24 GMT

Re: There was an error trying to process this table.

KimOllivier — Wed, 28 Aug 2013 08:07:55 GMT

Maybe don't use a spreadsheet as a data source because all the text fields will be 255 character wide and all numbers floating point?

Use Microsoft schema.ini to load from a csv dump of the sheet or use FME to load with valid field names and normal widths. Many people have trouble with the default loading of spreadsheets for any geoprocessing, not just locating.

Putting the source on a local drive is a good idea, but if it is a spreadsheet it's still a bad format to use in data processing.

Re: There was an error trying to process this table.

BryanSheasby — Thu, 05 Sep 2013 13:39:44 GMT

Just to throw this out there, I have tried geocoding from xlsx files, csv files, and mdb files. All give the same error. All start the process and fail later. The program needs to be able to deal with data from any source that allows you to click on it and it needs to be able to ignore errors and continue geocoding. All errors should be noted in another output. This is 2013 and this problem existed all the way back in 2003. This should not be happening still.

Re: There was an error trying to process this table.

BryanSheasby — Thu, 05 Sep 2013 15:48:03 GMT

Update: I actually uninstalled ArcMap 10 SP5

I am now on ArcMap 10 with the following service packs and patches
SP3
SP3 Patch for Geocoding
SP4

Now the same lists I was using before will complete.

Re: There was an error trying to process this table.

BryanSheasby — Fri, 06 Sep 2013 17:21:34 GMT

Update 2: The problem is back
I attempted a list of 8,000 records or so and it got through about 2,200 and displayed the same error. Of course never telling me which records was the problem or what the problem even was.

Re: There was an error trying to process this table.

JoeBorgione — Fri, 06 Sep 2013 17:27:55 GMT

Update 2: The problem is back
I attempted a list of 8,000 records or so and it got through about 2,200 and displayed the same error. Of course never telling me which records was the problem or what the problem even was.

Two suggestions;
1)If you can, post your data here and let someone (me for instance) give it a go. ( you can shoot me a message about it if you want.)

2)Get ESRI tech-support involved. I can appreciate your frustration on this, but as I mentioned earlier, I geocode thousands upon thousands of addresses per year, and never with so much as a hic up. And I've been doing it in ArcGIS since version 8.1. (Arcview 3.x and ArcInfo before that but, that was a long long time ago...)