Is This Content Helpful?
We're glad to know this article was helpful.
Rematching a geocoded feature class created with a composite locator does not work.
Selecting to automatically rematch the geocoded feature class immediately after geocoding causes the application to crash.
Selecting to interactively rematch the geocoded feature class immediately after geocoding returns an error dialog with the following message:
"There was an error processing candidates"
A known issue in ArcGIS causes paths to participating locators to be stored improperly in the geocoded feature class' metadata. This is caused when the composite locator used to create the geocoded feature class uses relative paths to refer to the locations of the participating locators. As a result, ArcGIS cannot find the composite locator's participating locators when rematching the geocoded feature class.
If it is not necessary for the composite address locator to use relative paths to refer to the locations of the participating locators, open the composite address locator's Properties dialog, and uncheck the 'Store relative path names' option before using it to geocode tables of addresses.
If a geocoded feature class has already been created using a composite address locator that uses relative paths, then repair the definition of the composite locator stored in the geocoded feature class' metadata.