Printing in Chrome not working

Question

Hi all,

I'm using ArcGIS Enterprise 11.1 and frequently experience printing failures in Google Chrome. The issue occurs regularly, but clearing the Chrome cache temporarily resolves it until it happens again (after 1-2 days).

Error executing tool. Export Web Map Job ID: j755c2fb54053451aa9a361d866d7e530 : Failed to create layer from service at https://......./server/rest/services/....../MapServer. Failed to execute (Export Web Map).

This problem doesn't occur in Firefox. Has anyone encountered this issue or knows of a solution?

Thanks for your help!

Best,

MarcoPoetsch · Answer

Thanks, @ChrisUnderwood and @TimoT Here some additional findings: * Edge Browser: Printing works fine in Microsoft Edge * Basemap Issues: Occasionally, the basemap doesn't appear when printing (Chrome, Edge and Firefox). However, if I interact with the map (e.g., move or zoom) and try printing again, the basemap displays correctly. * Console Errors: When working with more complex maps and feature services in Chrome, I encounter these console messages: [esri.core.watchUtils] 🛑 DEPRECATED - Module: esri/core/watchUtils 🛠️ Replacement: esri/core/reactiveUtils :gear: Version: 4.24 [GroupMarkerNotSet(crbug.com/242999)!:A0002200AC430000] Automatic fallback to software WebGL has been deprecated. Please use the --enable-unsafe-swiftshader flag to opt in to lower security guarantees for trusted content. [.WebGL-0x512c0ecec600] GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels * WebGL Involvement: Are these console errors related to WebGL issues? Does the printing functionality in ArcGIS Enterprise rely on WebGL for rendering? * Deprecation Warning: Could the deprecated watchUtils module be contributing to the printing failures? * GPU Stall Messages: Are the GPU stall messages affecting the rendering pipeline necessary for printing?

TimoT · Answer

Hi @MarcoPoetsch,

You may be experiencing BUG-000135413

A known workaround for this bug is clearing the cache as you've done. This doesn't typically affect the average user unless they are often utilising the REST or Admin endpoints.

A lesser known workaround is creating a custom print service with valid Portal credentials embedded. However, you should understand the security implications before exploring this route.

ChrisUnderwood · Answer

Hello @MarcoPoetsch , it would be useful to know how Edge behaves for you in this scenario, eg like Chrome, or like Firefox, or indeed something different to both. If you press F12 in your browser you should see a Developers Console, that may show some error details you can add to this post. Otherwise, please check if your Browsers & ArcGIS Enterprise are patched up to date.