Qlik Nprinting failing to generate report

[TusharDev_Qlik]

We are using Qlik Nprinting to connect to Qlikview and generate Nprinting reports.
From last few days the NP user is creating 15-16  QlikView sessions for a single user causing Qlikview server to stuck(RAM around 85%) and not generate any reports. We have tried restarting QV services in order to release RAM and tried to run again after restarting all component involved but still we are getting the same error. The Nprinting publish task is stuck at "Starting content resolution" step only.
Kindly advise steps to troubleshoot this critical issue.

[Frank_S]

If you added CPU processes, this would account for any new/additional CPU processes.

Finetuning and preparing your NPrinting 19+ Deploy... - Qlik Community - 1716222

If things are getting stuck, this can happen for several reasons.

1. Unsupported items in the QVWs  - Unsupported QlikView Document item... - Qlik Community - 1714896

2. Sharing the NP engine service user account with other QlikView or NPrinting servers. Dedicated NPrinting Server & Engine Service Accoun... - Qlik Community - 1716056

3. It is not clear by your comments however, you may have upgraded QlikView to the 12. 8 track without upgrading NPrinting to the corresponding supported version. See QlikView May 2023 Compatibility with NPrinting - Qlik Community - 2076472

Kind regards,

[TusharDev_Qlik]

@Frank_S 

There has been no change in the Qlikview and Nprinting setup and its been running since few years now.

We run this report monthly for 300+ users and it is throwing error today only.

Engine log has below error recorded.

Navigator navigator process died or has been terminated and can't be used anymore to resolve requests

[Cascader]

How do you call Nprinting from Qlikview? using APi calls?

do you reload qlikview appilcation too frequent? so some tasks get duplicated in Nprinting? 

[TusharDev_Qlik]

@Cascader 

we have publish task created on Nprinting which is scheduled to run daily.

a single report is used to generate all the reports by applying user level filters.

[Frank_S · Accepted solution]

I urge you to check for unsupported items as already mentioned.

In a Qlik Support case this is the first thing they will ask you to do. So you can save a step by check your QVWs today.

https://community.qlik.com/t5/Official-Support-Articles/Qlik-NPrinting-Unsupported-QlikView-Document...

This is commonly seen issue for many years. It is likely that you are seeing it now:

• developers may add these items later or
• they simply cause this issue even if these unsupported items existed previously

Spoiler

Note: Alternate states, sheet & document triggers, 'Always one selected' list and multi-box properties are the most commonly found causes for connection issues and reporting problems and any other unexpected results.

You need to thoroughly review the article and each point therein.

If you find no unsupported items, then please start a support case.

Kind regards...