VGS Print Result has blank map and legend (on prem)
We are seeing issues with print outputs on premise. No map, no legend, etc. I am using the same services in a web map for the print that works in AGOL. The problem is in VGS Web (5.22.1) and the web traffic yields little information. The same print template in WAB on the same on premise env has no issues showing the map in the template, so something with VGS Web. Anything anyone can point me to start an investigation? I've tried sharing the web map publicly and that made no difference.
Using VGS Web 5.22.1, VGS Printing 5.19.0
-
Hey Ryan Kelley - this sounds like there may be some sort of security between the VSP server and the outside internet.
To me, this scenario implies an environment that involves a filtering of egress from your network. There's usually a forward proxy in this type of scenario. This type of network security is typical of any midsize+ organization.
A few things to check:
- in a browser (ideally on the VSP server), can you load the webmap and hit services from AGOL?
- are there any authentication challenges in this process?
In terms of the traffic, there are some logs we can peek at.
When printing we should see requests to https://apps.vertigisstudio.com/printing/service/job/run & wss://apps.vertigisstudio.com/printing/service/job/artifacts?ticket=<ticket>
In the wss messages tab there is a results which should contain a job log url eg: https://gcxo-apps-printing-prod-web-westus.azurewebsites.net/service/job/logs.html#logs?ticket=eyJhbGciOiJub25lIiwiemlwIjoiREVGIn0.q1ZKzs9TsqpWUimpLEhVslLyKi8JyUzOTi1xzs8rSc0rUdJRyspP8kwBSeUnFVvoJ1mYJxkYmRiYWRoamiSbplkaGZsbmCeaWwKZqYlGyUq1tQA.
The logs by default are filtered by topic - so you might not see much detail for a completed print job. We can ignore this filter and append &Topic=All to this URL to get a URL looking like:
https://server.domain.com/vertigisstudio/Printing/service/job/logs.html#logs?ticket=<ticket>&topic=AllThis should get you a full view of the print log output. In there, I imagine you'll probably see some failed requests to AGOL.
If this doesn't get you anywhere, I'd suggest working with our support team.
0 -
Hi Gareth - thanks for the tips on where to go with this. I played around some more with this.
If the map scale is 1:4,514 and using an ESRI basemap (topographic for example), the print output has the right features, including our agency dynamic services, which are public facing. The map scale of the print dialog puts it at 1:1,794. But, if I zoom out to even 1:18,056, which gives me print output scale of 1:7,176 it will often fail to draw any features from any layer. I have seen a few inconsistencies where features do draw in the map at that scale, but rarely for this scenario.
Map services used in the webmap:
Layer: Timber Harvest 2011 - 2020 (ID: 0) (usda.gov)
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
2 kommentarer