Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Nov 15, 2023 5:16:58 AM
Aug 28, 2018 3:44:59 AM
Description of Property "force-unused-resolvers-closure-policy":
*NOTE: The term 'Large' is relative to the amount of RAM on your NP server. If low Ram like 64 or 128 GB RAM, then 1 GB QVW is 'large' since it may grow as large as 10 GB in memory. Then if you have 8 cores, it will open 16 processes each potentially with 10 GB each since NPrinting will use every core process by default to generate a single report. (https://help.qlik.com/en-US/nprinting/February2019/Content/NPrinting/DeployingQVNprinting/Performanc...)
Qlik NPrinting June 2018 or higher. Do not apply to previous versions.
NOTE: Please ensure to back up the scheduler.config file before proceeding
Note: Config file changes are overwritten upon upgrading NPrinting. Please apply these changes again after upgrading if the issues persist.
We recommend to follow this article in case the problem persists.
I was having an issue with the below error in nPrinting when using Pixel Perfect and Qlikview data. For large reports (500 pages +) I sometimes was getting the objects hanging and the below error in the nPrinting engine log:
Navigator stuck or died on connection navigator=qlikview;documentpath="", forcing close of resolver. 3 unprocessed request(s) will be reenqueued. ERROR: Qlik.Reporting.Engine.Messages.Exceptions.NavigatorDiedException
I implemented this change and
based on Qlik support feedback and they have resolved the issue.