...I have a composite locator build on 7 single locators, all address points. Each of the single locators breaks down an address point dataset by the first two digits of the zip code and then a query is applied in the composite to point the input to the right single locator. The goal is to reduce the search from 8 million points down to something more reasonable and generally works well.
The composite works and geocodes fine including the locator output field which is attributed with the correct single locator.
All of a sudden, I can't run my datasets on the singles. They were working fine the other day. I am having some issues with SP2 and just reinstalled from the website along with the geocode patch for composite memory leaks.
The really quirky thing also is that I can't run my datasets on a single streets locator either (dual range), same error. But I can run my single zip code locators.
This is all on the same input dataset. It will geocode on the composite but not the singles (except zips). I have tried removing nulls where some address parts are missing and I have left them.
However a different dataset will geocode on everything, no problem. I've been using my problem datasets fine for weeks.
I've gone back and recreated everything fresh twice now. It's not rocket science.
Sorry to sound so confusing but welcome to my world. I can't make this stuff up.
To summarize:
How can a dataset (with or without nulls) geocode through a composite okay, but none of the particpating single locators, NOR geocode through a single streets locator, BUT will geocode through a single zip locator?
