Skip to main content
Announcements
Marching toward a simplified navigation! READ ON

Force Qlik NPrinting to automatically close idle QV.exe processes

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Force Qlik NPrinting to automatically close idle QV.exe processes

Last Update:

Feb 9, 2024 3:07:18 AM

Updated By:

Sonja_Bauernfeind

Created date:

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.

Resolution

  1. Stop the NPrinting services
  2. Open the file: 
    C:\Program Files\NPrintingServer\NPrinting\Scheduler\scheduler.config
  3. Look for the line:
    <!-- <add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" /> -->​
  4. Un-comment it as follow:
    <add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" />​
  5. Restart the NPrinting services.

 

What is the 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

  • The first value specifies the resolution, or how often we should collect information about the cpu usage of QlikView. It can go from 20 to 1000 milliseconds. 
  • The second value specifies the maximum time for which we should keep the collected values. It can go from 10000 to 600000 milliseconds and increased to allow the collection of at least 30 values.
  • The third value specifies the maximum time for which we should try to query the QlikView process and guess if it is stuck or alive. If before the timeout the process does not answer, it will be terminated. It can go from 1 to 1440 minutes.
  • The fourth value specifies the threshold under which the standard deviation calculated on the collected values will trigger the stuck check process.

 

Environment

 

 

Labels (1)
Comments
ktgipson
Contributor
Contributor

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. 

ktgipson
Contributor
Contributor

Current version we're operating on if needed:

Qlik NPrinting May 2022 SR3

Version: 22.15.11.0

Sonja_Bauernfeind
Digital Support
Digital Support

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 

 

ryan_byrne
Partner - Contributor II
Partner - Contributor II

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 

https://community.qlik.com/t5/Official-Support-Articles/How-to-remove-the-Idle-Connections-from-Npri...

based on Qlik support feedback and they have resolved the issue. 

 

rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Hey there @Sonja_Bauernfeind ,

Just a couple of questions:

  • what does represent the value '300:10000:15:0.0005'?
  • do we need to customize in any way this value?

Many thanks,
Riccardo

Sonja_Bauernfeind
Digital Support
Digital Support

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 

rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Thanks @Sonja_Bauernfeind, it's much clearer now!

Riccardo 

Sonja_Bauernfeind
Digital Support
Digital Support

Anytime! 

Version history
Last update:
3 weeks ago
Updated by: