Hi there,
We are currently experiencing issues with long-running reports, inconsistent run times and reports that sometimes run "forever" in Nprinting and I'm hoping someone might be able to advise on what we can do to resolve this.
We currently have three reports that run in the mornings. Our Nprinting server is a Windows Server 2012 server that is running reports on our Qlikview server cluster (we have two nodes in our cluster). We're currently pointing the reports at a specific node.
We're finding that our reports are extremely inconsistent, but that the run-times seem to be increasing over time. When they first started running,the two smaller reports took 15 minutes, and the larger one took 30 minutes. Now the reports are sometimes taking over 2 hours to complete. The run time for one of the smaller reports over the past few days: 1hr 11 minutes, 2hr 20 minutes, 2hr 10 minutes, 1hr 4 minutes, 35 minutes. We find at times also that if a report is never finishing and we change the setup of the report to use the other node in our cluster, the initial run on the other node is significantly faster but it then also slows down over time.
Today the report is still running after an hour and ten minutes. If I look at the engine log, it appears to be full of the following warnings:
"Navigator error while processing request"
"Exception while processing request"
I have no idea how to troubleshoot this issue. We've been in contact with Qlik, but haven't had any answers. It's not feasible for us to have reports in production that are so inconsistent.
Does anyone have any ideas of things we can try in order to remedy this issue? The two nodes in our cluster are very large and powerful machines and shouldn't be having so many issues generating these reports.
