Portal Print Service Doesn't Work Unless Feature Service is Shared Publicly (Export Web Map Task error)

[RyanUthoff]

I'm having an issue with my Portal's print service (using the built in Print button in the web map). If a map contains a referenced feature service, the only way the print service will work is if the feature service is shared publicly. If the feature service has organization or owner level permissions, the print service will fail. I receive the following message when using the print service: "An error occurred while creating the printed map."

If I check the server logs, I receive the following error for the Utilities/PrintingTools.GPServer service:

Error executing tool. Export Web Map Task : Failed to create layer from service at <feature service URL>. 

Note that the feature service URL it provides in the URL is valid. I can copy and paste it in a browser and it takes me straight to the rest endpoint. The only way it works is if the feature service is shared publicly. Otherwise, it fails.

Here is what I have tried with no success:

• Share the PrintingTools service with the public.
• Make the referenced feature service (when not shared publicly) and PrintingTools service the same owner in Portal.
• Share the feature service and PrintingTools service with the same group in Portal.

None of that works and the only way it works is if the feature service is shared publicly.

We're using ArcGIS Enterprise 11.2.

I'm assuming this is not expected behavior, right? If not, does anyone have any issues on what the issue could be? Thank you!

UPDATE: I've made progress in determining the root cause of this issue. The PrintingTools service doesn't seem to like AD accounts. If I am logged in under a built-in Portal account and use the print service with a feature service not shared publicly, it works fine. However, if I am logged in under an AD account and attempt to use the print service with the same feature service (not shared publicly), it fails.

Second UPDATE: I initially thought it was an AD vs. built-in account issue. But I've ruled that out and realized that it's just a browser issue. Opening the map in an incognito tab or using another browser works..... I don't think it's ideal for users to have to completely clear their cookies and cache every time they want to use the print service (because this is happening to multiple people), but at least it's not completely broken.

[Juan_Toro-Killion]

I'm having an almost identical problem. I've also been working backwards by testing various things, like the original poster, to figure out what's going on. I've found out that if I don't try to print hosted feature services, the print service works fine. It's only when 1 or more hosted feature services are turned on in the map (WAB, EB, or Map Viewer) does the print task fail. I'm running 11.3 on Windows. Any comment on why there is no need for me or my users to clear cache when printing referenced/server feature services, but it's almost required when printing hosted (majority of our use cases)?

[SillPaul]

Did you get any resolution to this?  We are experiencing the same issue, on the similar platform (11.3, Windows).

[SillPaul]

I was able to resolve this issue by changing the sharing level on our Data Stores.

The data stores were shared with the creator (user) and a group that I'm a member of.

However, the "Error executing tool. Export Web Map Task : Failed to create layer from service at <feature service URL>" persisted until the Data Stores were shared with our Enterprise.