Nprinting task stuck at zero percent

[ali_hijazi]

Hello
I got a publish task that was working fine yesterday
today I run it again and it is stuck on 0% and there is not log written when I click the link of the task in Admin->Task Execution

what should I look for?
would restarting the Nprinting server solve the issue?

below is the status after 3 hours of running

[Frank_S · Accepted solution]

Do the following @ali_hijazi 

• Yes...restart the Nprinting server entirely.
• Also restart the Qlik Sense server as it very well could badly need a restart due to overuse during NPrinting report production and may not be responding to NP reporting task requests. NPrinting requires a healthy, responding Qlik Sense server to work normally.

If either above is resolves the issue, this may indicate that you may need to add RAM to your NPrinting Server (NP engine) and or your Qlik Sense (Virtual Proxy) server to handling increasing load in your environment.

If neither above work.

• Open the Nprinting report using the NPrinting Designer (ensure that the NP designer and NP server are the 'same' version and service release (SR). Does it open or do you get opening errors? If no errors go to next point below.
• Create a temporary 'filter' in the NP web console. This will ensure that you don't pull all available data into the report. Use something 'this week' or 'this month' or pick a specific company, department or something similar. Add this filter to the report and preview the report. Does it produce a report or is there an issue producing the report.

If one of the above is not working, then something has changed in your report and that is what you will need to investigate and roll back any changes made either to the report. Or adjust any changes made in your Qlik Sense app within your Nprinting report.

Kind regards...

[Lech_Miszkiewicz · Accepted solution]

Hi, 

Frank has given you quite good ideas. One more thing to add to it is that apps used with NPrinting should be optimized and most of the time poor app development is a root cause of server performance which then translates to issues like yours.

cheers

[ali_hijazi]

well yes
when I asked the team responsible for the Nprinting server to restart it they told me that memory is not full it was 7.5GB out of 15GB
the CPU wasn't that busy
everything is normal

it seems that app's schema needs optimization
also the app has data since 2015!!