Upgrade to Qlik NPrinting June 2020 or newer with modified rendering configuration files

Ruggero_Piccoli — Tue, 24 May 2022 18:45:36 GMT

You must read this article only if you customized the Qlik Sense rendering configuration section of your Qlik NPrinting Engine configuration files (engine.config).

For default upgrade instructions, see Upgrading Qlik NPrinting.

Environment:

Modified rendering configuration files (engine.config)

In NPrinting April 2020 and earlier versions, by default, engine.config settings are stored in C:\Program Files\NPrintingServer\NPrinting\Engine\engine.config.

For example, if you have uncommented any of the following parameters, you must migrate to the new configuration:

If you have not edited any of these parameters, you can skip this section above.

The management of reporting web renderer parameters has been simplified.

The modification consists of two steps:

Parameters have been moved from the Qlik NPrinting Engine to the Qlik NPrinting Scheduler configuration file to ensure that all Qlik NPrinting Engines have uniform behaviour.
Some parameters have been simplified for easier handling.

This guide covers three topics:

The migration to the new configuration. This is mandatory if you edited the web renderer settings in the Qlik NPrinting engine.config file.
Simplifying parameter settings (optional).
Editing parameters in the renderer.config file (for customers editing these settings for the first time).

Before upgrading

Before upgrading your installation to Qlik NPrinting June 2020 and later versions, create backup copies of all your Qlik NPrinting Engine configuration files.
By default, they are stored in

C:\Program Files\NPrintingServer\NPrinting\Engine\engine.config

Migrating the parameters in the NPrinting Engine.config file

Do the following:

Stop the Qlik NPrinting Scheduler and Engine Windows services.
Copy any parameter you have previously set in your Qlik NPrinting Engine configuration files (the engine.config file of all your Engines) into the new file on the Qlik NPrinting Server computer. Ensure you notice the new formatting in the renderer.config file.

C:\Program Files\NPrintingServer\NPrinting\Scheduler\renderer.config

You may need to open the file in administrator mode.
When editing the strings webrenderer-mashup-qs or webrenderer-args parameters within the renderer.config file, ensure that the options are separated with a semicolon as shown in the example below on the right.

Reformatting examples:

engine.config (previous)	renderer.config (current)
<add key="webrenderer-mashup-qs" value="logging=net,ws&wssecure=1" />	<add key="webrenderer-mashup-qs" value="logging=net,ws;wssecure=1" />
<add key="webrenderer-args" value="-l=info -grpc-addr=127.0.0.1:51051 -e=1" />	<add key="webrenderer-args" value="-l=info;-grpc-addr=127.0.0.1:51051;-e=1" />

Simplify the parameters after the migration (optional)

If you edited any of the parameters webrenderer-request-overall-timeout-msec, webrenderer-remote-request-timeout-msec or webrenderer-remote-request-js-timeout-msec, you can simplify the setting of the timeout by using a single parameter that will set overall timeouts.

Do the following:

Take the maximum value between webrenderer-remote-request-timeout-msec and webrenderer-remote-request-js-timeout-msec.
Divide this value by 1000 to convert from milliseconds to seconds.
Use the calculated value to set webrenderer-timeout-sec.
Remove all webrenderer-request-overall-timeout-msec, webrenderer-remote-request-timeout-msec and webrenderer-remote-request-js-timeout-msec settings.

Configuration examples:

engine.config (April 2020 & earlier versions of NPrinting)	renderer.config (June 2020 & newer versions of NPrinting)
<add key="webrenderer-request-overall-timeout-msec" value="300000" /> <add key="webrenderer-remote-request-timeout-msec" value="60000" /> <add key="webrenderer-remote-request-js-timeout-msec" value="30000" />	<add key="webrenderer-timeout-sec" value="60" />
<add key="webrenderer-request-overall-timeout-msec" value="300000" /> <add key="webrenderer-remote-request-timeout-msec" value="60000" /> <add key="webrenderer-remote-request-js-timeout-msec" value="90000" />	<add key="webrenderer-timeout-sec" value="90" />

From NP June 2020 and newer versions the value settings are now in 'seconds' rather than milliseconds and only 'one' value is needed rather than 'three'
NOTE: Restart the Qlik NPrinting Scheduler and Engine Windows services to enable updated renderer.config file values

Editing parameters in the renderer.config file

The parameters available in

C:\Program Files\NPrintingServer\NPrinting\Scheduler\renderer.config

lets you change two basic operation settings.

1. Set the web renderer logging level to debug

If you want to set the logging level to debug only for the reporting web renderer:

Open the renderer.config file.
Set the value to <add key="webrenderer-logs" value="verbose" />.

This value is automatically set when the Qlik NPrinting Engine is set to debug log level in accordance with Logging.

2. Increase the rendering timeouts

The rendering timeout is set by default to 30 seconds. This can be increased if there are timeout errors due to charts that render slowly.

Timeouts errors appear in the Qlik NPrinting Engine logs as CefRenderingException with the error code

SENSE_JS_RENDER_TIMEOUT
ErrorMaxJsAttemptsExceededResult
ERROR_RENDER_TIMEOUT_RESULT

To verify that the issue is generated by a chart that is slow to render, check the chart load time in the Qlik Sense app.

To increase the rendering timeout:

Open the renderer.config file.
Uncomment the webrenderer-timeout-sec option.
Set the desired value in seconds. For example, to set the timeout to 180 seconds, change the parameter to: <add key="webrenderer-timeout-sec" value="180" />.

article Upgrade to Qlik NPrinting June 2020 or newer with modified rendering configuration files in Official Support Articles

Upgrade to Qlik NPrinting June 2020 or newer with modified rendering configuration files

Environment: