We have multiple Enterprise deployments in version 11.1.
It is possible to share as web layer of 3D multipatch, raster tile layer from a DEM and elevation layer from DEM in one of such instance. However in an identical deployment, the share as web layer for 3D multipatch fails where as raster and elevation layer from DEM works.
The only option is to create a slpk file and then upload directly to the portal, however the hosted feature service is then not created.
Any suggestion how to resolve this?
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 creating view layers from hosted feature layers. Apparently these were related issues and that also got fixed.
Thomas
did it give you any error messages?
Hi @BillFox
Except the one shown in the screenshot, nothing else
might not match what you see but does anything in this knowledge base help?
Have you checked the health of your ArcGIS Datastore tilecache?
https://support.esri.com/en-us/knowledge-base/how-to-validate-arcgis-data-store-000022348
Use the "Validate via JSON in the ArcGIS Server admin endpoint" method as it provides more information. You'll find your tilecache datastore under "nosqlDatabases".
@A_Wyn_Jones The validation option you suggested seems only works for relational datastores. I have validated the datastores via gis server admin end point and seems healthy.
Hmm - yes it does seem healthy.
Are you running a early windows server version which may need this workaround applied? https://support.esri.com/en-us/knowledge-base/error-001812-unable-to-connect-to-the-database-used-fo...
Check this article out too, essentially need to make sure the Service accounts trusted sites include your machine name and Friendly Alias:
Thanks @A_Wyn_Jones This was originally done to enable the scene layers to publish (as slpk) from contents in the portal (without that the error was : error 001887: failed to create couchdb database.
The issue now is more of just not been able to publish the 3D layers from pro directly where as the raster tile works fine.
The env I am testing is identical to the working env: in terms of windows / network etc (all in Azure)
We do not use web adaptors: just application gateway linked to the portal / gi servers
does the .eslpk option work for you?
Yes the SLPK option worked always. But then there is no option to edit the hosted scene layer (features)?