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.
There has always been a noticeable gap in Qlik Replicate, where users had no means of importing just an endpoint into Qlik Replicate. This article provides a workaround to that limitation.
{
"cmd.replication_definition": {
"databases": [{
...
}]
},
"_version": {
...
}
}
Verify that your endpoint name is correct.
You may want to skip entering the password and add it later through the user interface. Inputting the password in the JSON is in plain text.
{
"cmd.replication_definition": {
"databases": [{
"name": "DB2z_Source",
"description": "",
"role": "SOURCE",
"is_licensed": true,
"type_id": "DB2ZOS_NATIVE_COMPONENT_TYPE",
"db_settings": {
"$type": "Db2zosSettings",
"additionalConnectionProperties": "MaryHad=aLittleLamb",
"username": "dimae",
"databaseAlias": "DBALIAS",
"server": "lpardns.mydomain.com",
"port": 5035,
"databaseName": "LOCATION",
"CCSIDMapping": "234,ibm-p100-2345",
"ifi306SpName": "R4Z_UDF_ALL_NEW"
},
"override_properties": {
}
}]
},
"_version": {
"version": "2023.5.0.213",
"version_major": 2023,
"version_minor": 5,
"version_revision": 213
}
}
repctl importrepository json_file=NAMEOFFILE.JSON folder_name=DRIVE:\FOLDER
Editing an exported (json) file
ImportAll | Enterprise Manager API
Exporting and importing tasks
Importing tasks
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.
Qlik Replicate can be licensed using RepCtl. For instructions on how to license Qlik Replicate using the standard user interface, see Registering a license.
{
"cmd.license":
{
"license_type": "EVALUATION_LICENSE",
"licensed_to": "QLIK CUSTOMER",
"licensed_by": "Attunity US",
"serial_no": "60035964",
"expiration_date": "2023-12-01",
"hosts": "xxx.xxxx",
"source_types": "oracle",
"target_types": "target",
"features": "yyyy",
"version": "2023.11",
"issue_date": "2023-10-31",
"checksum": "xxxxx-xxxxx-xxxxx-xxxxx"
}
}
{
"cmd.license":
{
"license_type": "EVALUATION_LICENSE",
"licensed_to": "QLIK CUSTOMER",
"licensed_by": "Attunity US",
"serial_no": "60035964",
"expiration_date": "2023-12-01",
"hosts": "xxx.xxxx",
"source_types": "oracle",
"target_types": "target",
"features": "yyyy",
"version": "2023.11",
"issue_date": "2023-10-31",
"checksum": "xxxxx-xxxxx-xxxxx-xxxxx"
}
}
The Qlik Compose monitoring window takes a long time to load.
This is likely caused by old task entries not being purged from the project's ProjectRepoRuntime.sqlite file.
ProjectRepoRuntime.sqlite is located in <Instation_folder>\data\projects\PROJECT_NAME
Example (default): C:\Program Files\Qlik\Compose\data\projects\YOUR_PROJECT_NAME
Upgrade to Qlik Compose 2022.5.0-sp16 (2022.5.1177) or any later version.
After the upgrade, note:
It is essential to stop the Qlik Compose service and back up the project folder before compacting the file. Please contact support if any assistance is needed.
2022.5.0-sp16 (2022.5.1177) and higher
Recob-7766
Information provided on this defect is given as is at the time of documentation. For up-to-date information, please review the most recent Release Notes with RECOB- 7766 for reference.
While using Databricks Lakehouse (Delta) as a target endpoint, it would be highly beneficial for users to have the option to write data to multiple databases within a single target endpoint connection.
Some specific business use cases involve managing more than 30 databases under a single catalogue. Creating over 30 separate target endpoint connections in Qlik Replicate to handle these databases is a big challenge.
In this article, we will explain the solutions to how we can manage multiple databases within a single connection. The same approach can be used in other common databases, including Databricks (Cloud Storage), Microsoft SQL Server, PostgreSQL, and other similar databases.
Changing the Target table schema is the equivalent of changing the specified database name in the endpoint settings.
In the endpoint definition, specify the "Database" name, this is the default database. In our screenshot example, the default database is named "APACDB".
We may use "schema" to identify the non-default database name, which will write different tables of data to different databases within a single connection.
There are two options, Table level, and Global level:
Qlik Replicate all versions
Databricks Lakehouse (Delta) all versions
Databricks (Cloud Storage) all versions
Support case #00122351
The QlikView server creates a last document state or session recovery bookmark ($LASTKNOWNSTATE) when a QlikView document is closed from the Full Browser Client. This allows work to be resumed, even after the session has been terminated. Sometimes, this session or state needs to be cleared.
Symptoms:
A QlikView document does not open and is stuck in:
The last known document state may be attempting to call an invalid state or object created by the user the last time the document was closed.
To clear this, the end-user needs to click the Remove Last Document State button visible in the View Details menu accessible from a link below the document listed on the AccessPoint.
Note that clearing the last document state does not mean the session is reset. If the user is still within an active session and they close and re-open the document, the previous session is resumed. This is not the last document state.
The last document state is a bookmark applied at the end of a session.
For a more detailed description, see Session Recovery in QlikView: How to enable it and how it works.
Qlik Sense works normally, but a huge quantity Repository logs is generated. These following messages are continuously repeated (not necessarily both of them are present).
In System logs:
INFO SERVERNODE System.Repository.Repository.Core.Repository.Common.ModelRepository`1[[Repository.Domain.Model.UserDirectorySettings, Repository.Domain, Version=xx.xx.x.0, Culture=neutral, PublicKeyToken=...]]
..... Database object has newer timestamp than object being modified; ....
.... ERROR SERVERNODE System.Repository.Repository.Core.Repository.Common.TransactionUtility
..... Error when committing
In User Management logs:
WARN SERVERNODE UserManagement.Repository.Repository.Users.SyncUsersWorker ........
Conflict when trying to do database operation; retrying... at Repository.Core.Repository.Common.AbstractModelRepository.CheckConflicts(IRepositoryObject persistedItem, DateTime itemModifiedDate)↵
The quantity of messages generated is very high and several GB of memory can be occupied in disk in few hours.
In order to avoid a complete filling of the disk, it is necessary to restart the node where the problem occurs. Generally, this resolves the issue.
To avoid this problem, we have introduced an improvement in the latest Qlik Sense releases that avoids potential conflicts. This improvement is present in Qlik Sense February 2021 Patch 6 and in Qlik Sense May 2021 SR1 or higher releases. An upgrade is recommended to ultimately fix the problem.
The problem is due to an incorrect synchronization between the Database and one of the nodes.
SHEND-509
The Qlik Download page or Qlik Ideation app do not show their expected content. The web page and browser console display error messages referring to HTTP 401 Unauthorized access, which may look similar to the below examples.
The Qlik Download page and Ideation App on Qlik Community require 3rd party cookies as part of the current web integration. The accessing browser must allow 3rd-party cookies while accessing the Qlik Downloads page in order for the page to render successfully.
The browser does not have to completely allow 3rd party cookies, but can also just allow 3rd cookies for the *.qlik.com or community.qlik.com domain.
The cookie settings are browser-specific, please consult browser help for more details.
The Qlik Download page and Ideation App in Qlik Community are composed by an embedded object hosted in Qlik Cloud. This means cookies for the user session are associated with two different domains, community.qlik.com and qlikcloud.com. The browser refer to the parent page (community.qlik.com) as a 1st party cookie, while the embedded content from a different domain (qlikcloud.com) is referred to as a 3rd party cookie.
3rd party cookies may be blocked in a browser as a mechanisms to block user tracking and advertisement. Browser incognito mode may also block 3rd party cookies by default as part of keeping the user more anonymous.
Clear, allow & manage cookies in Chrome
Third-party cookies and Firefox tracking protection
Microsoft Edge, browsing data, and privacy
Clear cookies in Safari on Mac
QMSEDX is a community-provided customization. Qlik does not provide support or direct assistance for this solution. For assistance, contact our Professional Services or engage in our QlikView Integrations forum.
EDX is a trigger mechanism for starting a QlikView reload or task from an external source, such as a scheduler or application. To start a task using EDX the QlikView Management API must be used and this is delivered in the form of a Web Service.
QMSEDX is a third-party app designed to perform said mechanism. For more information, see Using EDX in QlikView 11.
QMSEDX is an open source tool that is developed by CwolfX on sourceforge where you can find more information and maybe support: https://sourceforge.net/p/qmsedx/wiki/Home/ Also keep in minde that as it is an opensource it could have other developers making there version available online, juste make sure to contact the one that made the version you are using
For custom developments. Documentation about QMS API is available at Qlik Help.
Upgrading QlikView fails with the Warning:
You need a valid maintenance contract to be allowed to install and use this Software
Proceeding with upgrades without an updated maintenance contract will lead to the QlikView Server license being invalidated. The server will enter Off Duty state.
Attempting to license a QlikView server with an outdated license will lead to
Server failed to set license: QVS@qlikviewserver: This license key has expired!
The maintenance data for the license key has expired prior to the release date of the product version you are updating too.
See the Maintenance contract on upgrade for more details.
Example:
000000000000000
NUMBER_OF_USERCALS;5;;
NAMED_CAL_BY_MACHINE_ID;NO;;
PRODUCTLEVEL;10;;2016-12-30
000000000000000
If the maintenance date is correct and you have attempted to update the license, verify if no old LEF.txt files are stored in your system. See Where do all the QlikView LEF files go? for information on where they are stored. Carry the check out on all nodes if you have a multi node environment.
If you do not have an up-to-date maintenance date, contact your Qlik Account Manager to renew the license and repeat steps 1 and 2 above.
When attempting to connect to a new Direct Access Data Gateway data source within the load script editor of a Qlik Application, the new data connection test fails.
When reviewing the Data Gateway logs at "C:\Program Files\Qlik\ConnectorAgent\data\logs" , the following error is discovered:
ERROR partner 'myremotedataserver.com:3350' not reached"
Expected Result:
The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
If you want to submit a new idea or improvement request for Qlik's products, our Ideas section in the Qlik Community is open to all registered customers.
Content:
Ideas are qualified and prioritized based on their value to improving and enhancing the Qlik product. For a successful request, please consider including a strong business case on why you think the change would be beneficial, including:
Before you get started, review Ideation Guidelines: How to Submit an Idea for submission guidelines and eligibility information.
Ideas and Improvement requests are reviewed by our product teams. While we strive to provide answers, we cannot guarantee a specific response time.
Ideation on Community
Ideation Platform Updates
Ideation Guidelines: How to Submit an Idea
After upgrading from Windows 10 to Windows 11, or applying certain patches to Windows Server 2016, Qlik Replicate may not load in the browser.
The following error is displayed:
ERR_SSL_KEY_USAGE_INCOMPATIBLE
Qlik Replicate 2022.11 (may happen with other versions)
Qlik Compose 2022.5 (may happen with other versions)
Qlik Enterprise Manager 2022.11 (may happen with other versions)
Use of the self-signed SSL certificate
Windows 11
Windows server 2016
This issue has to do with the self-signed SSL certificate. Deleting the existing one and allowing Qlik Replicate/Compose/Enterprise Manager to regenerate them resolves the issue.
For Qlik Compose:
For Qlik Enterprise Manager:
Navigate to the ..\Attunity\Enterprise Manager\bin directory and then run the following command:Qlik Replicate will now allow you to open the user interface once again.
If users still cannot log in and are returned to the log in prompt at each attempt, see How to change the Qlik Replicate URL on a Windows host.
This article explains how to save network logs in web development tools and the console logs from the browser and how to capture and read client-side response trace with HAR file analyzer.
For Qlik Sense it is important that the trace is started prior to Qlik Sense login so that WebSocket creation is captured.
Environment:
To read the files, use a tool such as the HAR Analyzer https://toolbox.googleapps.com/apps/har_analyzer/
To read the files, use a tool such as the HAR Analyzer https://toolbox.googleapps.com/apps/har_analyzer/
Further Troubleshooting
Upgrading Qlik Sense Enterprise on Windows with a standalone PostgreSQL database to August 2023 or later fails. The installer does not return an error on-screen.
A Qlik Sense Enterprise on Windows environment can have a bundled PostgreSQL database or a standalone database.
If your Qlik Sense environment has relied on a standalone PostgreSQL database since its initial setup, and still has its PostgreSQL 9.6 database and binaries, additional steps are required to prepare for an upgrade to any versions beyond Sense August 2023.
These binaries will be in the following folder:
C:\Program Files\Qlik\Sense\Repository\PostgreSQL\version number
Where version number is 9.3 or 9.6.
The old binaries need to be uninstalled and new binaries installed (on all nodes).
Qlik Sense August 2023 and higher as the target version
Qlik Sense May 2023 and lower as the source version
Before proceeding with an upgrade:
The msi will be revealed.
The msi will be revealed.
The upgrade will be blocked when a 9.6 or 9.3 database binary folder is found. These folders can be in either:
C:\Programdata\Qlik\Sense\Repository\PostgresSQL\version number
C:\Program Files\Qlik\Sense\Repository\PostgresSQL\version number
The CPU affinity is not working as expected. The number of CPU affinity for the QVS does not match the cores in the Server.
QlikView
Generation 9 HP servers
This issue comes from a new BIOS setting introduced in Generation 9 of HP servers. A new setting has been added in BIOS that needs to be modified to allow the QlikView services to properly detect all the CPU Cores in the machine.
This can be resolved by changing the BIOS setting "NUMA Group Size" to "Flat". The default setting for "NUMA Group Size" disables QlikView from properly detecting all CPU cores in the hardware.
In this Webinar, we covered how to approach a Qlik Sense Enterprise on Windows migration.
The session covers:
Qlik Sense Migration: Migrating your Entire Qlik Sense Environment (Blog post)
Help.Qlik.Com Documentation: Backup and Restore Qlik Sense Enterprise on Windows
Qlik Sense Upgrade Guide
Qlik Admin Playbook
Q: Is it possible to migrate from a standalone installation to a clustered one?
A: Yes. Once the Central Node has been moved to a new host, additional Rim nodes can be added as usual through the QMC.
Q: What about the personnal objects created by users (sheets, bookmarks, ...) ? Are they included in the QSR backup ?
A: All user objects as well as base sheets are included both in the Apps themselves as well as in the QSR.
Q: Is this possible to migrate one repository to another server and merge the repository with another one?
A: Not through the procedure outlined in this webinar. If your goal is to merge content from multiple sites, or seamlessly migrate content, I recommend reaching out to your Account Manager and discuss Qlik Mission Control platform.
Q: Would the steps given here change if postgres is installed on a stand-alone server?
A: The only steps that would change would be the backup/restore for the DB itself, as this would have to be performed locally on the DB host. Additionally, if the DB location has changed, the QRS connection strings will have to be updated via QlikSenseUtil.
Q: Is it necessary to have the same release on both servers before migrating ? Or is there compatibility between versions of QlikSense ?
A: You can restore a database from a previous version on a newer Qlik Sense release and the system will update the internal objects automatically, however the reverse is not possible. It is recommended to perform the upgrade in place, before migrating the server.
Q: Is it possible to restore without certificate ?
A: Yes, Trust Root and Qlik Client certificates can be recreated from scratch, however as mentioned during the call, all internal metadata values that were previously encrypted, such as data source connection strings, would have be updated via the QMC by re-entering the connection password and saving.