For a listing of compatible, built-in Qlik Sense objects, check the compatibility matrix found in the following link to better understand specific Qlik Sense object limitations with NPrinting reporting. Working with Qlik objects
Check that 'In' and 'Out' bound ports between the NPrinting server NPrinting engine and the Qlik Sense server are configured. Keep in mind that Ports 4997 and 443 must now also be configured since November 2018 release of NPrinting.
Check that ports 2727 and 15672 are not being used by any other process/program on the NPrinting server and engine computers. These ports are required for normal NPrinting operation. See Ports - Qlik NPrinting
Check that the Qlik Sense objects and or Qlik Sense visualization used in your NPrinting report are supported as per the "Keep in Mind" section above
Abort all running Task and On Demand Task executions then reboot the NPrinting Server, NPrinting Engine computer and the Qlik Sense server at the first available opportunity and retest if the issue still persists. Ensure all services on each computer are up and running before retesting.
If the issue persists after checking all points above, please check the solutions in the resolutions section of this article.
Resolution 4 - If Resolution 1 and 2 above do not resolve the issue and all image export requirements are met, check and perform the steps below:
Stop the NPrinting Engine Service.
Open the renderer.config file in C:\Program Files\NPrintingServer\NPrinting\Scheduler. You may need to open the file in administrator mode.
Make a backup copy of the file.
Add (or modify if present) the following parameter: <add key="webrenderer-timeout-sec" value="120" /> 120 is the time in seconds for the timeout. It can be increased further if necessary.
Restart the NPrinting Engine service
! Increasing these timeout values may lead to improved performance as NPrinting may simply need more time to execute tasks and report generation.
How to Enable 'Tracing'
If resolutions above have not resolved the issue, please perform the following steps and reproduce the issue one again in order to retrieve additional tracing information necessary for a deeper investigation. Then zip and upload the requested folder below up to the support case.
CEF tracing is enabled by automatically when enabling DEBUG logging from NP June 2020 and later versions.