Error during report generation: ArgumentOutOfRangeException

[Dustver]

Qlik NPrinting May 2026 SR1 - ArgumentOutOfRange when exporting Qlik Sense Sheet as image above 800×600

Hi,

I am experiencing a reproducible issue with Qlik NPrinting May 2026 SR1 when generating an HTML report containing Qlik Sense sheets as images.

Environment

• Qlik NPrinting: May 2026 SR1

• Report type: HTML

• Source: Qlik Sense May 2026 patch 2

• Object type: Qlik Sense Sheet

• The sheets contain charts only

• No tables are used in the problematic sheets

Problem

The report fails during Content production with:

ArgumentOutOfRangeException
Заданный аргумент находится вне диапазона допустимых значений.

The NPrinting log contains:

Starting content resolution for report ...
Finished content resolution for report ...

Starting content production
WARN: error during report generation:
Заданный аргумент находится вне диапазона допустимых значений.

Finished content production

Failed generation of report ...
ERROR:
Заданный аргумент находится вне диапазона допустимых значений.

Content resolution completes successfully, and the failure happens only during content production.

Reproduction

The HTML template is extremely simple:

<html>
    <body>
        <img src="%%ef634961-f70e-4980-b27d-7a035aa28007%%" alt="Sheet 1">
        <img src="%%c19f9cd5-77cd-4037-9331-dca5115bdf7b%%" alt="Sheet 2">
    </body>
</html>

Both objects are Qlik Sense sheets added to the Images node in NPrinting Designer.

The important part is the image dimensions.

I tested the same sheet with different NPrinting image dimensions:

Image dimensions Result Below 800×600 Report generation succeeds 800×600 Report generation succeeds, but the sheet is cropped Above 800×600 Report generation fails with ArgumentOutOfRangeException Auto / 0×0 Report generation fails with ArgumentOutOfRangeException

For example, increasing the dimensions beyond 800×600 causes the report to fail even though the same sheet works with smaller dimensions.

Additional observations

The issue does not appear to be related to the HTML itself.

The same HTML report can successfully generate other content, and the failure occurs before publishing, during content production.

The problematic objects are whole Qlik Sense sheets exported as a single image.

The issue appeared after moving to the May 2026 generation of NPrinting. The same reporting approach worked in the previous NPrinting version.

According to the NPrinting documentation, Qlik Sense sheets are exported as a single image:

https://help.qlik.com/en-US/nprinting/May2026/Content/NPrinting/QlikViewEntityReports/Embed-QV-Sheet...

Questions

1. Is there a known defect in NPrinting May 2026 / May 2026 SR1 related to Qlik Sense Sheet image rendering and image dimensions?

2. Is 800×600 an unintended rendering limit in the current version?

3. Is there a configuration parameter or workaround that allows Qlik Sense sheets to be rendered at, for example, 1920×1080?

4. Is there a recommended workaround for HTML reports when a whole Qlik Sense sheet needs to be exported as an image?

5. Could this be related to the image rendering changes/regressions introduced in May 2026?

I can provide the NPrinting logs, screenshots of the template/image properties, and a minimal Qlik Sense app reproducing the issue if required.

Thanks.

[Ruggero_Piccoli]

Hi, 

Your description matches an issue with images rendered at higher resolutions afftecting Qlik NPrinting May 2026 SR1 and February 2025 SR7. The same sheets render correctly at smaller sizes. May 2026 IR and older versions are not affected.

Until a Service Release with a fix is available, there are two options:
- set the image size of the sheets to a size that works in your tests
- as a temporary workaround, keep the NPrinting Server on May 2026 SR1 and replace only all the Engines with the May 2026 IR. Then add the Engines again in the web console Engine manager or re-enter its certificate password.

Please note that the second option leaves you with mixed versions. It isn't a configuration to keep:  as soon as a Service Release with the fix is available, upgrade the Server, all Engines and the Designer to that same release.

Best Regards,

Ruggero