I have noticed recently that our custom print services are no longer working from web apps that have been created by Web App Builder Developer Edition and published to the web server. If I access the web app from WAB, the print services work fine.
The error description says "Error executing tool. Export Web Map: Failed to create layer from service at" then lists each service in the map. I unfortunately just stumbled on this error and do not know when it stopped working. Does anybody have any ideas?
Solved! Go to Solution.
Can I ask if you applied this patch:
If you're on 11.1 already then it's core code. Have a look here and see if there is any cross over?
Can I ask if you applied this patch:
If you're on 11.1 already then it's core code. Have a look here and see if there is any cross over?
Hi @cdevault_pickett ,
I will tell you my take on this topic.
There is a BUG with Esri regarding this issue. We are told that they could not reproduce the Issue.
But Esri Germany could. We are therefor questioning how the Esri INC is testing the Enterprise Rollouts or reported BUGs. But that isn't helping you.
We have the same Problem in our 10.8.1 Enterprise Environment.
If you are using Enterprise Environment and therefor also Referenced Services it is most likely that you will experience this BUG.
There could be a workaround which we are testing.
Workaround:
1. Go to Service in Portal and set it up to Public.
2. then open the map with only this service.
3. Print something with Layers activated in Map.
4. Change the Shared Service Setting from Public to what it was.
What we are testing is that this workaround is maybe Session based. Meaning it works as long as you have an active session in your browser.
After clearing Cache the Problem should reaper.
That is my latest take.
Esri did put out another Portal Security Patch for 10.9.1 and 10.8.1 and is marked with additional B letter. But this BUG isn't addressed there.
I do not know if Esri is aware that the workaround which I have to give to my 600 Users is make a screen shot.
I will stop here with my comments.
Hope this clarifies for you this topic.
Br
Goran
This is EXACTLY the issue we're having in multiple 11.2 environments. Your workaround is the only way we're able to get it to work. Did you ever find any permanent solutions to your issue? Or just still using the workaround?
I thought our deployment was all patched up, but I just checked again and the custom print service patch is not installed. I'll make that a priority and report back.
Our custom print services just started working on their own between last Tuesday and Saturday. I tested them just before installing the patches and they worked fine. However I still installed on patches and custom print services are still working.