I have a cached tiled map service hosted in our standalone ArcGIS Server 10.9.1 environment being displayed in a web application for public use. This web application contains the print widget which uses a "custom" print service also hosted in our standalone ArcGIS Server 10.9.1 environment.
As of recently, a few users have been mentioned that when attempting to print a PDF containing this cached tiled map service (with the service visible), the returned PDF from the print service does not show the appropriate layer (the layer is not visible in the PDF, but visible in the web application). Attempting to replicate the issue, I found that the issue is VERY intermittent and not specific to any web browser (replicated on Edge, Firefox, and Chrome). Looking at the server logs, I found the following errors for this specific cached tiled map service.
- Method failed.HRESULT = 0x80004005 : Unspecified error .
- Missing parameter: MapName
I am unfamiliar with this issue and error log. Has anyone else experienced this issue before?
Have you ever tried to use the same service as a standard service instead of a tiled mapservice?
I used to use a tiled mapservice, but I found that ESRI made big improvements in performance so it was no longer necessary. This will depend on how complex your mapservice is though.
Yes, I have tried using the service as a standard service, but unfortunately since the data being visualized is 1ft contours for a whole county, this solution doesn't work very well; the performance of the standard service version is VERY poor (almost unusable). The cached tile service is the only reliable way to provide this information quickly for any map extent.
How about scale dependency on that contour layer? Do you allow endusers to visualize the contours at all scales?
Do you have multiple sets of contours where at smallest scales you could have 10 ft contours, medium scales 2 or 5 ft contours and then at the largest scales you would have 1 ft contours?
The service as it stands does not allow the end user to visualize the data at all scales. We do not have multiple sets of contours, just the 1ft contours. This could potentially be a solution to use the standard service, but I am still looking for any insight regarding the error messaging / log file from ArcGIS Server. The error code/text is fairly generic and any googling I have done has not been very helpful.
@KevinPiraino2 Is the tile cache service Dynamic or Shared?
@GlenEsriUK The service uses Dedicated instances and caching is from a tile cache stored on a file server. This service was also published using ArcGIS Pro.
@KevinPiraino2 Have you seen this? Problem: Printing Cached Map Results in Blank Output
@GlenEsriUK I have not seen this article before. Looking into the details of the article and comparing other cached tile services we have published (that are not experiencing this issue), this "Dynamic Layers" setting is enabled for these other services. Not sure if it matters, but the other services were originally published with ArcMap (and upgrade to the ArcGIS Pro runtime through AGS manager), while the service with the issue was originally published from ArcGIS Pro.
One thing I have noticed when comparing the service with the issue vs. other similar cached tile services, the service with the issue does not have a fully populated "caching" page. I believe this information is populated from one of the "config" files (conf.xml, conf.cdi, conf.properties), but its unclear if these are the issue or not.
Does the error message log in the log file provide any information? The "Missing parameter: MapName" is throwing me for a loop.