We are attempting to design & confirm a configuration of ArcGIS Enterprise (single machine deployment) that can be used to provide core services (basemaps, geometry service, geocoding etc) in an active-passive configuration. The current design is two single-machine deployments of ArcGIS Enterprise behind a third party network load balancer.
Both virtual machines in the active-passive configuration are identical and from a user/client perspective, the above configuration provides a seemless SSO experience through the NLB to both VM's. Using the webgisdr workflow to migrate changes from active to passive, we encountered an issue on importing the webgisdr site.
Failed to get SHARED_LOCATION property in "webgisdr file". Malformed \uxxxx encoding.
Any ideas? The only discrepancy I can see from the documented workflow here is that we have not altered the hosts file. Our justification for using this workflow is to migrate ad-hoc changes to our core services offering, upgrade underlying operating systems and reduce 'in place' ArcGIS Enterprise upgrades. Perhaps there is an alternative?
Yes, all single backslashes should be escaped, but I've never seen that type of error before.
What program are you using to edit the file? I don't think there's any other encoding/characters for a backslash, like there is for an apostrophe, (' vs ‘). What locale are you on?
Unfortunately we are using notepad to edit the file, but that's a good line of questioning.
Our local is English (Australia).
As an FYI, the portal logs (debug) show no records which highlight that this error is occuring within the actual webgisdr executable logic rather than after the GIS is contacted by the tool via the REST api.
So you were able to export from your original site, what happens if you move that properties file over to your new environment, and just update the URL and credentials? Even if the path is incorrect for the SHARED_LOCATION and BACKUP_LOCATION, leave it be and see if the DR tool can successfully read the path and validate it. It does sound like some sort of encoding problem:
Hello @JonathanQuinn !
Was there a solution for this Problem? We also have this issue.
Shared Location Property looks like this: SHARED_LOCATION=\\\\MYSHARE\\shared
Export is no Problem, but Import. Servers and File Share are on a Azure VM.
Thank you in Advance!