Nprinting report stuck in starting resolution

[helenalopez93]

Hi all,

I am currently using Qlik NPrinting February 2020 SR1 Version: 20.0.3.0, and I want to apply a Cycle for a field named: User, that has approximately 120 possible values.

When I execute the full report, it gets stuck in step:

Starting content resolution for report d7d17271-6529-43f6-a1e7-667d7c63fcd

When I filter the report to only 10 possible values, it executes successfully, log below:

20200806123817 Info Starting content resolution for report d7d17271-6529-43f6-a1e7-667d7c63fcd8
20200806123915 Info Finished content resolution for report d7d17271-6529-43f6-a1e7-667d7c63fcd8
20200806123915 Info Starting content production
20200806123921 Info Finished content production
20200806123921 Info Starting publishing for task 4f91e4eb-2f0e-4edb-b083-c767760ace71 report d7d17271-6529-43f6-a1e7-667d7c63fcd8 user 2caf5ae3-0232-4ffe-a4d9-3e53fba5aaae file DR_DR_Usuario
20200806123921 Info Starting publishing for task 4f91e4eb-2f0e-4edb-b083-c767760ace71 report d7d17271-6529-43f6-a1e7-667d7c63fcd8 user b88487b9-3e79-4ddf-b9ab-cbe4aa160c3f file DR_DR_Usuario
20200806123921 Info Finished publishing for task 4f91e4eb-2f0e-4edb-b083-c767760ace71 report d7d17271-6529-43f6-a1e7-667d7c63fcd8 user 2caf5ae3-0232-4ffe-a4d9-3e53fba5aaae file DR_DR_Usuario
20200806123921 Info Plan branch execution completed
20200806123925 Info Finished publishing for task 4f91e4eb-2f0e-4edb-b083-c767760ace71 report d7d17271-6529-43f6-a1e7-667d7c63fcd8 user b88487b9-3e79-4ddf-b9ab-cbe4aa160c3f file DR_DR_Usuario
20200806123925 Info Plan branch execution completed

I have changed the QlikView.config to have a longer  time out:

 <timeout initial="3600" minimum="3000" maximum="4000" />

However, even as I filter to only 20 users, the process still gets stuck in the content resolution phase and keeps running indefinitely.

What are yout thoughts?

Best regards,

Helena

[Frank_S]

If you are still experiencing the issue, check the points in the following article:

https://community.qlik.com/t5/Support-Knowledge-Base/How-to-resolve-NPrinting-verification-errors-Pu...

[Lech_Miszkiewicz]

Since it works for smaller amount of cycle values it indicates to me that the way QlikView application used for this report is not optimised for NPrinting. It has never been easy and many people assumed that they can just create report based on any application. The more complex your report gets the more visible issue with performance will be if you dont pay attention to how you have built your QlikView report in first place.

In the link below you have amongst other key points which should be taken into account - have you done all of them before building your NPrinitng report?

https://community.qlik.com/t5/Qlik-NPrinting-Discussions/QVW-size-limitations-with-NPrinting-17/m-p/...

principles are simple - you have to take into account what NPrinting needs to do to produce those reports (results of your cycles, levels, pages and filters which are all possible selections which will be applied on the app to check if they are possible at all before reports can be built). The faster those can be done the better performance, and bottleneck for that is usually in the QlikView application performance and not in NPrintning. 

Last note: It is important you have those settings done on your qvw document or overall generation time will be largely extended:

https://support.qlik.com/articles/000098313

hope this helps