Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
Qlik offers a range of opportunities to assist you in troubleshooting, answering frequently asked questions, and contacting our 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 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)
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)
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.
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 Contact Support 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:
How to create a case using chat
Log in to manage and track your active cases in Manage Cases. (click)
Your advantages:
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.
Qlik Cloud is a modern analytics and data platform built on the same software engine as QlikView and Qlik Sense Client-Managed and adds significant value to empower everyone in an organization to make better decisions daily. Qlik Cloud allows you to use one common platform for all users – executives, decision-makers, and analysts.
Navigation:
Migrating to Qlik Cloud can help your organization:
Q&A with Qlik: Qlik Sense Migration to Qlik Cloud
Articles relevant to migration and new Qlik Cloud users
This site provides you the tools to monitor, manage, and execute a migration from Client-Managed Qlik Sense to Qlik Cloud.
Index and home
Planning your migration
Setting up the Qlik Cloud migration tools
Create and configure a cloud tenant
This site provides you the tools to begin your journey to move from QlikView to Qlik Sense and Qlik Cloud.
March 14th 2023: You may have upgraded Qlik Sense and located a warning banner in your Management Console stating that this version of PostgreSQL is not supported. If you are running a standalone PostgreSQL database later than 9.6, this message can be disregarded. We are working on resolving the underlying cause.
In this article, we walk you through the requirements and process of how to upgrade an existing Qlik Sense Repository Database from PostgreSQL 9.6 to PostgreSQL 12.5 (see supported scenarios) or install a brand new Repository based on PostgreSQL 12.5.
We will use the Qlik PostgreSQL Installer (QPI).
For a manual method, see: How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version
PostgreSQL 9.6 has reached End of Life Reference: PostgreSQL Versioning Policy.
Download the installer here.
Qlik PostgreSQL installer version 1.2.1 Release Notes
Before using the Qlik PostgreSQL Installer, upgrade to a supported version of Qlik Sense Enterprise on Windows. Then use the Qlik PostgreSQL Installer to upgrade PostgreSQL.
We tested and validated Qlik Sense Enterprise on Windows from February 2022 to February 2023. Note that November 2022 and later do not support 9.6, and a warning will be displayed during the Sense upgrade.
Qlik Sense Enterprise on Windows installations other than in C:\Program Files\Qlik\Sense are currently not supported.
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
No further steps are needed unless you plan to upgrade Qlik Sense Enterprise on Windows to the next major release. If you plan to upgrade to, for example, November 2022, the old Qlik Sense Repository Database service must be removed from the server.
Perform the following steps to delete the Qlik Sense Repository Database Service:
This version of the upgrade tool is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
If you need to upgrade to a higher release than Qlik provides, you can install the same minor PostgreSQL release 12.x.
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. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.
Qlik PostgreSQL installer version 1.2.1 Release Notes
Techspert Talks - Upgrading Qlik Sense Repository Service
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades
You may notice fiber loop errors appearing in the Windows, QlikView and Qlik Sense logs.
e.g:
StdServer: Fiber loop (10b74b020) stall detected: last fiber loop iteration started 120917 ms ago.
Fiber loop is an entirely normal error to see and is usually just a sign of a busy server. It may not show any symptoms to the end user.
Fiber-loop stalls indicate a problem with a Windows fiber (a kind of thread) that has taken too long to respond. It shows up in the Windows error logs and the user may experience this a client crash as the session has been closed. If the browser is refreshed then a new session is created.
If the peak memory usage is sufficient to drive the server up towards the upper control limit (High Working Set default is 90%), then one can expect to see some level of degraded performance and unusual failures as the in-engine cache will be mostly drained of memory. The required and recurring re-calculations of results will also use a lot of CPU, and this is also likely the path of explanation for the observed stalls.
Fiber-loop stalls indicate a problem with a Windows fiber (a kind of thread) that has taken too long to respond.
Generally caused by a busy server that may or may not be oversubscribed (causing peaks in resource usage) and/or by slow network performance particularly when working with large apps stored on network device or share.
It would be more a case of investigating the overall server performance, size of the Apps (if these are very large and stored on a network device) perhaps there are issues with Network speed/performance.
Any performance issues should be investigated with their local IT team to help reduce the number of fiber loop errors reported.
See What are fiber loop errors in the QlikView server event log? for more details, as well as related content below.
In this article, we detail the 12 steps necessary to successfully configure Qlik Sense Enterprise on Windows after an Active Directory Domain name change or moving Qlik Sense to a new domain.
Depending on how you have configured your platform, not all the steps might be applicable. Before updating any hostname in Qlik Sense, make sure that the original value is using the old domain name. In some case, you may have configured “localhost” or the server name without any reference to the domain so there is no need in these cases to perform any update.
In this scenario we are updating a three-node environment running Qlik Sense February 2021:
The domain has been changed from DOMAIN.local to DOMAIN2.local
The servers mentioned below are already part of the new domain name DOMAIN2.local and their Fully Qualified Domain Name (FQDN) is already updated as followed:
All Qlik Sense services have been stopped on every node.
The first step is to update the postgres.conf file to listen on the correct hostname
Before doing any further changes, it is important to take a backup of your Qlik Sense Platform
Now we update the node names in the database with the new Fully Qualified Domain Name.
UPDATE public."Users"
SET "UserDirectory" = 'DOMAIN2'
WHERE "UserDirectory" = 'DOMAIN';
SELECT * FROM public."Users"
cd "C:\Program Files\Qlik\Sense\NLAppSearch\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\AppDistributionService"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\HybridDeploymentService"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\Licenses"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\NotifierService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\MobilityRegistrarService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\PrecedentsService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\DataPrepService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
If you are using the Qlik Logging Service;
cd "C:\Program Files\Qlik\Sense\Logging"
Qlik.Logging.Service.exe validate
cd "C:\Program Files\Qlik\Sense\Logging"
Qlik.Logging.Service.exe update -h QlikServer3.domain2.local
"C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname
If you are syncing your users with a User Directory Connector you will need to change the LDAP path to point to the new domain.
You will need to update the monitoring apps and their associated data connection to use the new Fully Qualified Domain Name
It is possible that you have created rules based on the User Directory. As you have changed the domain name, the user directory has also changed in Qlik Sense so you will need to update those to reflect that.
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.
The following error is seen when attempting a full load:
ORA-26086: direct path does not support triggers
A direct path operation is being attempted on a table which has enabled triggers.
Either disable the triggers on the table or disable Direct Path in the target endpoint. You can disable this in the Advanced tab of the target endpoint.
See Limitation (Using Oracle as a target) for more information.
A Qlik Replicate tasks fail with the error below:
[DATA_STRUCTURE ]E: SQLite general error. Code <13>, Message <database or disk is full>. [1000506] (at_sqlite.c:475)
Follow the options below to resolve the issue:
Option 1:
Free disk space or increasing disk quota.
Option 2:
Perform a full reload on all of your tasks. This would automatically delete the tswap files and free up space.
Option 3:
Change the location of the Qlik Replicate data directory. See Qlik Replicate Moving the Data Directory on the same server to a larger drive.
This error usually indicates Replicate has no space to write to due to high tswap files being generated. See Replicate Sorter Files.
Qlik Replicate is actively refusing the connection and Qlik Replicate does not start. This may happen after a Windows Update applied changes to a local group policy and a server restart.
After the reboot, the Qlik Replicate services fail to start and the following error can be found in task logs:
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:3552
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.
A PostgreSQL database has caused a disk to fill up or a storage limit to be reached. Services have been stopped.
Upon further investigation, it was detected that an inactive replication slot for a Postgresql database has filled up with lag data. This lag exists because the replication slot is still being filled but not consumed.
Upgrade to a Qlik Replicate version at or above version 2022.5.
If an upgrade is not yet possible, add the retryStartRepSlotActive and timeoutBetweenStartRepSlotRetry internal parameters as a workaround. This value indicates how frequently Qlik Replicate should attempt to start a replication slot before giving up. By default, the value is set to 5.
For instructions on how to add internal parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?
A Qlik Replicate task moving data directly from Salesforce Incremental + SOAP endpoint is not writing data to Snowflake Target. All changes are being written/saved to disk and not applied to the target.
An error to watch out for:
Failed to get data in table 'Event'. Error message: null, cause: null
Error message: null, cause: null
This is connection error on Soap API request, most probably due to timeout, since other requests works fine and there are no network issues.
Soap API is good for small amount of data, but for big results, bulk is much faster and has longer timeouts.
As per Salesforce documentation:
query() and queryMore() Batch size limits The maximum batch size is 2,000 records, but this number is only a suggestion. To maximize performance, the requested batch size isn’t necessarily the actual batch size. Salesforce Web Service Connector (WSC) clients can set the batch size by calling setQueryOptions() on the connection object. C# client applications can change the batch size in the QueryOptions portion of the SOAP header before invoking the query() call.
If the SOQL statement selects two or more custom fields of type long text, the batch size can’t be greater than 200 records. This limit prevents large SOAP messages from being returned.
Scenario:
In SAP, the extractor is used by two systems: BW and Qlik. To test if that was a problem, a new system for an extractor to be used exclusively by Qlik was created. The BW system did not use Qlik's system for the extractor.
Doing this, the extraction worked.
On the other hand, for full and delta loads, this raises the question: If you utilise BW, can Qlik Replicate do full and delta loads in a standard way (without having to create Z extractor)?
Errors and Warnings to watch for:
There is a known limitation on this, as the extractor should be run by Qlik Replicate only. If you use BW and Qlik at the same time, there is a chance of missing records unless they are not crossing each other.
A task which has been running okay for months started to build latency.
Error:
22007 NativeError: 100040 Message: Date '0000-00-00' is not recognized
This was due to a wrong date. We found an expression for the the bad date from the Source.
Steps to resolve the issue:
CASE
WHEN strftime('%Y-%m-%d', $ModifiedDate) IS NULL THEN
'0001-01-01'
ELSE
$ModifiedDate
END
The Qlik Replicate Server Service may be run by a dedicated service account.
To change the password:
Scenario:
Data is being loaded from Azure SQL Managed Instance (MS-CDC) to Kafka using Qlik Replication. Whenever connectivity issues occur, the task is run using Advanced Run Options (Point in Time).
Identical records are loading (Duplicate Records) multiple times. To track data integrity, the header AR_H_COMMIT_TIMESTAMP was used and the AR_H_COMMIT_TIMESTAMP is higher on the 1st committed than the second one.
When restarting the task back in time, the header information for specific changes is different every time the task is run. For example, when a change is captured the header_timestamp may be '2023-02-22 18:58:56.221000'. If the task is resumed back in time before the change the header_timestamp may be '2023-02-22 18:58:56.314000' for the exact same change.
All of the header column values are different.
The header timestamp is not an exact value on the change.
In the SQL Server, the transaction timestamp is approximate and based on the last commit that happened in the database. Because of the way that changes are captured in MS-CDC, the header information is not part of the change record and is read from a separate table and since it is not exact you can end up with different header values.
The following warning is logged while replicating a view from a Postgres source endpoint. This causes the NCLOB/String columns to be NULL on the target.
[SOURCE_UNLOAD ]V: Value for column 'XXXXX' was truncated. bind type: -8, data len: 10 (10, after truncation: -2), bind len: 0, statement: XXXXXX
Qlik Replicate tasks with an SQL endpoint fail with:
[SQL Server]Login failed
The behavior began after an upgrade to Qlik Replicate version 2022.11 or later.
In the Qlik Replicate UI:
See Working with Windows authentication | Qlik Replicate Help for details.
With an upgrade to Qlik Replicate 2022.11 (and later), the Qlik Replicate service name was change from Attunity Replicate server to Qlik Replicate Server. See Service name change from Attunity Replicate Server to Qlik Replicate Server
The default service is run as local system account, which will not have access to your SQL endpoint.
Qlik Replicate 2022.11 and later (upgrade)
Qlik Replicate was upgraded to 2022.11. The Qlik Replicate UI service fails to start post-upgrade.
Replicate version 2022.11
Review the repuictl.log stored in ~\replicate\data\logs and look for the following message:
Repository 'Global' or one of its ingredients are out of date, please run the following command to upgrade the repository: RepUiCtl.exe repository upgrade --repository <repository_full_path>
After verifying the error:
the "GlobalRepo.sqlite" file did not get update during the upgrade process.
Qlik Catalog container won't start due to the error:
Error: error creating container storage: the container name "catalog-pod-engine" is already in use by "xxxxxx". You have to remove that container to be able to reuse that name: that name is already in use.
The container already exists.
Qlik Replicate logs the following warning:
]W: MS-REPLICATION is not enabled for table 'dbo.YourTableName'. Therefore, UPDATE changes to it will not be captured. If you want UPDATE changes to be captured, either define a Primary Key for the table (if missing) or enable Microsoft CDC instead.
However, the table has a Primary Key and exists in an MS-Replication Publication not created by Qlik Replicate.
USE DBName
DECLARE @publication AS sysname
SET @publication = N'ProdArticlesNoSubs'
USE DBName
EXEC sp_changepublication
@publication = @publication,
@property = N'immediate_sync',
@value = true
GO
USE DBName
DECLARE @publication AS sysname
SET @publication = N'ProdArticlesNoSubs'
USE DBName
EXEC sp_changepublication
@publication = @publication,
@property = N'allow_anonymous',
@value = true
GO
When the Publication is set for immediate_sync is set to 'false' and allow_anonymous is set to 'false'. This causes the table that being replicated not to register to the sys.table.
Qlik Replicate 2021 and later
You are seeing a large number of tasks failing.
When checking your QlikView Distribution Service logs you can see issues to open files.
Example:
Error: Cannot open file: '\\qlikview.domain.local\Qlikview\QlikViewStorage\Reporting\QVD\2021\xyz.qvd' (System error: Failed to open file in write mode for file: \\qlikview.domain.local\Qlikview\QlikViewStorage\Reporting\QVD\2021\xyz.qvd)
When checking for the QVD on its network location you can observe a size at 0 KB
QlikView April 2020 SR3 (12.50)
To troubleshoot this issue please follow these steps:
A user opens the QlikView Desktop and attempts to lease a license from the QlikView Server. However, after successfully connecting and authenticating and even opening a QlikView document, the Desktop client remains unlicensed (Personal Edition).
Relevant log file:
The relevant log file to review on the QlikView server to verify if the user has arrived and has attempted to lease a license is the QlikView Server Event log. Note that it will only log the relevant lines when set to High logging level.
Example results:
See How To Lease License From QlikView Server To QlikView Desktop Client for more details.
License lease is not allowed for test license, see QlikView Test Server FAQ for more details on test licenses.
This means that if the user is opening QlikView from the correct shortcut everything is fine, but if he double clicks a .qvw a different version might open, breaking the lease. See How To Associate .QVW Extension To A Specific Version Of QlikView for detail on changing the QVW file association in Windows.
This can cause problems if the user connects to many different servers in a Citrix "Farm" during this time. A single user can lease up to two licenses to two separate workstations within a 24 hour / 7 day period. An attempt to lease the third license in a 24 hour / 7 day period will be revoked if the same User ID is used. Additionally, the existing license lease of the third machine, should there be one previously existing, will be revoked in the case where the same User ID has leased a license from two other workstations in the previous 24 hour / 7 day period. The third machine will, however, be able to lease a license after 24 hours / 7 days have passed.
The Lease info is stored locally in the profile, so if they no longer have access to it they will lose the lease. Look for root cause details in the LeasedLicense section of C:\Users\\AppData\Roaming\QlikTech\QlikView\Settings.ini. The LeasedLicenseCheck value shows more details on why the license lease has failed.
LeasedLicenseExpiry=
LeasedLicenseServer=
LeasedLicenseCheck= INVALID
You can also open via QlikView Desktop Client > Help> Document Support Information and search for the parameters above, as below:
This is specified as a NUMBER_OF_DOCUMENTS tag in the license LEF file.
Verify that the following registry key is present:
Registry > HKEY_CURRENT_USER > Software > QlikTech > QlikView
This will allow the license to lease initially, but the lease will be removed once the temporary profile is cleared out. You can check for this after the user logs in by going to C:\Users and looking for the login name. If it's not there, and there is a Temp folder, check there. One fix would be to disable temp profiles.
This typically the case when error "Connected to server OK, Negotiations Timed Out Switching to HTTP tunneling" is returned.
A Line chart displayed the error:
The chart is not displayed because it contains only undefined values
This is Working as designed. The axis was TEXT data, and the Continuous Scale can only be used for numeric values. See Line chart properties | Qlik Sense on Windows Help and Line chart properties | Qlik Cloud Help
X-axis <Dimension>