This article describes the analysis steps that should be carried out in the event of installation and printing problems with the VertiGIS Studio Printing Engine.
Problems during installation
The VertiGIS Studio Printing Engine is installed and updated via a Post Installer. The Post Installer creates a service definition file (SD file), which is then uploaded to the ArcGIS Server.
Installation instructions for the VertiGIS Studio Printing Engine can be found in our documentation:
Install VertiGIS Studio Printing Engine
Important: The following scenario is not supported: If the Portal for ArcGIS is configured with the Integrated Windows Authentication (IWA) authentication method and anonymous authentication is disabled on the Web Adaptor of Portal in IIS. |
Please check the following points if the installation of the VertiGIS Studio Printing Engine fails:
- Check the Post Installer log file to see which error message you receive. You can save the Post Installer log file directly:
- Please check the log file of the Post Installer to see whether an SD file has been created.
- If so, you can upload this SD file manually via the ArcGIS Server Manager.
- If not, you can also carry out the installation via the command prompt (cmd).
Hint: You can find more information on these processes in the following article: |
- If the installation was successful, but you cannot see or activate the ArcGIS Pro Layout Mode in VertiGIS Printing Designer, please follow the steps in the following article:
Unable to Toggle ArcGIS Pro Layout Mode in Print Designer After Installing VertiGIS Studio Print Engine
Problems with the printing process
The VertiGIS Studio Printing Engine creates a JobID for each request. A directory is created with this JobID and each of these directories contains a scratch directory. This scratch directory contains important information (log file, APRX file, JSON files, etc.) about the executed printout. The directory with the JobID is located under the following path by default: "...\arcgisserver\directories\arcgisjobs\vertigis_utilities\vertigis_printing_tools_gpserver\<JobID>".
Note: These created directories are automatically emptied and deleted after some time. |
If you receive an error when printing from VertiGIS Studio Web with the VertiGIS Studio Printing Engine, please check the following points:
1. Check the log file in the Scratch directory to see which error message can be found there.
- Check whether the printout works in an incognito window in the browser.
Hint: For secured map services, please check whether a valid token is present in the following file “..._PARAM_web_map_as_json.json”. |
2. Check whether printing the affected web map in the Map Viewer of ArcGIS Online or ArcGIS Enterprise works.
- Check whether the GP service PrintingTools (Utilities > PrintingTools), which is installed by default with the ArcGIS Server, is started in your ArcGIS Server Manager.
- If printing in the Map Viewer does not work either, please look in the browser console in the Network tab to see which error message is logged in the Execute request.
Note: If printing in the Map Viewer does also not work, this means that there is most likely an error on the Esri side. Possible causes and solutions can be found in the following Esri article: |
3. Check whether the print request from VertiGIS Studio Web works with the standard GP service PrintingTools on the REST interface.
- You will find the following file “..._PARAM_web_map_as_json.json” in the Scratch directory. Open this file in a text editor and copy out the content. Open the REST interface of the PrintingTools and execute the “Export Web Map Task”. Paste the previously copied content into the “Web Map As JSON:” parameter and execute the task.
Important information (VMware Tools Version 12.5): Version 12.5 of the VMware Tools software (Broadcom) causes ArcSOC processes to crash. This causes problems with the VertiGIS Studio Printing Engine. Please note the following information from Esri: |
Comments
0 comments
Please sign in to leave a comment.