Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dear Qlik Community,
I faced following issue when trying to add an img to my NPrinting report: Error: CEF rendering exception (attached is a screenshot of error popup). I've tested with different types of apps/objects/reports but always got the same issue. It is probably worth mentioning that there are no connection issues between Nprinting and Qlik Sense servers.
I know that this issue is often discussed here and i've also checked those articles:
but in none of the could find a solution for my case. I've checked cipher suites and both servers contain all required ones. Our both servers are in cloud and we found no issues with firewall or ports.
I would appreciate your support and thank you in advance.
Regards,
Pavel
HI Pavel,
Yes you might simply have low resources on the NPrinting server and or the Qlik Sense server.
By rebooting or restarting services you are reducing RAM and CPU consumption temporarily.
You should keep an eye on your system resources using Windows performance monitoring tools tool to monitor RAM and CPU usage and address any shortages there in based this monitoring.
You might also consider scheduling regular restarts of your NPrinting and Qlik Sense servers to mitigate performance and memory leak issues.
Kind regards..
I don't know that you can entirely get ride of those errors (particularly during heavy NPrinting report distribution and perhaps combined with day to day Qlik Sense system usage not related to NPrinting. QS and NP server saturation can cause timeout errors) but if you follow the points in my responses to Pavel, then you should hopefully see less of them.
Kind regards...
Hi,
They are timeout errors. Are you using a Qlik Sense extension? Could you check the Qlik Sense server workload and response time? How long will it take to open the Qlik Sense charts used in Qlik NPrinting manually and directly in Qlik Sense?
If it doesn't solve please open a support ticket with the complete logs and everything we need to be able to reproduce the issue.
Best Regards,
Ruggero