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-Report-Temp.htm

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.

What does it really mean to be bold or fearless in a professional setting? Join us this week as we explore how taking risks can open new doors in your career. Join the discussion to share the moments where courage paid off, the internal barriers that may have held you back, and ideas for how leaders can create environments where people feel safe to speak up and take bold steps forward.

Related Content: 

Article: Be Bold in Business: A Woman's Guide to Fearless Leadership

Podcast: Standout from the crowd: How to be bold an unapologetic

Share your thoughts in the comments: What does being “bold” or “fearless” mean to you in a professional setting?

Hi everyone, I have been setting up a scheduled REST connection in Qlik Sense to pull domain and page authority metrics into our marketing dashboard. When querying the external tool endpoints for bulk URL analysis, the response returns nested arrays for historical scores, but Qlik's REST connector keeps flattening the response into multiple disconnected tables that separate the root domain identifiers from their respective score records.

I tried adjusting the pagination settings and data connection parameters, yet whenever the reload task executes, the resulting data model creates synthetic keys and null values across the metric fields. Has anyone encountered similar JSON transformation issues when pulling automated website metrics from this kind of tool into Qlik Sense, and what scripting approach would you recommend to keep the domain keys and metric history properly joined?

We received a notice that an external integration or Qlik Automate modified a reload task through /api/v1/reload-tasks and should move to /api/scheduling/tasks before November 26, 2026.

The deprecation changelog says that creating tasks through the old API stops on November 26, while updates and deletes of existing tasks remain possible until each task is migrated. Could Qlik clarify:

1. Will all old API write calls fail on November 26, or only task creation? Can updates to an unmigrated task continue after that date?
2. How can a tenant administrator identify the specific integration, API key, or Automate workflow that made the old API call? Our task audit events show changes but do not include the HTTP method or request path.
3. Does this change affect POST /api/v1/reloads, which triggers an immediate app reload, or only the reload-task management API?

We want to identify the actual caller and migrate it without disrupting scheduled or on-demand reloads. Thanks for any guidance.

I'm trying to install a wildcard SSL certificate from GoDaddy on our NPrinting server. I thought I could copy it from our Qlik Sense on Windows server, but that didn't seem to work. Can you confirm that I need to send a new CSR to GoDaddy from the NPrinting server? We're using NPrinting February 2025, not May 2023, but the drop-down doesn't have more recent versions.