Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
fionna51
Creator
Creator

NP19 performance is not stable, sometimes hanging for cycling reports

Hi all,

We are running NP19 with Qlikview 12. In current stage, we have around 400 external users, and user can have multiple cycled reports attached in same email. Our Qlikview app size is 40MB, and right after we rebooted NP server, ten users each have 10 PDF reports might take as fast as 3 minutes to run. However this is really not stable, sometimes even one user with one pdf report attached might take 3-13 hours. Or in worst case it was hanging and timeout after 16 hours.

There is no unsupported items in our QVW file, no calculated filters and no macros. The only special thing is some of our users have multiple cycled reports - 10 users have 17 reports each and this could never run successfully. All this could be run in old NP16, it was slow but not hanging.

Now we really couldn't find out the pattern after so many tests, all sounds random. Even we clean up all QV.exe, reboot server/service, it may still hanging. Do you guys have any idea or ever experienced same for NP19 FEB20?

Thanks a lot.

Labels (2)
1 Reply
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

There is still no clear picture as few very important factors are missing:

  • are you using QVP or Local connection
    • if QVP - what are the QV server stats and logs saying
    • if LOCAL - what is the usage of resources (RAM-CPU)
  • QV 12 is too generic as a version you mentioned. What is the exact version of QV server and QV local clients. Server and Local should be on the same version.
  • are all objects used in visualisations minimised as per best practices
  • 40 MB app can easily hang the server up if there is not optimal model (island tables, cross-joins, calculated dimensions, Sum(If(...)) formulas etc...

I can understand your frustrations, but to troubleshoot it I think we would need to look at your report, model, environment etc.. If you are not comfortable sharing your model here you may want to open support ticket with Qlik support.

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.