Hi, I'm trying to use the print widget but it fails with the error message failed to create layer from service at http....../..../.../....etc. doesn;'t matter the page size or format, it always fails.
I'm using webAppBuilder 2.11 on our dev server and using locallayer to bring in layers from ArcGIS Server 10.6 via a published mxd.
Assuming the print service is an out of the box solution, what else can I look at? I've looked at the setting on ArcGIS server, I've also tried logging onto our server loading up the map and printing directly from there with no luck. I've really hit a brick wall here and everything I've tried does not work.
Does anyone have any ideas on where I could try looking next? Thanks.
Yes we have Portal too. I upgraded to 10.8 over the weekend. The map services and custom print service all reside on the same server which is federated with the Portal. Everything appears to be configured correctly and I can print webmaps without secured services. What is the easiest way to check to see if the webmap_as_json contains tokens?
What is the easiest way to check to see if the webmap_as_json contains tokens?
1. what kind of security you?
2. was it working before you upgrade to 10.8?
It doesn’t appear that the Web_Map_as_JSON request contains tokens.
Security is SAML through the Portal. I “think” this was working before the upgrade to 10.8 but honestly hadn’t looked in awhile.
I'm not at all familiar with SAML. Let me check to find more information on that.
In the meantime, please read the following help topic and see whether it helps you anyway in your situation.
The security on the GIS server is managed by Portal and the Portal security is Enterprise Login via SAML using an identity provider. The GIS server is federated with the Portal and hosts the map services and the custom print service. The Authentication Tier for the Server is the ARCGIS_PORTAL not through the web adapter on the server. From what I can tell everything is configured as described in the link above.
Nate Sylvester - One issue that trips people up with SAML is if they sign into the Server’s services directly (via the REST directory or Server Manager), then a cookie is created that gives them access to the server. When you then load an app it doesn’t know about this cookie and the service appears to be public, so it doesn’t generate a token for it. So one way to check for this is to see if the requests to the service in the app include token parameters or not. Another way to check is to clear the browser cache and then try to print in the app, or I suppose you could try in Incognito Mode if available.