Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Feb 9, 2024 3:07:18 AM
Aug 9, 2021 5:54:06 AM
Qlik NPrinting tasks connecting to QlikView look stuck in Running status. The task manager on the Engine nodes shows some Qv.exe processes running, but the RAM and CPU usage does not change.
The Qlik NPrinting Engine needs to open QlikView Desktop in the background to communicate with the source QVWs during the generation of the reports in the tasks. These Qv.exe processes can be seen in the task manager under the Detail tab.
At times, the QlikView process may not terminate correctly or may simply not send the needed information to Qlik NPrinting. Therefore the report creation can't proceed and the tasks remain in Running status without progress.
You can configure Qlik NPrinting to monitor the status of the Qv.exe process and terminate it if it remains stuck. A new Qv.exe process will automatically open to replace the closed one.
<!-- <add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" /> -->
<add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" />
This configures the behavior of how the navigator will monitor the qv.exe process for potential infinite loops or waits.
Disabled, the value would read: 0:10000:15:0.0005
The value is composed by four numbers, three ints and one double, separated by colons (:). Values can be omitted, i.e.: 20:::0.2
Are there any specific steps that would be relevant for an AWS NPrinting migration? This setting used to work for killing idle QV.exe processes in the past, but no longer functions correctly after migrating to an AWS server. I double checked that this line of code is still uncommented out in the scheduler.config file, but it seems like there's some permission or security feature that needs to be enabled or disabled to allow these idle processes to be killed.
Current version we're operating on if needed:
Qlik NPrinting May 2022 SR3
Version: 22.15.11.0
Hello @ktgipson
I noticed you had logged a ticket for this, which, in this case, looks to be the right way forward, as there are no known restrictions with AWS and this setting.
All the best,
Sonja
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.
Hey there @Sonja_Bauernfeind ,
Just a couple of questions:
Many thanks,
Riccardo
Hello @rzenere_avvale
Thank you for reaching out! I have updated the article with additional information, hope this helps.
Though, no, you do not need to modify these values, the ones presented in this article will work just fine.
All the best,
Sonja
Thanks @Sonja_Bauernfeind, it's much clearer now!
Riccardo
Anytime!