0

I have a custom locator that I built with the Create Locator tool (type: Street Address) in ArcGIS Pro that works perfectly in Pro using the Locate tool — it returns accurate candidates based on input addresses. But, after publishing the locator to our standalone ArcGIS Server (not federated with Portal), the FindAddressCandidates operation via the REST endpoint returns no results, regardless of the input.

Locator Details:

* The locator references data from an Oracle enterprise geodatabase.

* During publishing, the data was copied to the server.

* The published service returns no candidates and no errors — just empty responses.

* The exact same input returns matches when tested in Pro.

Environment Details:

* ArcGIS Pro version: 3.4

* ArcGIS Server version: 11.4

* ArcGIS Server type: Standalone, Advanced license

* Oracle database:  12c, Standalone

* Locator role: Street Address, built using the modern Create Locator tool

* Server is not federated with Portal

* Data Store locator is built off of is registered with ArcGIS Server

* Valid publisher .ags connection used in Pro

Suspected Cause (from ChatGPT):

* The issue may stem from the locator failing to properly access or resolve the copied Oracle-based data in the server environment. This could be due to:

   * Incorrectly copied data that breaks the locator’s reference path

   * Missing or misconfigured database connection on the server

   * A limitation or bug when publishing locators that use enterprise data sources

Does anyone have an suggestions on what exactly might be happening and how to fix it?

Improve this question
1
  • It could be the way that you are invoking the locator. What operation on the geocoder is being used via REST call? I.e. findAddressCandidates, reverseGeocode, or geocodeAddresses. Commented May 21 at 12:27

0

Reset to default

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.