Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Table of Contents
The following release notes cover the versions of QlikView released in September 2026. For questions or comments, post in the Product Forums or contact Qlik Support.
https://help.qlik.com/en-US/qlikview/September2026/Content/QV_HelpSites/Whats_New_in_QlikView.htm
Window script function enhancements
The syntax, functionality, and documentation of window functions have been enhanced to improve usability and flexibility. Window functions are commonly used for analytics and ML data preparation scenarios that require aggregations across different partitions without losing the grain of the input data.
Script-only variables and drop mapping tables
Mapping tables can now be dropped as soon as they are no longer needed, improving memory efficiency during reloads, particularly helpful for large mapping tables or iterative scripts.
The load script now also supports script-only variables and explicit variable dropping, ensuring temporary variables do not appear in loaded data.
Concat function "no sorting"
When using the Concat script and chart functions, you can now specify a value of 0 as the sort_weight argument. When this is done, sorting is not applied to the function output.
OAuth 2.0 authentication for sending email
QlikView now supports sending email through Microsoft 365 using OAuth 2.0 authentication and the Microsoft Graph API.
Enhancements include:
The following functionality has been deprecated.
Source Control deprecated
The Source Control feature has been deprecated and is no longer supported.
QlikView IE Plug-in deprecated for Qlik Cloud
The QlikView IE Plug-in is no longer supported for use with Qlik Cloud. The plug-in remains supported for use with client-managed QlikView.
QlikView Workbench deprecated
The QlikView Workbench development toolbox has been deprecated and is no longer supported.
QlikView OEM-package OCX deprecated
The QlikView OEM-package OCX has been deprecated and is no longer supported.
Important information: Internet Explorer (IE) Plugin removed starting with the September 2027 Release
Due to Microsoft's retirement of Internet Explorer in 2022, the QlikView IE plugin will no longer be included or supported starting with the QlikView September 2027 release. Customers using the IE plugin should migrate to QlikView Web Client or QlikView Desktop before upgrading.
For details, FAQs, see the full statement: https://community.qlik.com/t5/Support-Updates/QlikView-Internet-Explorer-IE-Plugin-to-be-removed-in-the/ba-p/2556681
|
Key |
Title |
Description |
|
QCB-35817 |
Data lineage: QVD file tracking corrected |
Data lineage was not recorded when loading data from text files into QVD files. Lineage tracking now captures the complete data flow for QVD file operations. |
|
QCB-35797 |
Chart: plot area position in design mode |
Dragging the red axis borders to resize a bar chart's plot area caused the chart to shrink beyond the intended position. The chart area now resizes to exactly where the drag is released. |
|
QCB-35510 |
QlikView Desktop: project folder export now completes successfully |
Saving documents with the -prj export option sometimes produced an empty project folder with no files or error message when the document contained deleted object references. The export process now skips these references and writes all project files as expected. |
|
QCB-35466 |
QlikView: table gridlines visible at all zoom levels |
Horizontal and vertical gridlines and thin cell borders in straight tables and pivot tables appeared intermittently at fractional zoom levels such as Fit to Window. Thin strokes are now rendered at a minimum of one device pixel to ensure gridlines and borders remain visible at all zoom levels. Users who previously thickened their table borders as a workaround no longer need to do so. |
|
QCB-35345 |
Visualization: dimension limitation with tied measures |
Tied measures were broken by internal element number order instead of the configured sort criteria when a dimension limitation was applied. Sort order with tiebreaker logic now determines which elements are grouped into Other. |
|
QCB-35241 |
Document Support Info: non-ANSI file name crash fixed |
Document Support Info crashed when opening documents with non-ANSI file names such as Japanese characters. The window now uses UTF-8-aware path handling to correctly open documents with any-language file names. |
|
QCB-35238 |
QlikView: resolved freeze during DMS license lease |
QlikView became unresponsive when a non-domain user leased a DMS license with SupportLeaseLicenseForDMSMode=1 enabled. Internal dialogs now suppress correctly, allowing the Windows credential prompt to display and function as expected. |
|
QCB-34954 |
Visualization: chart loading spinner persists after data load |
Loading spinners remained visible indefinitely when charts did not repaint due to unchanged data. The spinner now clears correctly in all repaint scenarios. |
|
QCB-34571 |
AccessPoint: sheet list scroll issue |
Long sheet lists extended beyond the visible area, preventing access to all sheets. A scroll bar now appears when the list exceeds the available space. |
|
QCB-34453 |
QlikView Desktop: Intermittent crash with open document |
Qlikview Desktop and Batch would occasionally crash when the application was closed with an open document. This issue has been resolved. |
|
QCB-33602 |
UI: context menu tooltip handling |
Tooltips remained visible after selecting a context menu action. Tooltips now dismiss automatically when any context menu action occurs. |
|
QCB-33601 |
App: icon transparency corrected |
Uploaded icons appeared transparent or unclear in the app. Icons now display with proper visibility and correct transparency handling. |
|
QCB-33570 |
Document support: corrected Japanese character display |
Document names containing Japanese characters appeared as garbled text in the support information panel. Unicode encoding now renders all double-byte characters correctly. |
|
QCB-33534 |
Window Function: Improved Handling of If-Statements |
We've resolved an issue where if-statements with a window function nested in the condition expression were being evaluated before the window function calculations were completed, resulting in incorrect results. |
|
QCB-33101 |
QvConnect32 Connector Availability |
The QvConnect32 connector is now included again in the QlikView Server bundle. |
|
QCB-33031 |
Measures: Fixed evaluation of simple fields with NULL values |
Resolved an issue where hypercubes containing only simple field dimensions and measures without aggregation incorrectly evaluated to NULL. Now, when a measure contains one value plus NULL, it correctly returns the actual value instead of NULL. |
|
QCB-32937 |
Access Point: bar chart printing with alternate states |
Bar charts using alternate states and expression conditionals did not print correctly. Printing now works as expected for bar charts with these features. |
|
QCB-32936 |
Visualization: area chart rendering with uneven series |
Area charts displayed incorrectly when series contained different numbers of elements. The chart now renders correctly regardless of element count across series. |
|
QCB-32927 |
Legacy Table Sorting Option for Individual Apps |
We've introduced a new script variable to give you more control over table sorting behavior in specific apps. Here's what you need to know:
|
|
QCB-32813 |
Dimensions/Measures: Fixed access error for dynamic properties |
Resolved a "State not found" error that occurred when accessing dimensions or measures containing dynamic properties using QIX internal type names (e.g., 'qSelectionObjectDef'). |
|
QCB-32690 |
Excel Export: Option for Mixed Data Export |
To choose how to export mixed data, use the setting 'ExcelExportMixedAsText'. |
There are no known new limitations at time of release.
Upgrading QlikView NPrinting on demand add-on
The following directions apply when:
When upgrading Nprinting On Demand components and the QlikView IIS server settings component, do so in the following order:
1. First: Update the version of Qlik NPrinting on-demand add-on
2. Second: Update the version of QlikView IIS Server
You can update your Qlik NPrinting Server and Qlik NPrinting engine components at any time – before or after the QlikView server update. The on-demand add-on from Qlik NPrinting May 2025 is compatible for use with previous versions of Qlik NPrinting server.
NOTE: This order of operation is a one-time requirement for your first instance of QlikView server update to September 2025 or higher. Once the QlikView server is updated and the on-demand component is working correctly, you can perform future updates in any order.
The system requirements for this release can be found under “System requirements” on the Qlik help web site. https://help.qlik.com/en-US/qlikview/September2026/Content/QV_HelpSites/System-requirements.htm
Support for Windows 10 has been removed because the operating system has reached end of support with Microsoft.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover Qlik NPrinting May 2026 IR to May 2026 SR1.
Jira issue ID: SUPPORT-10976
Erlang is updated to version 27.3.4.16.
Jira issue ID:
The PostgreSQL version of the Qlik NPrinting Repository service is upgraded to 17.10-2.
Jira issue ID: OP-10204
The time zone data is updated to version 2026c.
Jira issue ID: QCB-33315 QCB-33920 QCB-34833
In some circumstances, Excel reports could be generated with an incorrect sort order in native pivot tables or with chart legends displayed incorrectly. Report generation could also fail with error code “SHA-10000,” the error “Aspose.Cells.CellsException: This won't work because it will move cells in a table on your worksheet,” or an “ArgumentOutOfRangeException” error. These issues have been resolved.
These issues affected all February versions of Qlik NPrinting.
Jira issue ID: QCB-34949
Temporary files created to support the export of Qlik entities were not deleted after the export process completed and had to be removed manually. The temporary files are now deleted after use.
Jira issue ID: OP-10205
Qlik Sense container objects, including layout containers, are now visible by default under the Images node in Qlik NPrinting Designer. Existing report templates that reference a layout container ID no longer fail during generation with an unsupported sn-layout-container export error. In earlier versions affected by this issue, container objects can be made available through configuration.
Jira issue ID: QCB-35571
The Qlik NPrinting Repository and Messaging MSIs contained in the Qlik NPrinting Server installer were not signed, resulting in setup failures in some cases.
Jira issue ID: QCB-35587
Exporting a Word report to PDF could fail with an “Object reference not set to an instance of an object” error when the PDF image quality was set to Very High. The issue affected reports generated after upgrading to Qlik NPrinting May 2026.
The following issues and limitations were identified at release time. The list is not comprehensive; it lists all known major issues and limitations. We expect to have these issues fixed in future versions.
The following languages are supported:
Other languages are not officially supported. There may be issues with other languages, particularly those with right-to-left script and non-Roman alphabets.
Qlik Sense custom size sheets are not supported. Custom size will not be maintained on export.
Alternate states
QlikView and Qlik Sense alternate states are not supported.
QlikView and Qlik Sense alternate states are not supported.
Jira issue ID: OP-6196
Qlik NPrinting Server, Engine, and Designer can only be installed on C: drives. Any attempt to install them on a different drive will result in task failures.
Jira issue ID: OP-5831
When you add the same object twice, using the Images node in Qlik NPrinting Designer, only the image size property of the first image is respected.
It is possible to select the “Enable” check box in On-Demand for reports using Qlik Sense app data. These reports are visible in the QlikView On-Demand menu of the QlikView On-Demand add-on. But if selected, they will not generate reports, and you will see an error message.
If you experience random crashes when using Qlik NPrinting Designer, open your Windows Display Settings in the Control Panel and verify that Smaller – 100% (default) is selected. When settings of 125% or 150% are selected, Qlik NPrinting Designer may crash.
Jira issue ID: OP-5908
In some cases, when you use Qlik NPrinting On-Demand in Internet Explorer 11 or Edge, the “origin” HTTP header is not generated. This results in the error message “REVEL_CSRF: tokens mismatch”.
The workaround is to install Qlik NPrinting On-Demand on a Microsoft IIS server hosting QlikView Access point or use a different web browser.
Jira issue ID: OP-4940
Qlik NPrinting Designer may be unable to open a report template if there are too many filters associated with a connection in the report's app. The following error message displays: “A task was canceled”.
This typically happens when more than 4000 filters are using fields from a connection. Sometimes, higher numbers can work. For example, 7000 filters have worked in some situations.
The workaround is:
1. Split the Qlik NPrinting app into separate apps.
2. Split the connections (possibly by using multiple connections to the same documents in different apps).
3. Split the filters across apps (so that the filter count per app is lower).
Jira issue ID: OP-4839
Some Qlik NPrinting tasks fail with the error message: “Exceeded maximum number of retries”. This is due to a performance issue in QlikView that appears when it exports large unfiltered files to Excel.
Jira issue ID: OP-5278
In some rare circumstances, pressing the Verify connection button will cause the screen to freeze on the “Initializing…” status and the spinning wheel cursor. This happens when a Qlik NPrinting Engine goes offline and Verify connection is pressed before the Qlik NPrinting Scheduler is aware that it is offline. It can take up to 20 seconds before the Qlik NPrinting Scheduler determines the offline status of a Qlik NPrinting Engine.
Jira issue ID: OP-5914
When you:
The filters associated with each user are not uploaded, or displayed, for performance reasons. Waiting for all filters for thousands of users to import would take a long time. In most cases, importing this information is unnecessary, because filters created for users often contain something like the user IDs. You can change this behavior and make all filters visible by uncommenting the line <!--<add key="include-user-filters" />--> in the webengine.config file.
To make a specific filter visible in the lists, remove its association to all users, or create a new filter with the same fields and values not linked to any user.
Jira issue ID: OP-3986
The rollback that follows a Qlik NPrinting Server or Engine upgrade cancellation may corrupt the related Qlik NPrinting installation. A rollback is triggered by errors or by clicking the cancel button during the upgrade execution. After a corruption caused by a rollback, services may be uninstalled or cannot be started.
To restore a Qlik NPrinting Server to its original status:
You should always create a backup before starting an update. In any case, a backup is automatically created in the folder "%ProgramData%\NPrinting" at the beginning of the upgrade process. To restore a Qlik NPrinting Engine to original status:
Jira issue ID: OP-7560
Add title functionality is not supported on Qlik Sense objects with Assistance mode enabled. The workaround to restore the Add title functionality is to disable Assistance mode for the chart in Qlik Sense. Then reload the metadata of the connection.
Jira issue ID: OP-7568
Qlik Sense objects made in Assistance mode cannot be used as tables, columns, or cells in Qlik NPrinting. To restore them, disable Assistance mode on the chart in Qlik Sense; then reload the metadata of the connection. Furthermore, if a Qlik Sense object made with Assistance mode is exported as a table, column, or cell using Qlik NPrinting APIs, the request will fail.
Jira issue ID: OP-7165
Open Type Fonts (*.otf) are not supported in PixelPerfect templates. Generated reports will use a different font, and not look as expected.
Jira issue ID: OP-7747
The following functionalities are not supported for Qlik Sense tables that have a "Show column if" condition set on one or more of their columns: levels, single column export, and keep source formats.
Jira issue ID: OP-8382
Qlik Sense On-Demand reports with selections applied on calculated dimensions will fail. However, you can apply selections on dimensions based on Qlik Sense fields. The workaround is to move the formula to the load script and use the calculated fields to apply selections to your On-Demand reports.
Jira issue ID: OP-8985
Due to the internal way of exporting Qlik Sense histograms, you cannot add them to the Qlik NPrinting Designer Tables node. If you add a Qlik Sense histogram to the Tables node, you will not receive any errors or warning messages, but the exported data will be wrong.
Jira issue ID: OP-8921
QlikEntity reports support Qlik Sense objects with the following limitations:
Jira issue ID: OP-9087
You cannot embed an Excel worksheet in a PowerPoint report template. This will cause a Qlik NPrinting Designer crash. The workarounds are to insert the Excel worksheet without using the Qlik NPrinting Designer:
Jira issue ID: OP-9067
Dynamic views is a new Qlik Sense feature starting from June 2020.
If you connect Qlik NPrinting to a Qlik Sense app that contains a chart used to generate dynamic views, the chart and the containing sheet are excluded from the Qlik NPrinting connection cache and cannot be used in reports.
You can connect Qlik NPrinting to a Qlik Sense app containing dynamic views. However, after a dynamic view refresh, the connection will stop working.
Jira issue ID: OP-9628
Starting from November 2020, RabbitMQ Server (deployed as Qlik NPrinting Messaging Service) has been updated to version 3.8.3. It has an internal limit, not configurable, about messages size of 512MB. Previous limit was 2GB. As consequence, is not possible to generate Qlik NPrinting reports bigger than 512MB.
Jira issue ID: OP-9766
Excel worksheet print areas can contain more than one range if the generation of the report does not expand the print area. If it expands, you will see an error: “Invalid Cell Name”. For example, the default setting of the Expand Range option in a Qlik NPrinting table causes the print area to change during report production, and an error is received.
Jira issue ID: OP-9518
Using Cyrillic characters in the Search form of the Qlik NPrinting user interface is case sensitive.
Jira issue ID: OP-9995
The percentage “%” format is not kept in Excel reports when using QlikView 12.50 (12.50.20000) or newer due to a QlikView issue. You can solve this by upgrading to QlikView May 2021 SR2 (12.60.20200) or newer.
Jira issue ID: OP-95599
If you start a Run Verification on a connection to a QlikView document in QVF format, Qlik NPrinting cannot confirm whether the QlikView Desktop version installed locally on each Qlik NPrinting Engine is compatible with QVF file format. The check mark next to "QlikView can open the document" may be green, even if a version of QlikView that does not support QVF is installed. This is because verification only checks file permissions. If the installed QlikView Desktop does not support QVF format, metadata generation will fail.
Jira issue ID: OP-95682
QlikView objects with many different fields with exactly the same label are not supported. Duplicated labels cause an exception during the connection cache generation. To solve this issue, ensure that each field has a unique label.
Jira issue ID: OP-95797
Images linked by using URLs in Qlik Sense tables are exported as text. This affects only Qlik Sense connections. A workaround exists for PixelPerfect templates.
Jira issue ID: HLP-17139
The sensitivity labels feature in Microsoft Office is not supported. If used, report generation and preview will fail with errors.
As a workaround to the issue, block the Active Directory domain policy that pushes the sensitivity labels requirement to domain users.
Jira issue ID: RS-4525
When editing a PowerPoint template exported from Qlik NPrinting using the Office add-in, image refresh functionality is not available if the installed version of Microsoft Office supports an Office JavaScript API requirement set lower than 1.10.
Attempting to refresh an image displays a placeholder image instead of the refreshed content.
In addition, image selection and the add-in properties pane are not synchronized correctly: selecting an image in the PowerPoint template does not automatically display its properties in the add-in, and opening the image properties from the add-in does not select or activate the corresponding image in the template.
To use image refresh functionality and ensure correct synchronization between images and their properties, install a version of Microsoft Office that supports Office JavaScript API requirement set 1.10 or later.
Minimum supported Office versions:
To upgrade to Qlik NPrinting May 2026 Service Release 1, you must start from one of the following versions:
Note that the minimum starting version for a direct update has changed, starting from February 2025 SR2 (25.5.8).
If you are using a version older than May 2022 (22.15.2) you must first upgrade to a version from May 2022 (22.15.2) to February 2025 SR1 (25.5.5). You can then upgrade to the current version. Skipping this step will stop the installation process with an error message that the upgrade is not supported. Your installation will not be modified or broken in this case and you will be able to continue following the correct procedure.
To upgrade directly to Qlik NPrinting May 2022 (22.15.2), you must start from one of the following versions:
If you have a version of Qlik NPrinting older than April 2018, you must first upgrade to Qlik NPrinting April 2018 before you can upgrade to Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting May 2026 SR1.
If you have a version of Qlik NPrinting older than 17.3, you must first upgrade to Qlik NPrinting 17.3. Then you must upgrade to a version from April 2018 to May 2021 SR4 before you can upgrade to Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting May 2026 SR1.
If you are upgrading from a version older than February 2018, all metadata caches (QlikView and Qlik Sense) will be marked as "not generated". This is due to a breaking change in the format of the metadata cache. All connection caches must be regenerated before you can edit a template or create a new connection.
You must back up your data before you proceed. Data can become damaged if a problem occurs during the upgrade. If data is damaged, a backup is required to restore the repository. See: Backup and restore of a repository
After backup, you must follow the instructions for upgrading on the help site page Qlik NPrinting upgrade.
If you are upgrading to 2026 IR from September 2018 SR2 or older you must:
• Open port 4997 outbound on Qlik NPrinting Server and inbound on all Qlik NPrinting Engines.
• Reinstall all your Qlik NPrinting Engines and provide a password for certificate exchange.
• Open the Engine manager in the Web Console.
• Open the detail page for each Engine and send the certificate after inserting the same password you used during the engine’s reinstallation.
Qlik NPrinting Engines stay offline until the certificate exchange is performed. Older Engine versions cannot connect to a Qlik NPrinting May 2026 IR Server.
Setups are available at https://community.qlik.com/t5/Downloads/tkb-p/Downloads
About Qlik
| Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive. |
Table of Contents
The following release notes cover Qlik NPrinting February 2025 SR6 to SR7.
Jira issue ID: SUPPORT-10976
Erlang is updated to version 27.3.4.16.
Jira issue ID:
The PostgreSQL version of the Qlik NPrinting Repository service is upgraded to 17.10-2.
Jira issue ID: OP-10204
The time zone data is updated to version 2026c.
Jira issue ID: QCB-33315 QCB-33920 QCB-34833
In some circumstances, Excel reports could be generated with an incorrect sort order in native pivot tables or with chart legends displayed incorrectly. Report generation could also fail with error code “SHA-10000,” the error “Aspose.Cells.CellsException: This won't work because it will move cells in a table on your worksheet,” or an “ArgumentOutOfRangeException” error. These issues have been resolved.
These issues affected all February versions of Qlik NPrinting.
Jira issue ID: QCB-34949
Temporary files created to support the export of Qlik entities were not deleted after the export process completed and had to be removed manually. The temporary files are now deleted after use.
Jira issue ID: OP-10205
Qlik Sense container objects, including layout containers, are now visible by default under the Images node in Qlik NPrinting Designer. Existing report templates that reference a layout container ID no longer fail during generation with an unsupported sn-layout-container export error. In earlier versions affected by this issue, container objects can be made available through configuration.
Jira issue ID: QCB-35571
The Qlik NPrinting Repository and Messaging MSIs contained in the Qlik NPrinting Server installer were not signed, resulting in setup failures in some cases.
The following issues and limitations were identified at release time. The list is not comprehensive; it lists all known major issues and limitations. We expect to have these issues fixed in future versions.
The following languages are supported:
Other languages are not officially supported. There may be issues with other languages, particularly those with right-to-left script and non-Roman alphabets.
Qlik Sense custom size sheets are not supported. Custom size will not be maintained on export.
Alternate states
QlikView and Qlik Sense alternate states are not supported.
QlikView and Qlik Sense alternate states are not supported.
Jira issue ID: OP-6196
Qlik NPrinting Server, Engine, and Designer can only be installed on C: drives. Any attempt to install them on a different drive will result in task failures.
Jira issue ID: OP-5831
When you add the same object twice, using the Images node in Qlik NPrinting Designer, only the image size property of the first image is respected.
It is possible to select the “Enable” check box in On-Demand for reports using Qlik Sense app data. These reports are visible in the QlikView On-Demand menu of the QlikView On-Demand add-on. But if selected, they will not generate reports, and you will see an error message.
If you experience random crashes when using Qlik NPrinting Designer, open your Windows Display Settings in the Control Panel and verify that Smaller – 100% (default) is selected. When settings of 125% or 150% are selected, Qlik NPrinting Designer may crash.
Jira issue ID: OP-5908
In some cases, when you use Qlik NPrinting On-Demand in Internet Explorer 11 or Edge, the “origin” HTTP header is not generated. This results in the error message “REVEL_CSRF: tokens mismatch”.
The workaround is to install Qlik NPrinting On-Demand on a Microsoft IIS server hosting QlikView Access point or use a different web browser.
Jira issue ID: OP-4940
Qlik NPrinting Designer may be unable to open a report template if there are too many filters associated with a connection in the report's app. The following error message displays: “A task was canceled”.
This typically happens when more than 4000 filters are using fields from a connection. Sometimes, higher numbers can work. For example, 7000 filters have worked in some situations.
The workaround is:
1. Split the Qlik NPrinting app into separate apps.
2. Split the connections (possibly by using multiple connections to the same documents in different apps).
3. Split the filters across apps (so that the filter count per app is lower).
Jira issue ID: OP-4839
Some Qlik NPrinting tasks fail with the error message: “Exceeded maximum number of retries”. This is due to a performance issue in QlikView that appears when it exports large unfiltered files to Excel.
Jira issue ID: OP-5278
In some rare circumstances, pressing the Verify connection button will cause the screen to freeze on the “Initializing…” status and the spinning wheel cursor. This happens when a Qlik NPrinting Engine goes offline and Verify connection is pressed before the Qlik NPrinting Scheduler is aware that it is offline. It can take up to 20 seconds before the Qlik NPrinting Scheduler determines the offline status of a Qlik NPrinting Engine.
Jira issue ID: OP-5914
When you:
The filters associated with each user are not uploaded, or displayed, for performance reasons. Waiting for all filters for thousands of users to import would take a long time. In most cases, importing this information is unnecessary, because filters created for users often contain something like the user IDs. You can change this behavior and make all filters visible by uncommenting the line <!--<add key="include-user-filters" />--> in the webengine.config file.
To make a specific filter visible in the lists, remove its association to all users, or create a new filter with the same fields and values not linked to any user.
Jira issue ID: OP-3986
The rollback that follows a Qlik NPrinting Server or Engine upgrade cancellation may corrupt the related Qlik NPrinting installation. A rollback is triggered by errors or by clicking the cancel button during the upgrade execution. After a corruption caused by a rollback, services may be uninstalled or cannot be started.
To restore a Qlik NPrinting Server to its original status:
You should always create a backup before starting an update. In any case, a backup is automatically created in the folder "%ProgramData%\NPrinting" at the beginning of the upgrade process. To restore a Qlik NPrinting Engine to original status:
Jira issue ID: OP-7560
Add title functionality is not supported on Qlik Sense objects with Assistance mode enabled. The workaround to restore the Add title functionality is to disable Assistance mode for the chart in Qlik Sense. Then reload the metadata of the connection.
Jira issue ID: OP-7568
Qlik Sense objects made in Assistance mode cannot be used as tables, columns, or cells in Qlik NPrinting. To restore them, disable Assistance mode on the chart in Qlik Sense; then reload the metadata of the connection. Furthermore, if a Qlik Sense object made with Assistance mode is exported as a table, column, or cell using Qlik NPrinting APIs, the request will fail.
Jira issue ID: OP-7165
Open Type Fonts (*.otf) are not supported in PixelPerfect templates. Generated reports will use a different font, and not look as expected.
Jira issue ID: OP-7747
The following functionalities are not supported for Qlik Sense tables that have a "Show column if" condition set on one or more of their columns: levels, single column export, and keep source formats.
Jira issue ID: OP-8382
Qlik Sense On-Demand reports with selections applied on calculated dimensions will fail. However, you can apply selections on dimensions based on Qlik Sense fields. The workaround is to move the formula to the load script and use the calculated fields to apply selections to your On-Demand reports.
Jira issue ID: OP-8985
Due to the internal way of exporting Qlik Sense histograms, you cannot add them to the Qlik NPrinting Designer Tables node. If you add a Qlik Sense histogram to the Tables node, you will not receive any errors or warning messages, but the exported data will be wrong.
Jira issue ID: OP-8921
QlikEntity reports support Qlik Sense objects with the following limitations:
Jira issue ID: OP-9087
You cannot embed an Excel worksheet in a PowerPoint report template. This will cause a Qlik NPrinting Designer crash. The workarounds are to insert the Excel worksheet without using the Qlik NPrinting Designer:
Jira issue ID: OP-9067
Dynamic views is a new Qlik Sense feature starting from June 2020.
If you connect Qlik NPrinting to a Qlik Sense app that contains a chart used to generate dynamic views, the chart and the containing sheet are excluded from the Qlik NPrinting connection cache and cannot be used in reports.
You can connect Qlik NPrinting to a Qlik Sense app containing dynamic views. However, after a dynamic view refresh, the connection will stop working.
Jira issue ID: OP-9628
Starting from November 2020, RabbitMQ Server (deployed as Qlik NPrinting Messaging Service) has been updated to version 3.8.3. It has an internal limit, not configurable, about messages size of 512MB. Previous limit was 2GB. As consequence, is not possible to generate Qlik NPrinting reports bigger than 512MB.
Jira issue ID: OP-9766
Excel worksheet print areas can contain more than one range if the generation of the report does not expand the print area. If it expands, you will see an error: “Invalid Cell Name”. For example, the default setting of the Expand Range option in a Qlik NPrinting table causes the print area to change during report production, and an error is received.
Jira issue ID: OP-9518
Using Cyrillic characters in the Search form of the Qlik NPrinting user interface is case sensitive.
Jira issue ID: OP-9995
The percentage “%” format is not kept in Excel reports when using QlikView 12.50 (12.50.20000) or newer due to a QlikView issue. You can solve this by upgrading to QlikView May 2021 SR2 (12.60.20200) or newer.
Jira issue ID: OP-95599
If you start a Run Verification on a connection to a QlikView document in QVF format, Qlik NPrinting cannot confirm whether the QlikView Desktop version installed locally on each Qlik NPrinting Engine is compatible with QVF file format. The check mark next to "QlikView can open the document" may be green, even if a version of QlikView that does not support QVF is installed. This is because verification only checks file permissions. If the installed QlikView Desktop does not support QVF format, metadata generation will fail.
Jira issue ID: OP-95682
QlikView objects with many different fields with exactly the same label are not supported. Duplicated labels cause an exception during the connection cache generation. To solve this issue, ensure that each field has a unique label.
Jira issue ID: OP-95797
Images linked by using URLs in Qlik Sense tables are exported as text. This affects only Qlik Sense connections. A workaround exists for PixelPerfect templates.
Jira issue ID: HLP-17139
The sensitivity labels feature in Microsoft Office is not supported. If used, report generation and preview will fail with errors.
As a workaround to the issue, block the Active Directory domain policy that pushes the sensitivity labels requirement to domain users.
To upgrade to Qlik NPrinting February 2025 SR7, you must start from one of the following versions:
Note that the minimum starting version for a direct update has changed, starting from February 2025 SR2 (25.5.8).
If you are using a version older than May 2022 (22.15.2) you must first upgrade to a version from May 2022 (22.15.2) to February 2025 SR1 (25.5.5). You can then upgrade to the current version. Skipping this step will stop the installation process with an error message that the upgrade is not supported. Your installation will not be modified or broken in this case and you will be able to continue following the correct procedure.
To upgrade directly to Qlik NPrinting May 2022 (22.15.2), you must start from one of the following versions:
If you have a version of Qlik NPrinting older than April 2018, you must first upgrade to Qlik NPrinting April 2018 before you can upgrade to Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting February 2025 SR7.
If you have a version of Qlik NPrinting older than 17.3, you must first upgrade to Qlik NPrinting 17.3. Then you must upgrade to a version from April 2018 to May 2021 SR4 before you can upgrade to Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting February 2025 SR5.
If you are upgrading from a version older than February 2018, all metadata caches (QlikView and Qlik Sense) will be marked as "not generated". This is due to a breaking change in the format of the metadata cache. All connection caches must be regenerated before you can edit a template or create a new connection.
You must back up your data before you proceed. Data can become damaged if a problem occurs during the upgrade. If data is damaged, a backup is required to restore the repository. See: Backup and restore of a repository
After backup, you must follow the instructions for upgrading on the help site page Qlik NPrinting upgrade.
If you are upgrading to February 2025 SR7 from September 2018 SR2 or older you must:
• Open port 4997 outbound on Qlik NPrinting Server and inbound on all Qlik NPrinting Engines.
• Reinstall all your Qlik NPrinting Engines and provide a password for certificate exchange.
• Open the Engine manager in the Web Console.
• Open the detail page for each Engine and send the certificate after inserting the same password you used during the engine’s reinstallation.
Qlik NPrinting Engines stay offline until the certificate exchange is performed. Older Engine versions cannot connect to a Qlik NPrinting February 2025 SR6 Server.
Setups are available at https://community.qlik.com/t5/Downloads/tkb-p/Downloads
About Qlik
| Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive. |
Qlik Alerting now allows configuring a Microsoft 365 email provider using OAuth2
Added support for MongoDB 8, Node JS 24
The August 2026 release of Qlik Alerting adds a required shared encryption key for multi-node deployments: all nodes now use one master key stored on a shared network folder to keep credentials, certificates, and license data in sync, and this requires the servers to be part of a common Active Directory domain. Customers upgrading an existing multi-node setup should review the updated guide before adding or reinstalling nodes, since the key-sharing step is now part of the installer flow.
This release includes support for Android 16 (API level 36), updates to third party and internal dependencies.
Download this release from the respective App Store / Play Store
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of GeoAnalytics Server released in May 2025, SR1. For questions or comments, post in the Product Forums or contact Qlik Support.
Dependencies have been updated.
| Key | Title | Description |
| QCB-35593 | Vulnerable Jetty version | Upgraded Jetty libraries to the version 12.1.12 in order to get the latest security fixes. |
| QCB-33617 | Fixed servlet error handling | For some internal exceptions the error page show would leak information about the server internals. This is now fixed and such exceptions will just show a generic error message. |
None at the time of release.
Requires Java 21 or newer.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of GeoAnalytics Server released in May 2026, SR1. For questions or comments, post in the Product Forums or contact Qlik Support.
Dependencies have been updated.
| Key | Title | Description |
| QCB-35593 | Vulnerable Jetty version | Upgraded Jetty libraries to the version 12.1.12 in order to get the latest security fixes. |
None at the time of release.
Requires Java 25 or newer.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
This release includes several fixes, updates to third party and internal dependencies.
Download this release from the respective App Store / Play Store
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover version 2.4.0 of the Qlik Analytics Migration Tool. For questions or comments, post in the Product Forums or contact Qlik Support.
This version allows to migrate Word and PowerPoint report templates from Qlik NPrinting installations running version May 2026.
Qlik NPrinting recently started supporting the export of Word and PowerPoint reprot templates to migrate them into Qlik Cloud.
With this release, Qlik Analytics Migration Tool includes those template formats among those migrated.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover version 2.3.0 of the Qlik Analytics Migration Tool. For questions or comments, post in the Product Forums or contact Qlik Support.
This version embeds the QlikView to Qlik Sense Converter Tool in the migration of QlikView Documents.
Why use it?
Allows to convert, migrate, modify script, assign ownership, reload and publish QlikView Documents into Qlik Cloud under the governed and structured workflow in the Qlik Analytics Migration Tool.
Conversion configuration and preview in Qlik Cloud are available and once the right configuration is found, it is possible to apply it to several Documents, or settings can be configured individually.
Conversion logs and reports are available as in the standalone tool.
All the components are included in the installer, no need for extra installations or licenses.
Logging has been extended to further support troubleshooting. Wording and minor usability improvements have been added.
The limitations of the QlikView to Qlik Sense Converter are described in its Help Page.
A new install is required to use this version.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
The following release notes cover the versions of QlikView released in September 2025.
Added a feature for ease-of-administration
In the QlikView Management Console, you will now be able to see any non-default settings that has been applied for the QlikView Server Service, just as you have been able to see them for the other services since QlikView 12.30.
Version upgrade of Skia to version 121.0.0.0
|
Key |
Title |
Decription |
|
QV-25497 |
FQDN for leasing license by setting “CustomLicenseServiceUrl“ env. |
New setting the “CustomLicenseServiceUrl“ is set with FQDN and overwrites "LicenseServiceUrl" env value on restart services. |
|
QV-25479 |
Alternate state value not retained when exporting |
This change fixes an issue when a user prints an object in AJAX, the object's alternate state is not restored. This means the printed report wrongly includes Current Selection in Default State instead. |
|
QV-25377 |
QlikView: Authentication redirect filtering not working |
The QlikView Authentication redirect filtering has now been fixed and is working correctly. |
|
QV-25376 |
QlikView: License tracking events not captured |
QlikView report license tracking and CAL events are now captured in the Event log. |
|
QV-25375 |
QlikView: Publisher function missing |
Fixed a problem that caused the Publisher function to disappear in the QMC |
|
QV-25371 |
QlikView: Cannot open files on server from QlikView desktop |
Fixed a problem where the files could not be opened on server from QlikView Desktop if the .qvw extension was in mixed casing or if it occurred more than once. |
|
QV-25347 |
QlikView: WebView not working on desktop when QVS has SSL enabled |
Fixed a problem that caused WebView to fail in QlikView desktop when QVS has SSL enabled in the same system. |
|
QV-25339 |
QlikView: Wrong value displayed in popup label |
Fixed a problem that caused the popup label to display the wrong value for bar charts with two expressions and no dimensions. |
|
QV-25323 |
QlikView Publisher: Additional lines added to the log file |
Fixed a problem that caused, for every task reload, an additional four lines to be added to the log file named with the current date. |
|
QV-25189 |
Unexpected selections, freezing, or disconnection |
Adjusted alt vector re-calculation not to impact cardinality of result |
|
QCB-32291 |
<CreatorDoc> tag in QVD files created with STORE empty |
Fixed a problem where the <CreatorDoc> tag in the metadata header of QVD files created with the STORE statement was empty. It is now written correctly. |
|
QCB-32144 |
Improved Alternate State Selections After Server Reloads |
We've resolved an issue that affected applications using Alternate States in server environments. Previously, after a server reload, selections in Alternate States were not correctly reapplied. Now, field selections in Alternate States are consistently maintained and correctly propagated after server reloads. |
|
QCB-31582 |
Fixed: Data Reload Issue Causing Unresponsive Behavior |
We've resolved an issue where certain data reload operations could become unresponsive, potentially causing the system to appear frozen. This problem occurred when using specific data processing functions together. |
|
QCB-31540 |
QlikView: Fixed black background color export to Excel |
We've resolved an issue in QlikView where the black background color was not correctly exported to Excel. With this fix, tables exported from QlikView to Excel now correctly display the black background color. |
|
QCB-31441 |
Table Box: Added sort option for columns in Ajax and QlikView Cloud |
Users can now sort columns in Table Boxes when using Ajax and QlikView Cloud. |
The following issues and limitations were identified at release time. The list is not comprehensive; it does however list all known major issues and limitations.
Limitations
None known at time of release
If a standard Upgrade is done, new certificates will be created using the AES 256
GCM mode as part of the upgrade.
Instructions for upgrading QlikView with new certificates mode (GCM) – Before implementing this, TLS 1.2 has to be enabled for QVS to work normally.
Perform the upgrade on all machines in the cluster.
After completion, the installer will ask you to restart the machine/s.
After restart and services are running, stop all the services and open "C:\Program Files\QlikView\Management Service\QVManagementService.exe.config" and apply the following config:
<add key="InstallingNewCertificatesAndCryptoKey" value="true"></add>
If Services are clustered, all the cluster nodes also need the new certificate.
Add into resp config files for each (one on each node):
<add key="InstallingNewCertificatesAndCryptoKey" value="true"></add>
or
InstallingNewCertificatesAndCryptoKey=1 if QVS.
Start the QMS first and then rest of all services
In the QMC, go to the service’s System/setup, for example if QDS select the node and distribute the new certificates to QDS machine with Apply in setup and follow the popup instructions. Do this for one service om each node to distribute new certs mode. Stop QMS again and all services. Make above configuration false in all config/settings files
"<add key="InstallingNewCertificatesAndCryptoKey" value="false"></add>".
Start all services. All machines in the cluster shall now have the new certs mode.
If you for some reason need to downgrade to the previous version again, follow this
Support Article to re-generate certificates using the old encryption algorithm.
The system requirements for this release can be found under “System requirements” on the Qlik help web site. https://help.qlik.com/en-US/qlikview/September2025/Content/QV_HelpSites/System-requirements.htm
https://community.qlik.com/t5/Product-Downloads/tkb-p/Downloads
|
Key |
Title |
Description |
|
QCB-33101 |
Missing QvConnect32 connector |
The QvConnect32 connector was missing in Qlikview server bundle due to change of build paths where the path to QvConnect32 pointed to wrong folder. |
|
QCB-32937 |
Bar chart printing fixed in Access Point |
We've resolved an issue with bar chart printing in Access Point. Previously, when using alternate states and expression conditionals, bar chart data didn't print correctly. This update ensures accurate printing of bar charts with these features. |
|
QCB-32926 |
Window Functions: Improved Handling of Calculated Fields
|
We've resolved an issue with Window Functions. Previously, fields calculated in a preceding load statement were not properly recognized by Window Functions, causing them to be incorrectly interpreted as null values. |
|
QCB-32885 |
QlikView Window function: Improvements |
Several enhancements to the Window function have been implemented and are now enabled by default in QlikView. |
|
QCB-32690 |
Excel Export: Option for Mixed Data Export
|
To choose how to export mixed data, use the setting 'ExcelExportMixedAsText'. It is set to 1 by default, to export mixed data exported as text. Set to 0 to export mixed data as integers. |
https://community.qlik.com/t5/Product-Downloads/tkb-p/Downloads
|
Key |
Title |
Description |
|
QCB-34453 |
QlikView Desktop: Intermittent crash with open document |
Qlikview Desktop and Batch would occasionally crash when the application was closed with an open document. This issue has been resolved. |
https://community.qlik.com/t5/Product-Downloads/tkb-p/Downloads
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
This release includes updates to expose Intune policy status in the app’s About screen. It also contains several improvements to the app, including security enhancements and dependent component upgrades.
Download this release from the respective App Store / Play Store
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of Qlik Gold Client released in May 2026. For questions or comments, post in the Product Forums or contact Qlik Support.
Patch 01 Transport GCSK900356
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
Learn about new features and improvements in Qlik Replicate.
This section describes the issues that you may encounter when upgrading/migrating to the new version.
Qlik supports four Replicate versions (including this one).
Direct upgrade is supported from the last two versions only (including any service releases for those versions). The last two versions are Replicate May 2025 and Replicate November 2025.
Note: When upgrading, select All releases and all patches on the Downloads page to see all the available versions. The upgrade paths below refer to initial versions, but the upgrade path is identical for SR versions as well.
If you are upgrading from Replicate April 2020 (6.6), you need to perform the following upgrades:
If you are upgrading from Replicate 6.x (starting from 6.3), you need to perform the following upgrades:
Note: If you are upgrading from Replicate 5.5, please contact Qlik Support.
When upgrading a Replicate installation with multiple Data folders, only the default Data folder (<Product_Dir>\Data) will be automatically upgraded. The other Data folders need to be updated manually by running the following command:
repuictl.exe -d <data_folder_path> setup install
This version of Replicate is compatible with the following related products only:
This section describes all issues resolved since the Replicate November 2025 initial release.
The following issues have been resolved in the Replicate May 2026 Service Release 1:
Jira issue: RECOB-12009
Salesforce case: 464058
Type: Issue
Component/Process: SAP HANA (Full Record mode) Source
Description: The before-image part of UPDATE operations is not replicated.
Jira issue: RECOB-11926
Salesforce case: 466188
Type: Issue
Component/Process: Global Transformation
Description: A Change Tables name redefinition rule configured before Replicate 2025.11 causes an additional suffix to be added incorrectly to the name; backward compatibility is provided under a Feature Flag.
Jira issue: RECOB-11948
Salesforce case: N/A
Type: Issue
Component/Process: IMS Source
Description: Endpoint improvements.
Jira issue: RECOB-11961
Salesforce case: 450936
Type: Issue
Component/Process: SAP HANA Source (Log based)
Description: Fatal error “Could not find an active root key in the BACKUP root key backup” occurs when LSS encryption module is used by SAP HANA.
Jira issue: RECOB-11992
Salesforce case: 469832
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: Task might incorrectly stop with a recoverable error “End of log wait limit of 900 seconds exceeded”.
Jira issue: RECOB-11867
Salesforce case: N/A
Type: Issue
Component/Process: SAP HANA (Full Record mode) Source
Description: After a task resumes, some changes that had been replicated before the task stopped might be replicated a second time, causing Apply Conflicts in the target.
Jira issue: RECOB-11855
Salesforce case: 454879
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: AR_H_DB_COMMIT_TIMESTAMP is different between Replicate and Oracle GoldenGate.
Jira issue: RECOB-11950
Salesforce case: 454102
Type: Issue
Component/Process: Parallel Load
Description: A key is not created in Target tables in "Create primary key or unique index after full load completes" mode.
Jira issue: RECOB-11917
Salesforce case: 466188
Type: Issue
Component/Process: Replicate Upgrade
Description: When an endpoint uses the password provider add-on, its password must be redefined after an upgrade from version 2024.11 and below.
Jira issue: RECOB-11895
Salesforce case: 456375
Type: Issue
Component/Process: PostgreSQL Target
Description: An endless Detach/Attach loop occurs when bidirectional replication is configured, and a duplicated record is detected in a PostgreSQL table.
Jira issue: RECOB-11613
Salesforce case: N/A
Type: Issue
Component/Process: IMS Source
Description: Full Load stuck for:
Jira issue: RECOB-11914
Salesforce case: 458545
Type: Issue
Component/Process: Sorter
Description: A memory leak might occur in “TS_FILE_READER” memory pool.
Jira issue: RECOB-11922
Salesforce case: 458556
Type: Issue
Component/Process: Replicate Engine
Description: When “Store task recovery data in target database” is enabled in the Batch Optimized mode, and Oracle target is used, task might crash after resuming.
Jira issue: RECOB-11886
Salesforce case: 463923
Type: Issue
Component/Process: Databricks (Cloud Storage) Target
Description: Binary zeros in character values are replaced by a space.
Jira issue: RECOB-11775
Salesforce case: 453622
Type: Issue
Component/Process: SAP ODP
Description: After an upgrade of the Replicate version, Resume Task might fail with the error “Selection enhances the delta in more than one dimension”.
Jira issue: RECOB-10870
Salesforce case: 452095
Type: Issue
Component/Process: SAP ODP (CDS View)
Description: The capture process might fail with a delta-queue error (SAP error 666/001).
Jira issue: RECOB-11880
Salesforce case: 458125
Type: Issue
Component/Process: SAP HANA Source (Log based)
Description: The capture process might stop with a fatal error reporting that the backup file cannot be opened.
Jira issue: RECOB-11820
Salesforce case: 448575
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: When an alternate backup folder is configured using a Direct Read, a task might stop with a fatal error:
Jira issue: RECOB-11894
Salesforce case: 465060
Type: Issue
Component/Process: Microsoft SQL Server (MS-CDC) Source
Description: Timestamp columns are not exposed.
Jira issue: RECOB-11308
Salesforce case: N/A
Type: Issue
Component/Process: Transformation
Description: Table key manipulations might result in an incorrect key definition.
Jira issue: RECOB-11817
Salesforce case: N/A
Type: Issue
Component/Process: IBM DB2 LUW for Target
Description: When Replicate is installed on Linux and a DB2 server on Windows, tables that contain LOB columns are suspended when a task is configured for Limited LOB support.
Jira issue: RECOB-11883
Salesforce case: 448179
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: When the AES XTS method is used for Redo Logs encryption in Oracle 26ai, the decryption process might be corrupted, causing unpredictable results.
Jira issue: RECOB-11182
Salesforce case: 443266
Type: Issue
Component/Process: Replicate installation
Description: RPM installation fails when the prefix or the data folder name contains dot (‘.').
Jira issue: RECOB-11834
Salesforce case: 455055
Type: Issue
Component/Process: IBM DB2 for z/OS Source
Description: The DB2 command START TRA( MON) invoked by Replicate might fail because of an invalid symbol in the configuration setting.
Jira issue: RECOB-11527
Salesforce case: 453693IMS
Type: Issue
Component/Process: Sorter
Description: $AR_H_USER is not evaluated for cached events.
Jira issue: RECOB-11838
Salesforce case: 448179
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: The capture process might stop due to a recoverable error, without a clear error message, when trying to open an Online Redo Log from ASM.
Jira issue: RECOB-11828
Salesforce case: 461579
Type: Issue
Component/Process: SAP Application (DB)
Description: The task would crash during LOB Lookup in rare scenarios.
Jira issue: RECOB-11783
Salesforce case: 455053
Type: Issue
Component/Process: SAP Application (DB)
Description: The task would crash during LOB Lookup when the order of columns in SAP transparent table and in the corresponding backend table was different.
Jira issue: RECOB-11714
Salesforce case: 458171
Type: Issue
Component/Process: Databricks Delta target
Description: During parallel load, tables would sometimes be suspended due to a COPY_INTO_DUPLICATED_FILES_COPY_NOT_ALLOWED Databricks Delta error.
Jira issue: RECOB-11794
Salesforce case: 457699
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: A permission error would occur when using DBCC PAGE SQL SERVER request if the task user was not a sysadmin.
Jira issue: RECOB-11826
Salesforce case: 462564
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: When capturing from a STANDBY Oracle environment, an Online Redo Log would sometimes be skipped following the info message “RAC instance ‘unknown’ (thread <>) is closed”.
Jira issue: RECOB-11557
Salesforce case: 451124
Type: Issue
Component/Process: IBM DB2 for LUW Target
Description: CDC data truncation would not be reported.
Jira issue: RECOB-11753
Salesforce case: N/A
Type: Issue
Component/Process: Snowflake Target
Description: A truncation error would sometimes be reported in Net Changes table for VARIANT columns.
Jira issue: RECOB-11707
Salesforce case:
Type: Issue
Component/Process: SAP HANA (Full Record mode) Source
Description: QTREP/TRAN_LOG table would not be part of the cleanup process and therefore could grow to more than a billion records, causing trigger failures.
Jira issue: RECOB-11749
Salesforce case: 461387
Type: Issue
Component/Process: Google BigQuery Target
Description: Task batches would be uploaded containing only one change, which would cause huge latency.
Jira issue: RECOB-11770
Salesforce case: 457311
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: The capture process would sometimes miss primary key column values when UPDATE operations were performed on compressed rows, causing NULL values in the target.
Jira issue: RECOB-11689
Salesforce case: 452390
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: The task would fail with a recoverable error because the configured alternate backup folder name was changed to uppercase and could not be found as a result.
Jira issue: RECOB-11734
Salesforce case: 455275
Type: Issue
Component/Process: Databricks (Cloud Storage) Target
Description: Binary zero in character values would be replaced by a space.
Jira issue: RECOB-11346
Salesforce case: 449927
Type: Issue
Component/Process: SAP OData Source
Description: Table Full Load might not complete after the corresponding SAP ODP job finishes.
Jira issue: RECOB-11568
Salesforce case: N/A
Type: Issue
Component/Process: MongoDB Source
Description: The “Avoid scientific notation” settings for Double and Decimal128 data types would have no effect.
Jira issue: RECOB-11447
Salesforce case: 435853
Type: Issue
Component/Process: SAP ODP Source
Description: Full Load performance would be slow when the captured table list contained many patterns.
Jira issue: RECOB-11536
Salesforce case: N/A
Type: Issue
Component/Process: Log Stream Source
Description: Log Stream would not report the description of input events in Verbose mode.
Jira issue: RECOB-11687
Salesforce case: 458626
Type: Issue
Component/Process: Fabric Mirroring Target
Description: In transactional mode, Replicate would cause duplication on cached events.
Jira issue: RECOB-11578
Salesforce case: 453506
Type: Issue
Component/Process: SAP HANA Source
Description: When a source table was shared between two replication tasks and removed from one of them, the triggers supporting CDC would be incorrectly dropped, causing the remaining task to stop capturing changes from that table.
Jira issue: RECOB-11573
Salesforce case: 451122
Type: Issue
Component/Process: Databricks Delta Target
Description: In character columns, binary zero would be replaced by space, causing incorrect data to be replicated.
Jira issue: RECOB-11661
Salesforce case: 453047
Type: Issue
Component/Process: Oracle Source - General
Description: The task would fail with ORA-1406 when QUERY HIGH ROW LEVEL LOCKING compression was defined on one of the captured tables.
Jira issue: RECOB-11472
Salesforce case: N/A
Type: Issue
Component/Process: SAP HANA (Log based) Source
Description: Rollback-To-Savepoint HANA operations would not be supported correctly; that would sometimes cause incorrect changes to be replicated.
Jira issue: RECOB-11614
Salesforce case: N/A
Type: Issue
Component/Process: IMS Source
Description: Log Stream would not be supported.
Jira issue: RECOB-11655
Salesforce case: 457306
Type: Issue
Component/Process: DB2 z/OS Source
Description: The task would sometimes stop capturing changes without any notification.
Jira issue: RECOB-11646
Salesforce case: 447792
Type: Issue
Component/Process: SAP Application (DB) Source
Description: Events would be missing as a result of the Detach/Attach of a Target Apply component.
Jira issue: RECOB-11618
Salesforce case: N/A
Type: Issue
Component/Process: IBM DB2 for LUW Target
Description: Some error messages would not correspond to Replicate UI terminology.
Jira issue: RECOB-11616
Salesforce case: 448930
Type: Issue
Component/Process: Amazon S3 Target
Description: All timestamp fields in Parquet format are be marked as UTC.
Jira issue: RECOB-11440
Salesforce case: 446492
Type: Issue
Component/Process: SAP HANA source
Description: Using Trigger Based mode, SAP HANA DECIMAL CS_DECIMAL_FLOAT data type would be exposed as Number (34,0), resulting in the scale part of values not being replicated.
Jira issue: RECOB-11567
Salesforce case: N/A
Type: Issue
Component/Process: Microsoft Fabric
Description: A table would sometimes be suspended when the “Minimum number of changes per transaction” was configured to a small value and a huge number of small transactions were captured during a short interval.
Jira issue: RECOB-11608
Salesforce case: 457311
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: The capture process for Update operations on compressed rows would sometimes miss a primary key column value, causing a NULL value to be used in the target.
Jira issue: RECOB-11562
Salesforce case: N/A
Type: Issue
Component/Process: BigQuery Target
Description: The task would sometimes fail with the exception “PERMISSION_DENIED: Table identity changed during the call”.
Jira issue: RECOB-11385
Salesforce case: 388202
Type: Issue
Component/Process: Sorter, SAP DB
Description: When a table was reloading, data problems and warnings would sometimes occur with other tables.
Jira issue: RECOB-11511
Salesforce case: N/A
Type: Issue
Component/Process: Amazon Redshift Target
Description: Column length DDL operations would not support changes.
Jira issue: RECOB-11380
Salesforce case: N/A
Type: Issue
Component/Process: MySQL Target, Azure MySQL Target, Google Cloud MySQL Target
Description: Directories from which data files could be uploaded via LOAD DATA LOCAL INFILE were not restricted, allowing potential file read vulnerabilities in compromised database servers.
Jira issue: RECOB-11478
Salesforce case: 447726
Type: Issue
Component/Process: PostgreSQL Target
Description: Full Load would fail with the “The access token has expired” error message when working with Azure Active Directory Service Principal authentication.
Jira issue: RECOB-11141
Salesforce case: 432202
Type: Issue
Component/Process: SAP HANA trigger based
Description: The log table (V2) mode using V1 triggers would fail with the error “Bad event rowid and operation” after an upgrade, or when, in rare unpredictable situations, SAP HANA would not assign the application user value.
Jira issue: RECOB-11383
Salesforce case: 433464
Type: Issue
Component/Process: PostgreSQL Source
Description: If the Capture component Metadata connection was disconnected when the main data connection continued working and a new partition was added to a captured table, changes belonging to the new partition would be missed.
Jira issue: RECOB-11322
Salesforce case: 423018
Type: Issue
Component/Process: SAP Extractor
Description: Duplicate records would be replicated when resuming Replicate task after SAP extraction job cancellation.
Jira issue: RECOB-11315
Salesforce case: 434250
Type: Issue
Component/Process: SAP Application
Description: SAP CLOB columns (ABAP type ‘g’) would not be converted from the original UTF-16 codepage to the exposed UTF-8 codepage, causing data to be replicated incorrectly.
Jira issue: RECOB-11514
Salesforce case: N/A
Type: Issue
Component/Process: IMS Source
Description: Reload of virtual tables would fail when the task was capturing changes for the relevant database (DBD).
Jira issue: RECOB-11373
Salesforce case: N/A
Type: Issue
Component/Process: IMS Source
Description: If an error happened during Parallel Load mode, it would be reported as a CDC error.
Jira issue: RECOB-11432
Salesforce case: N/A
Type: Issue
Component/Process: IBM DB2 LUW for Target
Description: Parallel Load mode is not supported but could have been configured in UI.
Jira issue: RECOB-11127
Salesforce case: N/A
Type: Issue
Component/Process: Replicate Engine
Description: JAVA Endpoints would not support Start-From-Timestamp and Start-From-Position task start modes.
Jira issue: RECOB-11408
Salesforce case: N/A
Type: Issue
Component/Process: Databricks Delta
Description: A table would be suspended when the length of one of its columns was enlarged in the task source.
Jira issue: RECOB-11268
Salesforce case: N/A
Type: Issue
Component/Process: Databricks Lakehouse (Delta), Databricks (Cloud Storage)
Description: Connection to proxy with username and password would fail after upgrading the ODBC driver according to Replicate 2026.5 documentation.
Jira issue: RECOB-11260
Salesforce case: 445792
Type: Issue
Component/Process: Teradata Target
Description: A table would be suspended if the target table contained more columns than the source manipulated table.
Jira issue: RECOB-11424
Salesforce case: N/A
Type: Issue
Component/Process: Microsoft SQL Server Source
Description: Task process would fail with a recoverable error (connection timeout) when DBCC call was used after a long time.
Jira issue: RECOB-11420
Salesforce case: 446522
Type: Issue
Component/Process: PostgreSQL Source
Description: LOB Lookup would not be able to retrieve LOB column values when one of the key columns was TIMESTAMPTZ.
Jira issue: RECOB-11603
Salesforce case: 447028
Type: Issue
Component/Process: Salesforce Source
Description: If ID was not the first table column, it would be replicated incorrectly into another column.
Jira issue: RECOB-11377
Salesforce case: 443318
Type: Issue
Component/Process: UI
Description: It was not possible to update the Maximum Retry Count in the Environment Error Handling policy.
Jira issue: RECOB-11489
Salesforce case: N/A
Type: Issue
Component/Process: Microsoft Fabric Target
Description: Changes would not be propagated to the Control Tables.
The following issues have been resolved in the Replicate May 2026 initial release:
Jira issue: RECOB-11251 Salesforce case: 430619
Type: Issue
Component/Process: Oracle Source - Replicate Log Reader
Description: In rare scenarios, an UPDATE operation might not capture an after-image value of one or more starting columns in a wide table.
Jira issue: RECOB-11215
Salesforce case: 441160
Type: Issue
Component/Process: Amazon RDS for MariaDB source
Description: Connecting to Amazon RDS for MariaDB with TLS 1.3 would fail.
Jira issue: RECOB-11197
Salesforce case: 418337
Type: Issue
Component/Process: Global Transformation
Description: Any global column transformation would remove the original endpoint column subtype of JSON and XML.
Jira issue: RECOB-10689
Salesforce case: 393670
Type: Issue
Component/Process: Security
Description: SQLite versions were upgraded to 3.51.1 due to a known vulnerability with earlier versions.
Jira issue: RECOB-10213
Salesforce case: 397801
Type: Issue
Component/Process: SAP ODP source
Description: The SAP ODP filter would not be passed to SAP when defined on an extractor running in CDC-only mode.
Jira issue: RECOB-10213
Salesforce case: 397801
Type: Issue
Component/Process: SAP ODP source
Description: The SAP ODP filter would not be passed to SAP when defined on an extractor running in CDC-only mode.
Jira issue: RECOB-10361
Salesforce case: 403874
Type: Issue
Component/Process: Notifications
Description: Test notification email would not allow the “+” sign.
Jira issue: RECOB-11122
Salesforce case: 414220
Type: Issue
Component/Process: IBM DB2 for LUW source + File target
Description: Some UPDATEs would be missing when replicating a VARCHAR column.
Jira issue: RECOB-11123
Salesforce case: 396347
Type: Issue
Component/Process: IBM DB2 for iSeries source
Description: After resuming a task, capturing changes from a table that contained binary decimal columns would cause the task to crash.
Jira issue: RECOB-11159
Salesforce case: 423853
Type: Issue
Component/Process: Sybase target
Description: Truncate table would not be performed within a multi-statement transaction.
Jira issue: RECOB-11158
Salesforce case: 416046
Type: Issue
Component/Process: Sybase target
Description: When a table on the target was defined with cluster primary key, duplicate records would cause the task to enter an endless recoverable error instead of handling it as a standard duplication error.
Jira issue: RECOB-11148
Salesforce case: 438331
Type: Issue
Component/Process: IBM DB2 for z/OS source
Description: Failure to communicate with the source database would be handled as a FATAL error in a very specific scenario.
Jira issue: RECOB-11134
Salesforce case: 442203
Type: Issue
Component/Process: Task import
Description: Importing a task would fail for task names exceeding 32 characters.
Jira issue: RECOB-11085
Salesforce case: 439592
Type: Issue
Component/Process: Task import
Description: The repctl gettaskstatus command requires the monitor_data parameter instead of it being optional.
Jira issue: RECOB-11084
Salesforce case: 439984
Type: Issue
Component/Process: Snowflake target
Description: The task would sometimes fail with a timeout error during the "COPY INTO" phase.
Jira issue: RECOB-11046
Salesforce case: 440089
Type: Issue
Component/Process: Snowflake target with Snowpipe Streaming
Description: When using Snowpipe Streaming as the loading method, loading very large tables would consume an excessive amount of memory, which would eventually result in the task crashing and entering a loop of loading and crashing.
Jira issue: RECOB-11039
Salesforce case: 437801
Type: Issue
Component/Process: Amazon Redshift target
Description: VARBYTE column in Redshift appears as a BLOB
Jira issue: RECOB-11010
Salesforce case: 437226
Type: Issue
Component/Process: Microsoft SQL Server source
Description: When specifying an Alternate backup folder which did not contain the required logs, the task would stop with an unclear message instead of issuing a warning an continuing.
Jira issue: RECOB-10997
Salesforce case: 430021
Type: Issue
Component/Process: Microsoft Fabric Target – Mirrored Database
Description: Tables would sometimes be suspended with the following error:
No data rows available
Jira issue: RECOB-10996
Salesforce case: 436142
Type: Issue
Component/Process: Microsoft SQL Server source
Description: The task would sometimes crash while reading the transaction log backup.
Jira issue: RECOB-10995
Salesforce case: 437152
Type: Issue
Component/Process: Snowflake target
Description: The Snowflake hostname for China account (.cn) would not work.
Jira issue: RECOB-10983
Salesforce case: 435943
Type: Issue
Component/Process: Table transformation
Description: Table transformation would cause the table key columns to be ordered incorrectly, even if the index was not changed in the manipulation.
Jira issue: RECOB-10970
Salesforce case: 432837
Type: Issue
Component/Process: PostgreSQL source
Description: After resuming a task that did not capture any changes for the minute before it was stopped, no changes would be captured.
Jira issue: RECOB-10967
Salesforce case: 432391
Type: Issue
Component/Process: Kafka target
Description: Excessive memory consumption during the task, that steadily increases.
Jira issue: RECOB-10936
Salesforce case: 433474
Type: Issue
Component/Process: Amazon S3 target
Description: Corrupted data file would be treated as a recoverable error instead of a fatal table error.
Jira issue: RECOB-10933
Salesforce case: 430775
Type: Issue
Component/Process: Security
Description: The org.apache.logging.log4j:log4j-core component was upgraded to 2.25.3 due to known vulnerabilities with the installed versions.
Jira issue: RECOB-10930
Salesforce case: 435016
Type: Issue
Component/Process: Oracle source
Description: Incorrect 11.12 parsing of multi-delete operation would occur when a table was created with ROWDEPENDENCIES.
Jira issue: RECOB-10880
Salesforce case: 424255
Type: Issue
Component/Process: SAP HANA source
Description: Full record mode would sometimes not work properly with tables that contained numerous columns.
Jira issue: RECOB-10878
Salesforce case: 432913
Type: Issue
Component/Process: SAP ODP source
Description: Capture from CDS View would start failing after stopping and resuming the task.
Jira issue: RECOB-10869
Salesforce case: 417562
Type: Issue
Component/Process: SAP Extractor source
Description: CDC was aborted one hour after a table was reloaded, which caused the task to enter a recoverable error.
Jira issue: RECOB-10861
Salesforce case: 420989
Type: Issue
Component/Process: SAP Hana Log based CDC
Description: When capturing changes from partitioned tables, DELETE operations would sometimes fail at the target with a 'row not found' error.
Jira issue: RECOB-10856
Salesforce case: 404961
Type: Issue
Component/Process: Metadata run option
Description: After Stopping the task and using the “Recreate all tables” run option, the task would be resumed from NOW instead of the last LSN/LRI stream position.
Jira issue: RECOB-10853
Salesforce case: 428408
Type: Issue
Component/Process: Snowflake target
Description: After replicating to Snowflake, intermediate files on Replicate server would never be deleted.
Jira issue: RECOB-10805
Salesforce case: 427401
Type: Issue
Component/Process: Oracle source
Description: Clarification of the v$transaction permission in the help.
Jira issue: RECOB-10797
Salesforce case: 427417
Type: Issue
Component/Process: Engine
Description: When a user without CREATE SCHEMA permission tried to create an existing schema, an error would be returned incorrectly.
Jira issue: RECOB-10774
Salesforce case: 423114
Type: Issue
Component/Process: Microsoft SQL Server source
Description: The task would sometimes crash after DBCC Lookup invocation.
Jira issue: RECOB-10773
Salesforce case: 427484
Type: Issue
Component/Process: Oracle source
Description: When a table contained a long raw and the maximum LOB size was greater than or equal to 64K, the task would crash.
Jira issue: RECOB-10748
Salesforce case: 420235
Type: Issue
Component/Process: Oracle source
Description: The table would be suspended if the limited LOB size value was changed and a DDL was detected.
Jira issue: RECOB-10667
Salesforce case: 421961
Type: Issue
Component/Process: MySQL-to-MySQL task
Description: When the schema of the source and target are in the same MySQL instance and a control table is included in the replication, the task would sometime fail with the following error:
Process crashed with signal 11
Jira issue: RECOB-10637
Salesforce case: 419699
Type: Issue
Component/Process: Amazon S3 staging
Description: During Full Load, tasks would sometimes fail with the following error due to the connection being actively refused by Amazon:
Unable to execute HTTP request: Connect to s3.amazonaws.com:443
The issue was resolved by implementing a retry mechanism with a maximum of three retries before the error occurs.
Jira issue: RECOB-10577
Salesforce case: 403115
Type: Issue
Component/Process: SAP extractor
Description: When using the internal parameter removeJobAfterTaskStop, failed tasks used the existing job run in SAP instead of initiating a new process, resulting in missing data on the target.
Jira issue: RECOB-10824
Salesforce case: 428945
Type: Issue
Component/Process: IBM Informix source
Description: The task would sometimes not recover automatically after database maintenance.
Jira issue: RECOB-10746
Salesforce case: 408429
Type: Issue
Component/Process: PostgreSQL target
Description: Failure to load the CSV file into the Net Changes table would return a recoverable error (resulting in an endless loop) instead of switching to one-by-one apply.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
Learn about new features and improvements in Qlik Enterprise Manager.
Before upgrading, it's important to review the migration and upgrade considerations below.
Qlik supports four Enterprise Manager versions (including this one).
Direct upgrade is supported from the last two versions only (including any service releases for those versions). The last two versions are Enterprise Manager May 2025 and Enterprise Manager November 2025.
Note: When upgrading, select All releases and all patches on the Downloads page to see all the available versions. The upgrade paths below refer to initial versions, but the upgrade path is identical for SR versions as well.
If you are upgrading from Enterprise Manager April 2020 (6.6), perform the upgrades in the following order:
If you are upgrading from Enterprise Manager 6.x (starting from 6.3), perform the upgrades in the following order:
If you are upgrading from Enterprise Manager 3.3, please contact Qlik Support.
Excluding Qlik Catalog May 2023 which requires SR2, this version of Enterprise Manager is compatible with the following related product versions and their service releases:
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of Qlik GeoAnalytics Plus released in May 2026. For questions or comments, post in the Product Forums or contact Qlik Support.
Java 25
GeoAnalytics Plus now requires Java 25 or newer.
None at the time of release.
Requires Java 25 or newer.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of Qlik GeoAnalytics Extensions for QlikView released in May 2026. For questions or comments, post in the Product Forums or contact Qlik Support.
Dependency updates.
Storytelling - a map or layer snapshot should only be added once per story, and combining an embedded sheet with snapshots from the same sheet is not supported.
Printing is not supported.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of GeoAnalytics Extensions for Qlik Sense released in May 2026. For questions or comments, post in the Product Forums or contact Qlik Support.
Dependency updates.
Storytelling - a map or layer snapshot should only be added once per story, and combining an embedded sheet with snapshots from the same sheet is not supported.
Printing is not supported.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover the versions of GeoAnalytics Server released in May 2026. For questions or comments, post in the Product Forums or contact Qlik Support.
Java 25
GeoAnalytics Server now requires Java 25 or newer.
| Key | Title | Description |
| QCB-33617 | Fixed servlet error handling | For some internal exceptions the error page show would leak information about the server internals. This is now fixed and such exceptions will just show a generic error message. |
| QCB-32817 | Calculated center point outside bounds for some smaller polygons | For some smaller polygons the calculated center point would end up outside the bounds of the geometry, which caused their popups to be placed incorrectly in the map chart. |
None at the time of release.
Requires Java 25 or newer.
Download this release from the Product Downloads page on Qlik Community.
About Qlik
Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive.
Table of Contents
The following release notes cover Qlik NPrinting February 2025 SR5 to SR6.
Jira issue ID: SUPPORT-8939
Erlang is updated to version is 27.3.4.11.
Jira issue ID: QCB-34788
PowerPoint reports are now generated correctly when a shape in the template is replaced with a table.
Jira issue ID: OP-10197
Resolved an issue where failures occurring while sending task notification emails were not reported in the logs. Previously, these failures were only visible in Audit data, and only when Audit was enabled.
The following issues and limitations were identified at release time. The list is not comprehensive; it lists all known major issues and limitations. We expect to have these issues fixed in future versions.
The following languages are supported:
Other languages are not officially supported. There may be issues with other languages, particularly those with right-to-left script and non-Roman alphabets.
Qlik Sense custom size sheets are not supported. Custom size will not be maintained on export.
Alternate states
QlikView and Qlik Sense alternate states are not supported.
QlikView and Qlik Sense alternate states are not supported.
Jira issue ID: OP-6196
Qlik NPrinting Server, Engine, and Designer can only be installed on C: drives. Any attempt to install them on a different drive will result in task failures.
Jira issue ID: OP-5831
When you add the same object twice, using the Images node in Qlik NPrinting Designer, only the image size property of the first image is respected.
It is possible to select the “Enable” check box in On-Demand for reports using Qlik Sense app data. These reports are visible in the QlikView On-Demand menu of the QlikView On-Demand add-on. But if selected, they will not generate reports, and you will see an error message.
If you experience random crashes when using Qlik NPrinting Designer, open your Windows Display Settings in the Control Panel and verify that Smaller – 100% (default) is selected. When settings of 125% or 150% are selected, Qlik NPrinting Designer may crash.
Jira issue ID: OP-5908
In some cases, when you use Qlik NPrinting On-Demand in Internet Explorer 11 or Edge, the “origin” HTTP header is not generated. This results in the error message “REVEL_CSRF: tokens mismatch”.
The workaround is to install Qlik NPrinting On-Demand on a Microsoft IIS server hosting QlikView Access point or use a different web browser.
Jira issue ID: OP-4940
Qlik NPrinting Designer may be unable to open a report template if there are too many filters associated with a connection in the report's app. The following error message displays: “A task was canceled”.
This typically happens when more than 4000 filters are using fields from a connection. Sometimes, higher numbers can work. For example, 7000 filters have worked in some situations.
The workaround is:
1. Split the Qlik NPrinting app into separate apps.
2. Split the connections (possibly by using multiple connections to the same documents in different apps).
3. Split the filters across apps (so that the filter count per app is lower).
Jira issue ID: OP-4839
Some Qlik NPrinting tasks fail with the error message: “Exceeded maximum number of retries”. This is due to a performance issue in QlikView that appears when it exports large unfiltered files to Excel.
Jira issue ID: OP-5278
In some rare circumstances, pressing the Verify connection button will cause the screen to freeze on the “Initializing…” status and the spinning wheel cursor. This happens when a Qlik NPrinting Engine goes offline and Verify connection is pressed before the Qlik NPrinting Scheduler is aware that it is offline. It can take up to 20 seconds before the Qlik NPrinting Scheduler determines the offline status of a Qlik NPrinting Engine.
Jira issue ID: OP-5914
When you:
The filters associated with each user are not uploaded, or displayed, for performance reasons. Waiting for all filters for thousands of users to import would take a long time. In most cases, importing this information is unnecessary, because filters created for users often contain something like the user IDs. You can change this behavior and make all filters visible by uncommenting the line <!--<add key="include-user-filters" />--> in the webengine.config file.
To make a specific filter visible in the lists, remove its association to all users, or create a new filter with the same fields and values not linked to any user.
Jira issue ID: OP-3986
The rollback that follows a Qlik NPrinting Server or Engine upgrade cancellation may corrupt the related Qlik NPrinting installation. A rollback is triggered by errors or by clicking the cancel button during the upgrade execution. After a corruption caused by a rollback, services may be uninstalled or cannot be started.
To restore a Qlik NPrinting Server to its original status:
You should always create a backup before starting an update. In any case, a backup is automatically created in the folder "%ProgramData%\NPrinting" at the beginning of the upgrade process. To restore a Qlik NPrinting Engine to original status:
Jira issue ID: OP-7560
Add title functionality is not supported on Qlik Sense objects with Assistance mode enabled. The workaround to restore the Add title functionality is to disable Assistance mode for the chart in Qlik Sense. Then reload the metadata of the connection.
Jira issue ID: OP-7568
Qlik Sense objects made in Assistance mode cannot be used as tables, columns, or cells in Qlik NPrinting. To restore them, disable Assistance mode on the chart in Qlik Sense; then reload the metadata of the connection. Furthermore, if a Qlik Sense object made with Assistance mode is exported as a table, column, or cell using Qlik NPrinting APIs, the request will fail.
Jira issue ID: OP-7165
Open Type Fonts (*.otf) are not supported in PixelPerfect templates. Generated reports will use a different font, and not look as expected.
Jira issue ID: OP-7747
The following functionalities are not supported for Qlik Sense tables that have a "Show column if" condition set on one or more of their columns: levels, single column export, and keep source formats.
Jira issue ID: OP-8382
Qlik Sense On-Demand reports with selections applied on calculated dimensions will fail. However, you can apply selections on dimensions based on Qlik Sense fields. The workaround is to move the formula to the load script and use the calculated fields to apply selections to your On-Demand reports.
Jira issue ID: OP-8985
Due to the internal way of exporting Qlik Sense histograms, you cannot add them to the Qlik NPrinting Designer Tables node. If you add a Qlik Sense histogram to the Tables node, you will not receive any errors or warning messages, but the exported data will be wrong.
Jira issue ID: OP-8921
QlikEntity reports support Qlik Sense objects with the following limitations:
Jira issue ID: OP-9087
You cannot embed an Excel worksheet in a PowerPoint report template. This will cause a Qlik NPrinting Designer crash. The workarounds are to insert the Excel worksheet without using the Qlik NPrinting Designer:
Jira issue ID: OP-9067
Dynamic views is a new Qlik Sense feature starting from June 2020.
If you connect Qlik NPrinting to a Qlik Sense app that contains a chart used to generate dynamic views, the chart and the containing sheet are excluded from the Qlik NPrinting connection cache and cannot be used in reports.
You can connect Qlik NPrinting to a Qlik Sense app containing dynamic views. However, after a dynamic view refresh, the connection will stop working.
Jira issue ID: OP-9628
Starting from November 2020, RabbitMQ Server (deployed as Qlik NPrinting Messaging Service) has been updated to version 3.8.3. It has an internal limit, not configurable, about messages size of 512MB. Previous limit was 2GB. As consequence, is not possible to generate Qlik NPrinting reports bigger than 512MB.
Jira issue ID: OP-9766
Excel worksheet print areas can contain more than one range if the generation of the report does not expand the print area. If it expands, you will see an error: “Invalid Cell Name”. For example, the default setting of the Expand Range option in a Qlik NPrinting table causes the print area to change during report production, and an error is received.
Jira issue ID: OP-9518
Using Cyrillic characters in the Search form of the Qlik NPrinting user interface is case sensitive.
Jira issue ID: OP-9995
The percentage “%” format is not kept in Excel reports when using QlikView 12.50 (12.50.20000) or newer due to a QlikView issue. You can solve this by upgrading to QlikView May 2021 SR2 (12.60.20200) or newer.
Jira issue ID: OP-95599
If you start a Run Verification on a connection to a QlikView document in QVF format, Qlik NPrinting cannot confirm whether the QlikView Desktop version installed locally on each Qlik NPrinting Engine is compatible with QVF file format. The check mark next to "QlikView can open the document" may be green, even if a version of QlikView that does not support QVF is installed. This is because verification only checks file permissions. If the installed QlikView Desktop does not support QVF format, metadata generation will fail.
Jira issue ID: OP-95682
QlikView objects with many different fields with exactly the same label are not supported. Duplicated labels cause an exception during the connection cache generation. To solve this issue, ensure that each field has a unique label.
Jira issue ID: OP-95797
Images linked by using URLs in Qlik Sense tables are exported as text. This affects only Qlik Sense connections. A workaround exists for PixelPerfect templates.
Jira issue ID: HLP-17139
The sensitivity labels feature in Microsoft Office is not supported. If used, report generation and preview will fail with errors.
As a workaround to the issue, block the Active Directory domain policy that pushes the sensitivity labels requirement to domain users.
To upgrade to Qlik NPrinting February 2025 SR6, you must start from one of the following versions:
Note that the minimum starting version for a direct update has changed, starting from February 2025 SR2 (25.5.8).
If you are using a version older than May 2022 (22.15.2) you must first upgrade to a version from May 2022 (22.15.2) to February 2025 SR1 (25.5.5). You can then upgrade to the current version. Skipping this step will stop the installation process with an error message that the upgrade is not supported. Your installation will not be modified or broken in this case and you will be able to continue following the correct procedure.
To upgrade directly to Qlik NPrinting May 2022 (22.15.2), you must start from one of the following versions:
If you have a version of Qlik NPrinting older than April 2018, you must first upgrade to Qlik NPrinting April 2018 before you can upgrade to Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting February 2025 SR6.
If you have a version of Qlik NPrinting older than 17.3, you must first upgrade to Qlik NPrinting 17.3. Then you must upgrade to a version from April 2018 to May 2021 SR4 before you can upgrade to Qlik NPrinting May 2022 (22.15.2) and then to Qlik NPrinting February 2025 SR5.
If you are upgrading from a version older than February 2018, all metadata caches (QlikView and Qlik Sense) will be marked as "not generated". This is due to a breaking change in the format of the metadata cache. All connection caches must be regenerated before you can edit a template or create a new connection.
You must back up your data before you proceed. Data can become damaged if a problem occurs during the upgrade. If data is damaged, a backup is required to restore the repository. See: Backup and restore of a repository
After backup, you must follow the instructions for upgrading on the help site page Qlik NPrinting upgrade.
If you are upgrading to February 2025 SR6 from September 2018 SR2 or older you must:
• Open port 4997 outbound on Qlik NPrinting Server and inbound on all Qlik NPrinting Engines.
• Reinstall all your Qlik NPrinting Engines and provide a password for certificate exchange.
• Open the Engine manager in the Web Console.
• Open the detail page for each Engine and send the certificate after inserting the same password you used during the engine’s reinstallation.
Qlik NPrinting Engines stay offline until the certificate exchange is performed. Older Engine versions cannot connect to a Qlik NPrinting February 2025 SR6 Server.
Setups are available at https://community.qlik.com/t5/Downloads/tkb-p/Downloads
About Qlik
| Qlik converts complex data landscapes into actionable insights, driving strategic business outcomes. Serving over 40,000 global customers, our portfolio provides advanced, enterprise-grade AI/ML, data integration, and analytics. Our AI/ML tools, both practical and scalable, lead to better decisions, faster. We excel in data integration and governance, offering comprehensive solutions that work with diverse data sources. Intuitive analytics from Qlik uncover hidden patterns, empowering teams to address complex challenges and seize new opportunities. As strategic partners, our platform-agnostic technology and expertise make our customers more competitive. |