composite locator issue

MikkelHylden

I have a composite locator that uses two address lookups, and a single field lookup against a custom intersection table the customer has created.  All of the searches work individually, and they cascade through correctly when I run the locator in ArcMap.  

When I use the locator in an app we have that runs in the .Net SDK, however, I get the following very generic error:

Error initializing locator services: One or more of the locator's properties is invalid

I would think that if the properties were invalid, they would also be invalid in the ArcMap version.  Has anyone seen this or something like it?

Thanks

MikkelHylden

A colleague was able to point out that there is an additional step I was missing.  After creating the locator, I had to use the File -> Share As and drill down to share the locator as a runtime output.  

 

Now I have it running, but it behaves differently in the runtime than it does in ArcMap, in that the search must be more specific in runtime.  I'm not sure why this is the case yet, but looking at possible places where the search sensitivity may have been overridden.