Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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.
Some of connectors provided by Qlik are not visible in the Data Load Manager. They are only available in the Script Editor.
This article provides a complete list of them.
This is the list of the Qlik connectors available only on the Script Editor and not on Data Load Manager:
AI21 Labs (Amazon Bedrock),
Advanced Analytics,
Amazon Comprehend,
Amazon SageMaker,
Amazon Titan (Amazon Bedrock),
Anthropic (Amazon Bedrock),
Azure ML,
Azure OpenAI,
Cohere (Amazon Bedrock,
DataRobot,
Databricks MLflow,
Google Ads,
Google Calendar,
Hugging Face,
Meta (Amazon Bedrock),
MeaningCloud,
OData,
OpenAI,
Qlik AutoML,
Qlik Big Data Index (QBDI),
Qlik GeoOperations,
Qlik GeoOperations GeoJSON,
Qlik GeoOperations Shapefile
Sentiment140,
SMTP,
Watson Natural Language Understanding,
YouTube Analytics.
These connectors visible only on the Script Editor for a current limitation of the product.
Notice that also Custom Connectors are available on the Script Editor only, as stated here.
IM-6179
When using an MS SQL server target with Use "BCP for loading tables" checked in the advanced page of the endpoint the target field will contain 1 or 2 bytes.
Uncheck "BCP for loading tables"
Limitation and considerations #Limitation and considerations | Qlik Replicate Help
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.
Starting from version "November 2021" (Version 2021.11), Qlik Replicate introduced support for log data encryption to safeguard customer data snippets from being exposed in verbose task log files. However, this enhancement also presented its own set of challenges, such as making it very difficult to read the logs and complicating troubleshooting processes, the steps of Decrypting Qlik Replicate Verbose Task Log Files takes time.
In response to customer feedback and feature requests, we implemented a new feature allowing users the flexibility to disable log encryption in Qlik Replicate. This enhancement was rolled out with the release of Qlik Replicate version 2023.5 GA. This article serves as a guide on how to effectively disable Task Log Data Encryption.
{
"port": 3552,
"plugins_load_list": "repui",
... ...
"enable_data_logging": true,
"disable_log_encryption": true
}
Important Note:
Please exercise caution as verbose task logs may contain sensitive end-user data, and disabling encryption could potentially lead to data leakage. Always ensure appropriate measures are taken to protect sensitive information.
How to Decrypt Qlik Replicate Verbose Task Log Files
The Qlik Reporting Service is a value add offering in Qlik Cloud that allows customers to achieve higher complexity enterprise reporting style use cases.
The service allows for the production of advanced compositions of documents sourced from Qlik Cloud analytics and works with platform capabilities that allow for complex task definition that reach varied stakeholders who don’t have access to Qlik Cloud or may not be primary users.
These types of reporting use cases are often centralized to users who have skill-sets in analytics composition and report document development. For more on these capabilities from the value add services see
When working with the Qlik Reporting Service please be sure to understand your Cloud Subscription as per our product terms.
There are other capabilities on Qlik Cloud that allow users to access simple distribution use cases including:
Please reference the Qlik Cloud Government help page for the latest on distribution capabilities
Please note that Qlik on-premise features and capabilities are different for Qlik Sense and QlikView on Windows where value add products Qlik NPrinting and Qlik Alerting can be considered to achieve various report and report distribution use cases. The application download behaviors for Qlik Sense on Windows and QlikView utilize different services from those in Qlik Cloud so outputs will often differ.
It is possible to filter records based on range values set in the 'Filter' Window. This article is an example of setting this up as opposed to setting a Record Level or a Full Load Pass thru filter. We are filtering user_id values 25 and less.
Source table:
Within Task Designer -> Table Settings -> Filter
By clicking on the edit button:
If you export your task to see how it looks in .json format:
Target data after running the task:
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.
Other article on filtering for reference:
Starting from Qlik Replicate version "November 2021", when the logging level is set to Verbose, sections in a Replicate log file that might contain customer data will be encrypted while the rest of the log will remain in clear text, this is implemented by the enable_data_logging configuration parameter set to true by default in order to prevent customer data snippets from appearing in verbose logs.
The sample line of the task log file looks like this:
2021-11-05T15:45:11:390848 [AT_GLOBAL ]I: Logging of database data is disabled (at_logger.c:2702)
However, in some support cases, R&D may require the ability to decrypt the log in order to analyze the problem. In such cases, Qlik Support will ask you to provide the task or environment-level encryption key and corresponding task log files:
Below is the detailed steps how to enable the database data logging and decrypt a task log file with corresponding log.key files.
2021-11-05T15:59:07:969146 [AT_GLOBAL ]I: Log file encryption base "755opF/9oGw7YOx+2ma0dA==" (at_logger.c:2695)
2021-11-05T15:59:07:969146 [INFRASTRUCTURE ]I: The log level for 'TARGET_APPLY' has been changed from 'INFO' to 'VERBOSE'. (at_logger.c:2927)
2021-11-05T15:59:07:969146 [INFRASTRUCTURE ]I: The log level for 'SOURCE_CAPTURE' has been changed from 'INFO' to 'VERBOSE'. (at_logger.c:2927)
... ...
2021-11-05T16:02:21:346746 [SOURCE_CAPTURE ]V: Event of captured table 'SCOTT.KIT' (data object id '93719', object id '93719') (oradcdc_parse.c:303)
2021-11-05T16:02:21:346746 [SOURCE_CAPTURE ]V: xid [000008fb00100007] (oradcdc_parse.c:166)
2021-11-05T16:02:21:346746 [SOURCE_CAPTURE ]V: BI col 2 [5]
~uAAAABvF/duclauaOYlVdTbsCpbAiSZGsq3DIp8XyImAZjY984KVgc62Lir20Mnw1VU1V/54j/vXa4BXpyQ7rjcEPR1MtjoYnpPSeu4QSwfiUx3l}~ (oradcdc_parse.c:340)
The encryption key file (log.key file) can be used to decrypt any log that was encrypted with it, not just the log for which Qlik Support requested the encryption key file. If this is a concern, you can generate a log.key file that will only be valid for the specific log requested by Qlik Support.
To do this:
If you do not want verbose logs encrypted, open <REPLICATE_INSTALL_DIR>\bin\repctl.cfg and set the enable_data_logging parameter to false then restart the Replicate server service. Add the line if you do not see it in the file.
Products: Qlik Replicate
Sometimes we need to join different tables in the source databases and filter records according to another table records values. In this article we are using Oracle source endpoint, to demonstrate how to build up such a task in Qlik Replicate.
In the below sample task, table testfilter will be replicated from Oracle source database to SQL Server target database. During the replication, the records which value is INACTIVE in table testfiltercondition will be filtered out and are ignored in both Full Load and CDC stages. The two tables are joined by the same primary key column "id".
In the above expression, the 2 tables testfilter and testfiltercondition are joined by the PK column "id" in function source_lookup.
#00145952
QnA with Qlik: Qlik Replicate Tips
Application Automation Mail Block run history give the following error
Malformed UTF-8 characters
There is a problem with your email server provider.
Please use a different simple authentication email server mail box ie: Gmail (see link below)
Email server issues that must be rectified by the email administrator or by changing email service provider for Application Automation email delivery.
I cannot connect my SMTP server in the Qlik Applic... - Qlik Community - 1984572
I cannot connect my SMTP server in the Qlik Applic... - Qlik Community - 1984572
QB-24626
An escalation is a request from a customer concerning a specific case that is currently under
investigation by Qlik Support. The customer has a case that has business-critical impact without a workaround provided and requires a faster resolution than what is provided in the standard resolution process.
The Escalation Management process aims to bring order, structure, focused management attention and additional resources to those customer situations which could otherwise result in a high level of customer dissatisfaction. Any Qlik® customer or partner with a valid maintenance contract may initiate an escalation on an existing support case. Escalations are intended for existing cases. Please do not report new issues through Escalation Management. New issues should be raised through the Qlik Support portal.
Escalations can occur for several reasons. Having a defined process allows Qlik to identify, track, monitor and manage situations that require increased awareness and quick action.
Please note that for an issue to be escalated, a support case must first be created (we will not accept escalations solely based on communications via email). If a case has been worked through our standard support processes and with our teams and you are not satisfied with the level or timeliness of service you received, you can escalate accordingly. See Escalation Triggers for more information.
Americas |
Qlik Data Analytics ProductsGiuseppe Novello Akshesh Patel Qlik Data IntegrationJayashree Guin Robert Kittles Christian Tan Lori Wittal Evan Teitelbaum TalendChristian Tan |
EMEA |
Qlik Data Analytics ProductsAlbert Candelario Benoit Canal Patrick Vanotti Qlik Data IntegrationAnne Arnoult Dmitry Dmitriev Fabio Cunha TalendAnne Arnoult |
APAC |
Qlik Data Analytics ProductsKiran Shankar Ayaka Hanazono Yasser Ahmed Kahn Sankar Reddy K Qlik Data IntegrationJohn Wang Ravi Chintam Robin Patel Shaona Zhang TalendRobin Patel
|
Global Customer Support |
Qlik Customer SupportSuresh Kumar |
Americas | Hien Le hien.le@qlik.com |
EMEA | Réginald de Visscher reginald.devisscher@qlik.com |
APAC |
Robin Patel |
Global | Daniel Coullet daniel.coullet@qlik.com |
Qlik Replicate SAP Extractor Endpoint can be tuned to improve the performance of data being processed from an SAP environment. This is achieved by adding an internal parameter: sqlConnector. To confirm the performance improvements of the task, first record the task duration before implementing the parameter, then compare it to the subsequent runs.
Before the internal parameter can be added to the Qlik Replicate Extractor Endpoint, the below SAP Transports must be installed:
Once the transports have been installed make sure you follow the below steps to set the added Permissions on the SAP Replicate User:
Add the following authorization objects and settings to the RFC user ID:
Do the following:
For more information on how to import/upgrade the sqlConnector Transport, see Importing the SAP transports.
Configure the SAP Extractor Endpoint by defining the useSqlConnector Internal Parameter.
SAP Transports
Importing the SAP transports
When access Qlik Cloud from Qlik SAAS mobile app, you are faced with the following error:
"You are logged in to too many devices"
To resolve this, you need to ensure each Qlik Mobile SAAS user logs out of each session when finished working.
This generally occurs when an IDP is configured and users do not log out of the session. Even though the device is the same, a new session opens when users access the app from a new network or location.
The IDP or device might consider this a new session and the old session will remain open in the background
In some cases Qlik Sense master measures used in charts included in Qlik NPrinting report templates are not expanded in the produced reports as described in the following community discussions:
Two workarounds:
Note: The steps above may be performed on versions of Qlik Sense from the Feb. 2021 GA release and later versions. Previous versions of Qlik Sense do not support this Qlik Sense feature/option setting.
Related Community Discussion:
Internal IDs:
Qlik NPrinting Engine issues may result due to:
In some cases, the NPrinting Engine server service will not start, is offline in the NPrinting Web Console Engine manager or results in "Something Went Wrong with the current operation" or similar error message
Engine Offline:
Something went wrong with the current operation:
Verify that:
*Before proceeding below, we recommend restarting the Qlik Sense, QlikView and NPrinting servers to ensure that Windows memory leakage is not the root cause of NP Engine Offline issue*
If updating the Antivirus exceptions and server clock time and time zones do not resolve the issue, do the following:
Engine Installation Steps for Current NPrinting Versions:
Any endpoint that uses the feature flag (FF) “More option” is not working in 2023.11.0.159 (GA) and 2023.11. 226 (sp01).
When testing the endpoint with “more option” the connection will get stuck and won't start the progress on the test connection progress bar forcing you to refresh or reload the URL to come out of the stuck connection.
Note: The feature flag “more option” works fine in 2022.11.0.208 and the higher version of 2022.11. But fails to connect in 2023.11.0.159 (GA) and 2023.11. 226 (sp01).
Qlik has identified this as a defect and is working on a fix for this issue. At this point, we do not have an ETA yet. So please kindly subscribe to our Community page to stay updated on the latest news & fix for this issue.
User are requested to re-enter their credentials when they launch an On-Demand request from a device not running windows, for example a Mac computer.
This does not happen to the same users when working on Windows OS machines.
When an On-Demand request is launched, the user credentials are passed to NPrinting by the Integrated Windows authentication (IWA).
This functionality is only available on Windows machines. The credentials entered when the user has logged to Qlik Sense can't be passed if IWS is not active, as happens on any devices that does not run a Windows OS.
This is due to a limitation on the operating systems and can't be fixed by Qlik.
Below error will appear when you execute the "Bootstrap" command to generate/regenerate the Certificates while you are migrating or upgrading the Qlik Sense Environment,
[ERROR] Fatal exception during bootstrap: There is no RSA private key associated with this certificate
Note: Please take assistance from your Admin/IT Team if you are not aware of the Certificates issued to your Qlik Sense site.
Tip:
After regenerating the certificates, if your UDC and Data Connections are failing, you must re-enter the passwords to all data connections and UDCs, since those encrypted passwords have a hash reference back to those certificates, once you remove the Certificates and create new ones, that reference gets broken, a new hash needs to in place, and to do so, you must re-enter the password.
[ERROR] Fatal exception during bootstrap: Keyset does not exist
Creating 40 permanent worker threads for connection handler
The Search within the Discover function in Compose does not pick up changes in the source, once the Search has been done once. I created a Replicate task for some new tables, residing in their own landing database schema. The first time that I did a Search within the Discover function, it discovered them just fine.
I later added another table to the Replicate task, and it was created in the designated schema in the landing database. However, when I do a Discovery Search in the model, it does not detect any changes.
When you try to discover the table, if it doesn't show up, click the circled "Clear Cache" arrow above the table list, and it should then be included in the list.
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.
Umlaut letters like ä, ü or ö are shown incorrectly in the headers of QlikView tables when they are imported from QVD files (see the image below).
It is necessary to save the .qvs file in UTF + BOM format.
The necessity of saving the .qvs file in UTF + BOM format is due to Windows configurations. Before UTF8 become the standard, Windows text-files where typically using "ANSI" or "ISO 8859". When UTF8 and UTF16 come along there was a problem "knowing" what format a text file is using. Windows solved that using BOM. Since QlikView was created before UTF 8 was the most used encoding scheme, it now require BOM to identify the correct encoding of text-files.
It is also possible to explicit the encoding scheme in loading table files in the script.
After upgrading Qlik NPrinting to May 2023 SR 2, reports containing section breaks inside of levels will start to see the following failure message:
ERROR: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Upgrade to Qlik NPrinting May 2023 SR3.
Information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes, or contact support with the ID OP-95937 for reference.
Qlik May 2023 SR3
Remove the section break and insert a page break.
Product Defect ID: OP-95937