Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Knowledge
Slow or Failed PDF Printing in QlikView in the AJAX Client
Article Number: 000063287 | Last Modified: 2019/01/29Description
An issue was reported involving slow or failed pdf printing in QlikView in the AJAX client.
Environment: QlikView 11.20
When the time to print to pdf took over 60 seconds, the process never completed and there was no error message shown to the user and none found in the logs. The export to excel for the same was completed in a reasonable time without error. Using the IE plug-in the print to pdf action was completed in a reasonable time without error. The issue was only present in the AJAX client.
Environment: QlikView 11.20
When the time to print to pdf took over 60 seconds, the process never completed and there was no error message shown to the user and none found in the logs. The export to excel for the same was completed in a reasonable time without error. Using the IE plug-in the print to pdf action was completed in a reasonable time without error. The issue was only present in the AJAX client.
The following settings were adjusted to attempt to correct this behavior with any positive affect to the pdf printing issue:
- “PDFPrintTimeoutInSeconds” in settings.ini - on Publisher Server
- “QVSTimeout” in config.xml - on AccessPoint Server
- “SessionCookieTimeout” in the config file of the web server
- “SocketTimeOutInSeconds” in IIS - on AccessPoint Server
- “Object Calculations Time Limit” - In QMC
Cause
This was reported as a bug but it was closed as working as designed. A rule of thumb of less than 200 pages for pdf was suggested by R&D when using Print Report in the AJAX client.
Resolution
There were bugs submitted for this issue in the past: QV-1151 and QV-8938. In these bugs, R&D noted that Qlik did not recommend trying to print over 200 pdf pages with QlikView as a best practice and these bugs were closed as working as designed.
However, a potential workaround was suggested. Instead of using "Print Report" , R&D recommended using the "Select Report" option for this scenario. There is a community post about this: Select report option as Button
However, a potential workaround was suggested. Instead of using "Print Report" , R&D recommended using the "Select Report" option for this scenario. There is a community post about this: Select report option as Button
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us