ArcGIS Web AppBuilder
ArcGIS Spatial Analyst
Imagery and Remote Sensing
All Products Communities
Gas and Pipeline
State & Local Government
Roads and Highways
AEC (Architecture, Engineering and Construction)
All Industries Communities
ArcGIS Runtime SDKs
ArcGIS API for Python
ArcGIS Pro SDK
Developers - General
ArcGIS API for Silverlight (Retired)
ArcGIS REST API
ArcGIS API for Flex (Retired)
ArcGIS Online Developers
ArcGIS for Windows Mobile (Retired)
All Developers Communities
Comunidad Esri Colombia - Ecuador - Panamá
ArcGIS Content - Esri Nederland
Esri Italia Community
Swiss Geo Community
Rwanda Geospatial Forum
All Worldwide Communities
View All Communities
Community Help Documents
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Data Management Questions
Errors Using the World Geocode Service at ArcMap 1...
Subscribe to RSS Feed
Mark Topic as New
Mark Topic as Read
Float this Topic for Current User
Printer Friendly Page
Errors Using the World Geocode Service at ArcMap 10.1
03-10-2014 11:13 AM
Occasional Contributor II
Mark as New
Subscribe to RSS Feed
Email to a Friend
Report Inappropriate Content
I'm having a hard time getting the World Geocode Service to 'stick' in ArcMap 10.1.
When you click the "Find" button, you are immediately prompted with this dialogue:
When you yes or no, the dialogue pops up again.
Finally, you can go to the Find tool, click the "Locations" button, and browse to the new World Geocode service...
But... when you select the World Geocode service, you get the error again...
I can then do a geocode, etc. no problem.
When finished, I close ArcMap, assuming the new geocoder will be remembered.
But... when I open up ArcMap again, the first thing that comes up (before the ArcGIS splash screen) is the Damaged Locator error - *
I click the Find button, and the error still pops up, same process as noted above, and the locator was not kept in the list of Locators.
I know this is fixed at 10.2, but our organization just moved to 10.1 after many years of not upgrading from 9.3.1...
Any thoughts appreciated.