Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in Manage Cases. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
This guide provides step-by-step instruction on how to create an UDC that fetches users from AD in the most common way: default Active Directory UDC. The steps use LDAP Admin for testing the LDAP filter string.
For steps that do not require LDAP Admin see Qlik Sense: Configuring and testing LDAP filters for User Directory Connector
For connecting AD using Generic LDAP connector, follow article How to connect to Active Directory using the Generic LDAP Connector
1. Confirm current server is Central Node and Repository Service is running correctly.
2. In order to confirm AD connectivity, download a 3rd party tool called "LDAP Admin" and run it on current server.
3. In LDAP Admin, create a connection.
4. For the detailed information, consult your Domain Administrator.
5. Make sure the connection passes test.
6. Once connected, go to Search > Custom > set "Path" to the top level > Input appropriate LDAP filter. Make sure there are some users fetched successfully.
For any issues happening before this point, please contact Domain Administrator. For any issues happening after this point, please contact Qlik Support.
[VERY IMPORTANT] Before moving forward, confirm if there is any RootAdmin assigned to a domain user in Qlik Sense.
If there is, make sure that user appears in the search result of above filter otherwise it will be marked as inactive and could potentially lock users out from QMC. Also follow How to avoid the RootAdmin(s) from becoming inactive. But this step should not be relied on so please still make sure the filter fetches current RootAdmin.
7. Go to QMC > User directory connector > Create new > Active Directory:
9. Hit Apply, go back and do a Sync. Confirm the Sync is successful.
10. Go to QMC > Users > Filter by "User directory". Confirm the users are fetched.
With content cache-controls, you can modify the cache behavior of the browser. The cache-control is used on endpoints handled by the repository service. This functionality is disabled by default and can be enabled by modifying the files Repository.exe.conf and capabilities.json, followed by a restart of the Qlik Sense Service Dispatcher and the Qlik Sense Repository Service.
Cache-control for endpoints handled by the repository service was introduced in Qlik Sense Enterprise on Windows February 2022 (Patch 1). In the May 2022 release further enhancements were made to extend caching policies for requests specific to the Hub service. Upgrade Qlik Sense to make use of the new features.
In this article, we walk you through modifying the cache control policy and how to apply it globally across your Qlik Sense Enterprise on Windows environment.
Please note the following before modifying cache control headers:
Prior to applying any changes in a production environment, evaluate the risks of the changes.
The feature is disabled by default. For details, see Configuring content cache-control.
These are the predefined cache-control header values:
"CachePolicyEnum": { "values": [ "0: Normal", -> public, max-age=3600 "1: MustRevalidate", -> public, must-revalidate, max-age=0 "2: PrivateNormal", -> private, max-age=3600 "3: PrivateMustRevalidate", -> private, must-revalidate, max-age=0 "4: NoStore" -> no-store ] }
You can create a global cache control policy (not tied to a content library) by using either the API or an SQL query against the QRS database. A restart of the Qlik Sense Service Dispatcher and Qlik Sense Repository service is required after.
API example:
POST /qrs/ContentCacheControl
{ "id": "e07ca071-7d72-417d-93c2-d60687f747a8", "name": "api", "contentLibrary": null, "filter": "api", "maxAge": 3600, "cachePolicy": 4, "privileges": null }
INSERT INTO public."ContentCacheControls" ("ID", "CreatedDate", "ModifiedDate", "ModifiedByUserName", "Name", "Filter", "MaxAge", "CachePolicy", "ContentLibrary_ID") VALUES ('e07ca071-7d72-417d-93c2-d60687f747a8', '2022-08-19 14:28:48.077709', '2022-08-19 14:28:48.077709', 'RDLUND\svc-silver', 'api', 'api', 3600, 4, null);
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
What's new in Qlik Sense February 2022
What's new in Qlik Sense May 2022
Qlik Sense Enterprise on Windows
QB-11410
Installing, upgrading, and managing the Qlik Cloud Monitoring Apps for user-based subscriptions has just gotten a whole lot easier! With two new Qlik Application Automation templates coupled with Qlik Data Alerts, you can now:
The above allows you to deploy the monitoring apps to your tenant with a hands-off approach. Dive into the individual components below.
Content:
This automation template is a fully guided installer/updater for the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software GitHub and thus are subject to Qlik's open-source guidelines and policies.
For more information, refer to the GitHub repository.
Note that if the monitoring applications have been installed manually (i.e., not through this automation) then they will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.
This template is intended to be used alongside the Qlik Cloud Monitoring Apps for user-based subscriptions template. This automation provides the ability to keep the API key and associated data connection used for the Qlik Cloud Monitoring Apps up to date on a scheduled basis. Simply input the space Id where the monitoring_apps_REST data connection should reside, and the automation will recreate both the API key and data connection regularly. Ensure that the cadence of the automation’s schedule is less than the expiry of the API key.
Enter in the Id of the space where the monitoring_apps_REST data connection should reside.
Ensure that this automation is run off-hours from your scheduled monitoring application reloads so it does not disrupt the reload process.
Each Qlik Cloud Monitoring App has the following two variables:
With these variables, we can create a new Qlik Data Alert on a per-app basis. For each monitoring app that you want to be notified on if it falls out of date:
Here is an example of an alert received for the App Analyzer, showing that at this point in time, the latest version of the application is 5.1.3 and that the app is out of date:
Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?
A: Yes. Run the installer, select which applications should be checked and select the space that they reside in. If any of the selected applications are not installed or are upgradeable, a prompt will appear to continue to install/upgrade for the relevant applications.
Q: What if multiple people install monitoring applications in different spaces?
A: The template scopes the applications install process to a “target” space, i.e., a shared space (if not published) or a managed space. It will scope the API key name to `QCMA – {spaceId}` of that target space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already and it will install the application leveraging those pre-existing assets.
Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?
A: Yes. The template receives the list of applications dynamically from GitHub. If a new monitoring application is released, it will become available immediately through the template.
Q: I would like to be notified whenever a new version of a monitoring applications is released. Can this template do that?
A: As per the article above, the automation templates are not responsible for notifications of whether the applications are out of date. This is achieved using Qlik Alerting on a per-application basis as described in Part 3.
Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?
A: The history is preserved in the prior versions of the application’s QVDs so the data is never deleted and can be loaded into the older version. Each upgrade will generate a new set of QVDs as the data models for the applications sometimes change due to bug fixes, updates, new features, etc. If you want to preserve the history when updating, the application can be upgraded with the “Publish side-by-side” method so that the older version of the application will remain as an archival application. However note that the Qlik Alert (from Part 3) will need to be recreated and any community content that was created on the older application will not be transferred to the new application.
This article provides an overview of how to manage space membership for groups using a Qlik Application Automation. This approach can be useful when migrating from QlikView, or Qlik Sense Client Managed, to Qlik Sense Cloud when security concerns prevent the usage of Qlik-CLI and Powershell scripting.
In this example, we use Microsoft Excel to configure group Space memberships. A sheet name, for example, Groups, must be added and this must also be provided as input when running the automation. The sheet must also contain the following headers:
Qlik Sense patches can be downloaded from the Qlik Download page. Patches are cumulative, and only one patch can be installed at a time.
Example: Patch 4 for Qlik Sense February 2019 will include all fixes from 3, 2, and 1.
Before applying a patch:
Executing a patch installation package will automatically uninstall the previous patch and install the new one. If you need to uninstall a patch manually:
Custom configuration file changes not kept after Qlik Sense upgrade
End of Support for Qlik products follows Release Management Policy, as documented in the Product Terms found on the Qlik Site: On-Premise Products Release Management Policy
For detailed information on end of life and release dates, see:
Qlik Sense Enterprise on Windows Product Lifecycle
Qlik NPrinting Product Lifecycle
QlikView Product Lifecycle
Related Content:
This article describes how to resolve the NPrinting connection verification error:
x Qlik NPrinting webrenderer can reach Qlik Sense hub error
The Qlik Sense Repository Service can suddenly come to a situation where the CPU utilization of the central node increases beyond 95%, which causes effects in the Qlik Sense hub (sheets go blank and other unexpected slow behavior). The process that is consuming the maximum CPU can be seen as the Qlik Sense Repository Service.
Identified in a Problem Investigation with R&D, one of the possible causes is related to large number number of open transactions in the repository database and locks held by large number of sessions impacting on the repository service communication with the repository database.
Qlik Sense Enterprise on Windows November 2017 and later versions
Setting the idle_in_transaction_session_timeout to 5 minutes would clear the threads the repository database and progresses the new threads in the queue
SHOW idle_in_transaction_session_timeout;
alter system set idle_in_transaction_session_timeout to '5min';
SHOW idle_in_transaction_session_timeout;
# reload the configuration
select pg_reload_conf();
#idle_in_transaction_session_timeout = 0 # in milliseconds, 0 is disabled
And changing it to:idle_in_transaction_session_timeout = 300000 # in milliseconds, 0 is disabled
Save, and then schedule a restart.
Changing the value, idle_in_transaction_session_timeout terminates any session with an open transaction that has been idle for longer than the specified duration in milliseconds. This allows any locks held by that session to be released and the connection slot to be reused decreasing over CPU utilization.
The syntax used for creating expressions on column names that contain the symbol '$' differs between Qlik Replicate versions. This article documents the two different methods.
The syntax changed with the May 2023 release. Previously, the syntax allowed the full column name to be recognized with a '$' symbol in front of the column name. With the current syntax, Qlik Replicate interprets these expressions as containing two separate columns and will error out.
Content:
Starting with the May 2023 release, extra '$' symbols are treated as an additional column name. To correctly format the expression to read it as a single column, the setting Support special characters in column names used in expressions must be enabled and the syntax of double quoting the column name should be used.
Enable the transformation setting:
Syntax example:
Column name: IXF$RP
Expression: "IXF$RP"
If support for special characters is not toggled on, the Parse expression will not parse.
If the extra '$' is used, the expression will treat the column name as two separate columns. Running the expression as is will lead to the task failing with "Failed to init column calculation expression".
Previous syntax example:
Column name: IXF$RP
Expression: $IXF$RP
The warning and example provided in the user guide refer to string literals used in an expression and not the column name. Single quotes should be used for the string literals and not the column name.
This article is intended to get started with the Microsoft Outlook 365 connector in Qlik Application Automation.
To authenticate with Microsoft Outlook 365 you create a new connection. The connector makes use of OAuth2 for authentication and authorization purposes. You will be prompted with a popup screen to consent a list of permissions for Qlik Application Automation to use. The Oauth scopes that are requested are:
The scope of this connector has been limited to only sending emails. Currently, we do not enable sending email attachments and are looking to provide this functionality in the future. The suggested approach is to upload files to a different platform, e.g. Onedrive or Dropbox and create a sharing link that can be included in the email body.
The following parameters are available on the Send Email block:
As we do not currently support email attachments, we need to first generate a sharing link in Onedrive or an alternative file sharing service. The following automation shows how to generate a report from a Qlik Sense app, upload the report to Microsoft Onedrive, create a sharing link and send out an email with the sharing link in the body. This automation is also attached as JSON in the attachment to this post.
During a Replicate Full Load, incoming changes occur while the Full load is in progress. What happens to those changes?
Qlik replicate starts the CDC thread before starting the Full load and all the changes show as cached events while the Full load is running. For example, 2 billion records are applied in the Full load state and Replicate again check at the end of the Full load for committed changes. If 100k changes are also committed before finished then it will also be applied in the full load otherwise the 100k changes will go to CDC.
Another example, for a full load takes 12 hours, then updates during the 12 hours full load window are also applied. Note- these two examples assume you have CDC enabled in the task.
If CDC is turned off during a full load task, then Replicate will not capture the cached events.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
This article explains how to change the default locale in QlikSense Server when you create a new app on the hub.
Qlik Sense Enterprise on Windows
When you create a new application on the hub, the default locale is based on the settings on the QlikSense Server.
In order to change this setting, it is required to change the locale settings on the server for the account that is running the services.
If you run services as local system, you will need to use a tool such as Psexec in order to be able to execute the control panel as local system and change this settings.
QlikView Server May 2022 (12.70)
IIS
SAML authentication
A Qlik Compose task may fail during a full load but will run OK after a retry or when started at a different time.
The task error log shows:
main 2023-10-30 08:39:51.396 [engine ] [ERROR ] [] Failed to create temporary file for /com/sun/jna/win32-x86-64/jnidispatch.dll library: C:\Windows\TEMP\jna--187113817\jna4331371764969383844.dll (The process cannot access the file because it is being used by another process)
The error indicates that a virus scan or malware scan was active while the Qlik Compose task was run. This locked the files needed.
Exclude the Qlik Compose installation folder from the virus scan. The default path is: C:\Program Files\Qlik\Compose
Do not run any Qlik Compose task to run during scheduled virus scans.
Using a Sybase ASE source endpoint, Qlik Replicate may not capture or simply ignore all DDL (Data Definition Language) commands, while DML (Data Manipulation Language) commands (Insert/Update/Delete) are captured and applied successfully.
Example of DDL in a source database:
alter table db_test.dbo.tb_test add notes varchar(50) null
Qlik Replicate ignores the above DDL. Reviewing the task logs (if set to trace or verbose logging level) shows:
[SOURCE_CAPTURE ]T: Captured DDL / type for table dbo.tb_test (identified by objid 672002394) is not known to metadata manager. Irrelevant DDL - ignored... (sybase_endpoint_metadata.c:710)
Verify the user's privileges as per Required permissions for SAP Sybase AES.
Example of how to create a user (qruser) which owns sufficient permissions and works fine with DML/DDL operations:
create login qruser with password qruser123
sp_adduser qruser
grant role sa_role, replication_role, sybase_ts_role to qruser
sp_displaylogin qruser;
#00112248
The Qlik NPrinting Engine cannot resolve requests for tasks which include Qlikview Entity reports that output to PDF or is not printing QlikView Entity reports to PDF.
An error is displayed when attempting to edit or print the QlikView Entity report:
Error: QlikView NPrinting PDF Printer not installed or not properly registered
Or the report fails silently while the following is printed in the Qlik NPrinting logs:
resolution aborted with exception System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.↵↓ at Tracker.PDFXChange.IPXCControlEx.get_Printer(String pServerName, String pPrinterName, String pRegKey, String pDevCode)↵↓ at Qlik.Reporting.Printers.QlikPdfPrinter.Win64PrinterFactory.get_Item(String pServerName, String pPrinterName, String pRegKey, String pDevCode
When you install Qlik NPrinting, the Windows service “Print spooler” must be up and running. If it is disabled, the Qlik NPrinting Printer will not be added during the installation. Similarly, if a separate PDF-XChange driver is installed, the Qlik NPrinting engine install will not install the QlikView NPrinting PDF-Printer.
NPrinting: PDF reports generation fails after disabling the Windows Spooler service
QB-14941
Description of Property "force-unused-resolvers-closure-policy":
*NOTE: The term 'Large' is relative to the amount of RAM on your NP server. If low Ram like 64 or 128 GB RAM, then 1 GB QVW is 'large' since it may grow as large as 10 GB in memory. Then if you have 8 cores, it will open 16 processes each potentially with 10 GB each since NPrinting will use every core process by default to generate a single report. (https://help.qlik.com/en-US/nprinting/February2019/Content/NPrinting/DeployingQVNprinting/Performance.htm)
Qlik NPrinting June 2018 or higher. Do not apply to previous versions.
NOTE: Please ensure to back up the scheduler.config file before proceeding
Note: Config file changes are overwritten upon upgrading NPrinting. Please apply these changes again after upgrading if the issues persist.
We recommend to follow this article in case the problem persists.
NPrinting tasks connecting to QlikView look stuck in Running status. The task manager on the Engine nodes shows some Qv.exe processes running, but the RAM and CPU usage does not change.
<!-- <add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" /> -->
<add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" />
NPrinting Engine needs to open QlikView Desktop in the background to communicate with the source QVWs during the generation of the reports in the tasks. These Qv.exe processes can be seen in the task manager under the Detail tab.
For some reasons that are currently under investigation, it can happen that the QlikView processes stuck and are not able to send the needed information to NPrinting. Therefore the report creation can't proceed and the tasks remain in Running status without progress.
When the option in 'Resolution' is active, NPrinting monitors the status of the Qv.exe processes and close them when they are stuck. A new Qv.exe process will automatically opened to replace the killed one.