Insights for ArcGIS Something Went Wrong

[MichaelSchoelen]

Everything in our portal appears to be running fine (we can publish hosted feature services and apps), however Insights for ArcGIS suddenly started showing the message "Something Went Wrong" when creating a new workbook. 

Also getting an error message in Server Manager logs for "Failed to create data source..... NullPointerException"

Any ideas?

[JonathanQuinn]

Do you have an HA Data Store? If so, check the Admin API and see if the standby Data Store is listed first under the list of machines, (when viewing the JSON response of the Data Store. If it is, edit the item and move the primary Data Store above the standby machine and try again.

[MichaelSchoelen]

Yep, High Availability, and we recently had a failover event. 

Can you elaborate on the path to get that Json response?

…/server/admin > data > items > /enterpriseDatabases > …. ? Or somewhere else?

[JonathanQuinn · Accepted solution]

I don't have an HA Data Store in front of me right now, but the path should be:

https://server.domain.com:6443/arcgis/admin/data/items/enterpriseDatabases/AGSDataStore_ds_<id>?f=pj... 

There, you should see a "machines" list:

"machines": [{
    "name": "primary.domain.com",
    "adminURL": "https://primary.domain.com:2443/arcgis/datastoreadmin/",
    "dbPort": 9876,
    "platform": "Windows",
    "role": "PRIMARY"
    },{
   "name": "standby.domain.com",
   "adminURL": "https://standby.domain.com:2443/arcgis/datastoreadmin/",
   "dbPort": 9876,
   "platform": "Windows",
   "role": "STANDBY"
}]‍‍‍‍‍‍‍‍‍‍‍‍‍

If the standby machine is listed above the primary machine, edit the item, (append /edit after the AGSDataStore_ds_<id> part), and flip the machine information. This is something the Insights team is fixing.

[MichaelSchoelen]

That did the trick. As always, thanks Jonathan Quinn‌!!!

[JonathanQuinn]

Glad I could help!

[MichaelSchoelen]

Jonathan Quinn‌, was a formal bug ever assigned to this issue? We were hoping for a resolution at release 3.1.

[JonathanQuinn]

Unfortunately, it doesn't appear as though it'll be fixed in the next release.