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.
When exporting data from a Qlik Sense App, the Printing Service creates a temporary file which is stored in a temporary folder.
Exported XLSX files are stored in: C:\ProgramData\Qlik\Sense\Repository\TempContent.
The folder is in the node where the repository is installed.
The data is automatically deleted after 10 minutes by the Engine. This is not currently a configurable property.
How to change how long temporary excel files are stored by the QlikView server
Qlik offers a variety of coursework and training materials to help you adopt Qlik products faster and maximize their capabilities. Choose from Free online Courses, Self-paced Learning, Instructor-Led training, and custom Application Training.
Our existing offers can be found on Qlik's Training Site.
Content:
Tip! Once you get started, you can track your training progress and browse for more content in your personal Learning Portal.
Qlik Replicate does not support Oracle on Delphix.
It has not been tested nor certified with Oracle on Delphix. The use of the untested combination can lead to unexpected behavior.
Qlik Replicate
Oracle Delphix
Previewing or publishing a Qlik NPrinting report fails with the message:
Some of row's cells lay outside column
Remove any merged cells from the report.
This is caused by the 'Aspose' library Qlik NPrinting uses for generating reports.
Qlik Sense data files (.QVF) may contain sensitive organizational data. As such, even though Qlik Technical Support has a very strict Non-Disclosure Agreement, it may be desired to scrambled specific data before submitting apps Qlik Sense support for investigation.
For the currently available method in Qlik Sense Enterprise for Windows, see Scramble Sensitive Data In Qlik Sense Enterprise for Windows.
Data can be scrambled in two ways:
Before providing the scrambled application to Qlik Support, please check that you can still reproduce the issue within the scrambled application.
The attached automation_scramble_Support.json automation creates a copy of your app before scrambling the data.
To scramble your data using the automation:
If Automations are not enabled, or you do not have the correct subscription model, use the attached Qlik Script and Excel file to scramble the data.
To scramble data using an excel file and a Qlik script:
Binary;
$(Include=lib://NAMEOFSPACE:DataFiles/scramble.qvs);
CALL Scramble('lib://NAMEOFSPACE:DataFiles/scramble.xlsx');
Exit Script;
Idea / Feature Request - Data Masking
Alternative method using APIs and the DevHub: Data Scrambling in Qlik Sense
Scramble Sensitive Data In Qlik Sense Enterprise for Windows
To access the examples, visit the community post or download it from here.
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.
This article gives an overview of the Splunk Connector in Qlik Application Automation.
The Splunk connector has been created with the following use cases in mind:
The Splunk connector makes use of basic authentication. When connecting the connector, you will be prompted with the following popup screen:
Hostname: The hostname or IP address of the Splunk instance. Exclude the http(s):// part and the port number of the URL.
Username: The username you use to login to Splunk
Password: The password you use to login to Splunk
Use SSL: Select whether the management service of Splunk makes use of SSL. Default yes.
Management port: The port on which the management service of Splunk is running. Default is 8089. Providing no value will omit the port from the final URL.
To perform searches using the Splunk connector it is possible to perform a synchronous search as well as an asynchronous search. The synchronous search has a timeout of 50 seconds, with the asynchronous search it is possible to have a longer window before the automation will timeout.
The synchronous search can be done using the Synchronous Search block. In the Search Query block you will have to provide a splunk search query.
The asynchronous search block can be manually done using the block Asynchronous Search block. Then perform polling using the Get Search block using the returned Search ID. When finished, results can be obtained using the Get Results From Search block.
Alternatively it is possible to use the block Do Asynchronous Search and get Results. This block will perform the polling, only a search query has to be provided to obtain a list of results.
The other use of the Splunk connector is to send data into Splunk by making use of the HTTP Event Collector. An example usecase for this would be to send reload logs of a Qlik Sense app into Splunk.
To do this we will first have to create an HTTP Event Collector on the Splunk side.
To do this in Splunk go to Splunk in the web browser and go to Settings > Data > Data Inputs.
On this page you will see Http Event Collector. Press the Add new button.
Provide a name for the token and go to the next page. Select indexes to which this token can write. Click on Review and Submit. You will be given a token that you need to configure on the block.
In Qlik Application Automation make use of the Send Event block. For the inputs, enter the HEC token value. Provide the port for the HTTP event collector. This can be obtained from the Splunk HTTP Event Collector page when clicking on the Global Settings button. You can also find whether SSL is enabled for the HTTP Event Collector, select this value for the Hec_Use_Ssl parameter. Next, provide the index to which you're writing your events and provide a source string.
For data, you can map JSON message in the Event parameter.
The following example will perform a reload and send the reload log to Splunk:
In Splunk it is then possible to view the logs of the reload:
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 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.
After an upgrade to Qlik Sense Enterprise on Windows May 2023 patch 3 or later, REST connections fail with the following error:
"WITH CONNECTION" is not allowed. To allow "WITH CONNECTION", select Allow "WITH CONNECTION" in the connector settings.
The Allow WITH CONNECTION option is not exposed in the REST Connector GUI and cannot be changed.
Qlik Sense Enterprise on Windows August 2023 and later are not affected.
To resolve the issue, upgrade to August 2023.
To manually mitigate the issue in the May release branch, replace the qsdfw_qsefw_qlikview.qliksourceconfig file. Qlik is investigating a solution which does not require manual intervention.
Backup the affected file before continuing with the workaround. When taking the backup, do not keep the backed up file in the same folder. (see end notes)
This change must be done on all nodes and schedulers.
End notes:
The folder C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector can only contain one qliksourceconfig file with correct name: qsdfw_qsefw_qlikview.qliksourceconfig
If there are two qliksourceconfig files (even with different names, such as a backup), the first one in alphabetical order will be chosen.
QB-20735
Qlik Sense Enterprise on Windows May 2023 Patch 3 and later
Does not affect August 2023 and later releases.
QB-20735
The Qlik Community is a great resource where all Qlikkies can connect, collaborate and share with their peers, Qlik support engineers, Qlik product management, and Qlik experts!
Since multiple forums are available for each product, community users can post discussions in the most relevant area. Both new and experienced Qlik product users help others learn new tips, share information and provide solutions by replying to discussions. Qlik product managers, Qlik support engineers, Qlik product and services experts as well as Qlik community administrators are moderating all of the forums and blogs. Look for the headset icon to identify Qlik Support responses and the star to designate other Qlik employee responses.
What types of questions should be asked in the Qlik Community?
Search first before posting. Chances are someone else has already posted your question and answer. If the search does not result in an answer to your question, continue with posting on the Qlik Community. For step by step instructions on posting a question, check out this post. Any kind of question can be asked on the Qlik Community!
The Community is an excellent resource for asking how-to, scripting, app development and best practice questions. Some examples of questions include but are not limited to:
Note: Qlik Community pages, Qlik Help documents, and Qlik public knowledge articles are all regularly indexed by the major search services like Google. Be sure to append the product name when searching to retrieve specific results regarding Qlik (ex: Qlik, Qlik Sense, QlikView, NPrinting, etc). Qlik Community results as well as results from Qlik.com, Qlik Help and Qlik Support Portal display.
What information should I include when posting to the Qlik Community?
The more information the better! Depending on the question, more details may be required to get the conversation flowing. Try to provide as much detail as possible and don't be surprised if peers or other product experts may ask for more information. A solid post should include:
Once the question has been posted, make sure to set up notifications so you do not miss when others respond to and like your post. If a response is received that answers the question or solves the issue, be sure to mark the answer as correct by clicking 'Accept as Solution'. This will mark the post as solved and other Qlikkies will gravitate towards this post as it as a possible solution for their issue. Multiple responses can be accepted as a solution so make sure to select all that apply.
How can I participate in this great Community?
It's easy! Create a Qlik Community login and start surfing the forums. Add your thoughts and ideas to any post, let others know you've experienced the same behavior, or like any resolution that has helped you answer a question. Be kind, encouraging and offer any insight you can! Don't be afraid to post a question as others probably have the same one. For more information on using the Qlik Community, start here! Once you get started, navigate to our popular blogs and subscribe. Join a group. There so much you can learn and share when you are connected to the Qlik Community.
Thank you for being apart of this wonderful Community! Happy Qlikking!
The following error may occur when reloading data from Ms Excel: “Error: Too many columns in data source (16326) but the limit is 10000."
Defect QB-22272 reported to R&D
This was an intentional change introduced in Qlik Cloud but was obviously set as a default limit for Qlik Sense Enterprise for windows as well.
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 QB-22272 for reference.
As workaround, please add this parameter "MaxColumnsInDataSource=0" in "settings.ini" file
1. Stop Qlik Sense Engine service
2. Edit "settings.ini" file from C:\ProgramData\Qlik\Sense\Engine
3. MaxColumnsInDataSource=0 and save "settings.ini" file
4. Restart Qlik Sense Engine service and test
R&D is planning to turn back as it was before the latest release but I can't predict the version in which a fix will be available.
Product Defect ID: QB-22272
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