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

ArcMap crashes when geocoding after SP2 install

AndrewDecker

Incident #928557

I'm having persistent crashing (ESRI error message/instant disappearance) when geocoding in 10 SP2. I had some crashes before with 10SP1, but nothing like this. At least five times a day, five so far and it's only 11am. I can't make it crash and can't identify a dataset or environment setting that is causing it. It's crashing locally on my machine as well as on our virtual server. I didn't have problems before on our virtual server, but we put SP2 on day before yesterday and WHAM, crashola. I've moved my data and locators around in fresh geodatabases and made fresh map documents but that hasn't mattered. I have ArcInfo. I renamed, on the recommendation of ESRI support, the normal.mxt and the ESRI registry to reset default settings, but that didn't work, still crashed.

Like the tree said to the logger, I'm stumped.

Find more posts tagged with

Accepted answers

All comments

AprilNunn

I can confirm this bug with 10.0sp2. If you have a table to geocode that contains one or more null values in one of the input fields ArcMap (and geoprocessing scripts) will crash. The error appears to be intermittent/random. Eliminating the null records from the input data set is a workaround until the bug is fixed by esri. Note, applying the geocoding service patch for 10.0 sp2 does NOT fix the problem.

The same input data set runs fine using 9.3.1.

Thanks for the help, this is exactly what I've been running into. Now all I have to do is get the nulls out of another party's data...

BradNiemand

This is a known issue and it does have a fix but the fix is not in released software. It may make it into SP3 or SP4.

Brad

AJR

I can confirm this bug with 10.0sp2. If you have a table to geocode that contains one or more null values in one of the input fields ArcMap (and geoprocessing scripts) will crash. The error appears to be intermittent/random. Eliminating the null records from the input data set is a workaround until the bug is fixed by esri. Note, applying the geocoding service patch for 10.0 sp2 does NOT fix the problem.

The same input data set runs fine using 9.3.1.

WilliamCraft

I am using the Street_addresses.loc locator in ArcGIS Desktop 10 SP1. I see that address is a required field. When my input table contains a NULL value for the address field, the geocode operation fails and actually crashes in ArcMap. The locator was made in v10. This issue does not occur for earlier versions of the same locator.

@Brad Nieman from ESRI: is this a known issue and/or is there a fix for this?

AndrewDecker

Here are today's .dmp files.

ArcMap_10.0.2.3200_0_05_16_2011_14_54_23.zip

BradNiemand

We are looking into this issue but don't have anything as of now.

Brad

AndrewDecker

Here is the first error report of the day also....

This locator ran great for three runs and then crashed rerunning a previously successful dataset.

On this locator/crash, I had changed the run time memory limit to 1gb. But again, it ran fine and then didn't.

ArcMap_10.0.2.3200_0_05_13_2011_09_16_16.zip

AndrewDecker

1) I geocode off of the "street_address" fields, not "mailing_address"
2) Shouldn't the locator handle null values and simply not gain the scoring weights? I know there are sporadic missing values throughout the datasets.
3) I'm not positive what you mean by CA locator? The zip locators in my composite are from a statewide and a national dataset, both teleatlas (different years), both build on ZIP5 locators.
3a) Field mapping is simple with TA data. Address points where standardized using the tool, the streets come ready to geocode, zips are simple. I can send you my config spreadsheet. I left all the default input mappings for my purposes for now.
4) I've attached what dmp files I could
5) Like I said, they've worked and they haven't. Sometimes I can go all morning okay, sometimes three crashes in a row. The same dataset/locator will crash, and then immediately work. New mxd's, only one table added (the only layer) at a time, re-add the locator to the manager. I'm trying to keep it clean an simple.

ArcMap_10.0.2.3200_0_05_12_2011_14_46_19.zip

BradNiemand

Can you send me the crash dump from the following directory? It should have a date on it as well.

%appdata%\ESRI\ErrorReports

Brad

BradNiemand

I am not getting a crash but the table does fail to geocode when it gets to the record that has a <null> value in the Mailing_Address field.

Brad

BradNiemand

Do you create a California locator and what data do you use to create it? Also, what fields are you mapping when you create the locator?

Brad

AndrewDecker

I am testing a composite locator and several single locators. They were either created in 10SP1 or 10SP2, I've had both crash. A composite I built in SP2 does point to three singles built in SP1 but sometimes they work, sometimes they don't.

I am batch geocoding 10 stand-alone gdb tables (2 identical sets of five tables only one set is sorted), from 1k to 72k records. I cannot find a pattern to the locator/dataset. I am using the geocoding toolbar, not the toolbox.

I have attached a zip file with two of my tables. These have crashed and they haven't.

This is also happening on two machines. One is on XP (mine), the other is 2008.

Input_TestData_Sample.zip

BradNiemand

Are these locators that you created at 9.3, 10.0, 10.0 SP1, or at 10.0 SP2? Can you share your data so that I can take a look?

Also, what are you doing when it crashes? Are you batch geocoding, using the Find dialog, using the geocoding toolbar, reverse geocoding, etc...

Brad

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.