Unable to create view layers from hosted feature layers in ArcGIS Enterprise 11.1 (HA deployment). I saw this thread related to same issue in AGOL: https://community.esri.com/t5/arcgis-online-questions/why-isn-t-create-view-layer-working-for-some/m.... However there are no such issues with metadata in the services I am testing. Anyone got any experience with such a situation in enterprise?
Thanks Thomas
Solved! Go to Solution.
Apparently this was down to some permissions to a folder in gis server for the arcgis service account. This article helped to identify and fix it: https://support.esri.com/en-us/knowledge-base/error-error-001369-failed-to-create-the-service-000016...
The arcgis service account did not seems to have full access to the C:\arcgisserver folder. Once that was granted and restarted the gis server machine it seems the view layer is created.
There was a related issue with publishing hosted scene layers from the same portal via ArcPro. Apparently these were related issues and that also got fixed. Double winner 🙂
Thanks all
Thomas
Hard to know why it would fail. I get errors related to views now and again, and it's rarely the same issue twice.
When you go to create the view layer, have your browser's developer tools open and watch the network traffic. There should be a POST request that is sent when you click the button to create the view. The response to that request ought to give you more information about why it fails.
Yarg. Not helpful at all. Anything in your Server logs? I'm afraid I am otherwise out of ideas.
Apparently this was down to some permissions to a folder in gis server for the arcgis service account. This article helped to identify and fix it: https://support.esri.com/en-us/knowledge-base/error-error-001369-failed-to-create-the-service-000016...
The arcgis service account did not seems to have full access to the C:\arcgisserver folder. Once that was granted and restarted the gis server machine it seems the view layer is created.
There was a related issue with publishing hosted scene layers from the same portal via ArcPro. Apparently these were related issues and that also got fixed. Double winner 🙂
Thanks all
Thomas