[GIS] Geocodes fails when published to ArcGIS Server

arcgis-serverarcmapgeocoding

I have a composite address locator that was built using our streets line file and our address points that works great in ArcMap 10.1 sp1. But when published to ArcGIS Server (10.1 sp1) no results are ever returned, whether in a REST environment or within a map service. I've gone through the esri help files and it doesn't appear that I am doing anything wrong. (This is the first time I've ever published one out.)

Has anyone else had this problem, and if so, how did you fix it?

Is it due to it being a composite?

As a side note, I did publish out the individual address locators and those too didn't work.

Best Answer

If you're publishing a composite locator to ArcGIS Server 10.1, I understand that this is always copied (regardless of datastore setup). The composite locator is just a pointer, so the copy time should be trivial. That said, I'd still setup a datastore folder entry for your locator. If the locator is on the Server, great, just reference the folder. If its not, share it as a UNC path and reference that. (though UNC takes a performance hit...thats another story). [or if its a small bunch of locators, maybe you want to copy them, again thats up to you]

Once you have it started, I'd suggest trying it in ArcMap as thats the easiest to consume (move to REST once you know it works). Either use the Geocode Addresses tool with the Locator Service as input, or use the Geocode toolbar and point the input locator at your Geocode Service. If this doesnt work, it should give you more information on why it isn't working. If it does work, then move to REST and try there. Just a guess but the REST input might not be correct, thus not getting any good output.

Related Question