Survey123 Error: Failed to validate the server managed database
Tags: ArcGIS Server, Pooling, Survery123, Hosted Feature Services, ArcGIS Desktop, ArcMap.
I came across an interesting bug in ArcMap 10.6.1 today and thought I should share it with the community.
My client lost all connections to their survey123 surveys after setting pooling on an ArcGIS Server.
This was the errors that the client received
Portal UI:
ArcGIS Server UI:
just a blank screen
Poral logs:
<Msg time="2019-08-30T16:36:24,29" type="SEVERE" code="207047" source="Portal Admin" process="3952" thread="16" methodName="" machine="[my server name]" user="" elapsed="">Failed to update federated server '[my server name] (id: SmZlAFBzaRbJ0KA1)'. Failed to validate the server managed database '/enterpriseDatabases/AGSDataStore_ds_4927moek'.</Msg>
ArcGIS Server Logs:
<Msg time="2019-09-02T11:05:36,297" type="WARNING" code="9003" source="Rest" process="1564" thread="16" methodName="" machine="[my server name]" user="" elapsed="">Unable to process request. Service Hosted/service_6990198ab90942e28dfc646fa6834839/MapServer not found </Msg>
Trouble Shooting
after replicating the workflow on another server I noticed that the server JSON looked funny
Actual Erroneous JSON
{
"serviceName": "service_0d5061e6228d4e5a85301e3666919372",
"type": "FeatureServer",
"description": "",
"capabilities": "Query,Editing,Create,Update,Delete,Extract,Sync,Uploads",
"provider": "SDS",
"clusterName": "default",
"minInstancesPerNode": 1,
"maxInstancesPerNode": 2,
"instancesPerContainer": 1,
"maxWaitTime": 60,
"maxStartupTime": 300,
"maxIdleTime": 1800,
"maxUsageTime": 600,
"loadBalancing": "ROUND_ROBIN",
"isolationLevel": "HIGH",
"configuredState": "STARTED",
"recycleInterval": 24,
"recycleStartTime": "00:00",
"keepAliveInterval": -1,
"private": false,
"isDefault": false,
"maxUploadFileSize": 0,
"allowedUploadFileTypes": "",
"properties": {},
"portalProperties": {
"isHosted": true,
"portalItems": [{
"itemID": "ba880b7b91074eb68038d690ab9a7c4b",
"type": "FeatureServer"
}]
},
"extensions": [],
"frameworkProperties": {},
"datasets": []
}
Expected JSON
{
"serviceName": "service_0d5061e6228d4e5a85301e3666919372",
"type": "FeatureServer",
"description": "",
"capabilities": "Query,Editing,Create,Update,Delete,Extract,Sync",
"provider": "SDS",
"clusterName": "default",
"minInstancesPerNode": 1,
"maxInstancesPerNode": 2,
"instancesPerContainer": 1,
"maxWaitTime": 60,
"maxStartupTime": 300,
"maxIdleTime": 1800,
"maxUsageTime": 600,
"loadBalancing": "ROUND_ROBIN",
"isolationLevel": "HIGH",
"configuredState": "STARTED",
"recycleInterval": 24,
"recycleStartTime": "00:00",
"keepAliveInterval": -1,
"private": false,
"isDefault": false,
"maxUploadFileSize": 0,
"allowedUploadFileTypes": "",
"properties": {},
"jsonProperties": {
"adminServiceInfo": {
"status": "STARTED",
"name": "service_0d5061e6228d4e5a85301e3666919372",
"type": "FeatureServer",
"database": {"datasource": {"name": "/enterpriseDatabases/AGSDataStore_ds_smdosaso"}},
"serviceViews": [{
"name": "survey123_e8b9dff7626d43ebb8ee752f03e69ad2_stakeholder",
"serviceItemId": "603093eba1ce491aa1bf84b9b4a2f64b",
"type": "FeatureServer",
"refCount": 1
}]
},
"xssPreventionInfo": {
"xssPreventionEnabled": true,
"xssInputRule": "rejectInvalid",
"xssPreventionRule": "InputOnly"
},
"supportedQueryFormats": "JSON, geoJSON",
"allowGeometryUpdates": true,
"maxRecordCount": 1000,
"syncEnabled": true,
"copyrightText": "",
"enableZDefaults": false,
"serviceDescription": "Python_S123_Test2",
"description": "",
"currentVersion": 10.61,
"capabilities": "Query,Editing,Create,Update,Delete,Extract,Sync",
"hasVersionedData": false,
"editorTrackingInfo": {
"allowOthersToDelete": true,
"enableOwnershipAccessControl": false,
"enableEditorTracking": true,
"allowOthersToUpdate": true,
"allowOthersToQuery": true
},
...
Resolution
As it turns out that in ArcMap you can set the pooling for hosted features service and in the case of Surver123 services the JSON gets overwritten.
You don't get a warning or error it just execute even though there is no such option in ArcGIS Server Manager.
We restored a backup of the JSON and restarted the server and everything came back up.
I hope this helps.