Nprinting Sep 19 - QVP - QlikView Server Stuck - Report Running

[infosense_devel]

Sorry Message got change automatically below is the correct/Updated One.

We are at Nprinting Sep 19 version.

Using QVP Connection of QlikView Server, after some report generation server got stuck.

QlikView and Nprinting Server resources(CPU/RAM) is ideal and Nprinting task says running but it is not generating anything.

once I restart the QlikView Server everything work fine for few reports then again same problem. Also i'm seeing lots of active session on QlikView Server QMC with the same user while Nprinting is generating the report as per attached screenshot.

Thanks in Advance...!

[Lech_Miszkiewicz]

so...

• migrating from NPrinting 16 to NPrinting 2019 - it is indeed one by one process - full stop! https://help.qlik.com/en-US/nprinting/September2019/Content/NPrinting/AdministeringQVNprinting/Impor...
• migrating individual reports between lets say NPrinting 2019 (Dev server) to NPrinting 2019 (Prod Server)
  • you can do it also report by report https://help.qlik.com/en-US/nprinting/September2019/Content/NPrinting/AdministeringQVNprinting/Impor...
  • or you can migrate whole site (from dev to prod) as long as it is exactly the same version. It will effectively overwrite everything in Prod with whatever you have in dev. This process is well described in help.qlik.com https://help.qlik.com/en-US/nprinting/September2019/Content/NPrinting/DeployingQVNprinting/Backup-re...

Thats it - there are no other ways.

NPrinting deployment requires kowledge and needs to be planned by experienced NPrinting developer, so to avoid surprises i suggest you consult this with someone who is well experienced with NPrinitng or you may need to spend a lot more time by doing "double work".

cheers

Lech

[infosense_devel]

Sorry @Lech_Miszkiewicz  some how message got changed, can you please see updated one.

[Lech_Miszkiewicz]

Hi,

It is now very confusing as you have also changed title of the question and my answer is out of context completely!

Down to your problem with Stuck report:

• you need to investigate logs - this is to identify the moment where it gets stuck. Make sure you turn on DEBUG level so enough information is gathered. How to collect logs? --> go to https://help.qlik.com and search
• also I see 13 NPrinitng sessions - which indicates that you may have more than 12 CPU cores on NPrinitng machine, which is then not optimal or recommended configuration. What is your NPrinting server hardware
• is your qlikview document supported? check on https://help.qlik.com  for unsupported configurations of QlikView documents (always one selected value etc....)

lets focus on the above first... 

then we could move on to the optimisation like:

• all objects minimised
• set analysis instead of IF statements
• object calculation condition to allow for faster calc times etc...