In 10.2 we were able to save the geocoders in the geodatabase, publish them and then use python to update them without them being locked using a simple arcpy.RebuildAddressLocator_geocoding(in_address_locator). Now in 10.5, we have been forced to move them to a file location and now they have locks added to the mix. I agree there should be the option to not have the geocoding service lock the geocoders.
It would be nice to have a global option to never have your services lock the schema for any type of service so it doesn't have to be set for each service.
Ronnie Richards I found the best bypass for this is to publish as a Composite; then the underlying locators aren't locked once you stop the parent service.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.