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.
Importing a Qlik Sense App (.qvf) in the Qlik Sense Management Console fails. There are various causes for this issue and this article will help in identifying the most common root causes.
In the process of importing an App one must access the Sense QMC, Start-> Apps -> Import
- Select a QVF (App) to import using the Browse, and select <Import>.
This process will result in one of the following:
Review the log file for more detailed errors to assist in further troubleshooting. For basic log file information, see Logging Storage.
Locate the logs in the following locations:
C:\ProgramData\Qlik\Sense\Log\Repository\Trace\SERVERNAME_System_Repository.txt
C:\ProgramData\Qlik\Sense\Log\Engine\trace\SERVERNAME_System_Engine.txt
Note: If you are running a multi node environment, each node will have its own local copy. Review all of them. In addition, if the logs have been archived since the issue occurred, review the location of the archived log, which by default is in the configured Service Cluster location.
Verify that the account running the Qlik Sense Services has the correct permissions: It requires Read/Write permissions.
In the case of large Apps, verify that enough disk space is available. Check the available space on the central node's C:\ disk. Even if Sense is installed on another drive, C:\ (and its temporary folder) will be used for the calculation.
At least 2 times the App size need to be available for the import to succeed.
Example: If the app is 8 GB then a minimum of 16 GB free disk space is required to Import the app.
Qlik Sense shows error when importing an app - log files read "request entity too large"
Cannot import App (qvf) to the QMC "Failed to import app. Please check the log file"
Import of apps in Qlik Sense failed when FIPS is enabled
All users with the Automation Creator role can create automations.
To add or remove the Automations Creator role:
Automations at large can be enabled or disabled as a feature in Qlik Cloud. See Managing automations for more information on how to manage automations.
Also see a related video posted on Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly
This option is available in Qlik Sense June 2018 Patch 1 and later releases.
Description of related problem:
Getting errors "Connection to the Qlik Sense engine failed for unspecified reasons. Refresh your browser or contact our system administrator" for external users on other browsers except for IE when they open the Qlik sense app and leave it inactive until it exceeds the Firewall session idle timeout. This is followed by a connection reset for the TCP WebSocket session.
For Qlik Sense Enterprise for Business (Cloud), see Loading of an app is hanging when using QlikSense Cloud.
Cause:
TCP WebSocket connection is terminated by the firewall because the firewall is not receiving any TCP traffic such as keep-alive packets from client browser (e.g. Firefox, older Chrome versions). Specific web browsers have their own tcp keep-alive behavior.
This issue may be found with less frequency with IE because it sends the TCP Websocket keep-alive more frequent than any other main stream browser. Here are the default intervals for the three main browsers latest releases as of September 2020:
Default TCP-Keep-Alive intervals:
General info
This functionality is by default switched off not to affect any existing customers. Customers who do not experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it will send unnecessary traffic on the network. See How are WebSockets used in QlikSense ? for more information.
<add key="WebSocketPingInterval" value="0"/> <!-- Interval in seconds for the web socket ping to the client (a value of "0" is disabling the ping)–>
Where value is a suitable positive number depending on the inactive web socket timeout setting in the network. The effective interval that the Qlik Sense Proxy server will send keep-alive messages towards the client my oscillate between 2 x value and 1 x value, since it also takes into account backend inter-process socket activity. Eg: setting the value of WebSocketPingInterval to 30 may lead to keep-alive messages sent to the client every 30 or 60 seconds.It is possible that the same WebSocketPingInterval value has different behaviors in each Qlik Sense Hub section due to various network device. The value may keep the connection live in Dashboard but still lose connection in Data Load Editor. You may test with a lower WebSocketPingInterval value until the proper value is found to keep connection in all sections. For example, when connecting CloudFlare as web application firewall, the WebSocketPingInterval value may need to set to 10 seconds otherwise "connection lost" may still be received in Data Load Editor even the rest of Qlik Sense Hub keeps connected.
4. Restart the Qlik Sense Proxy Service.
Setting sensitivity in Qlik Catalog allows you to mark certain fields as sensitive, indicating that they require extra care to maintain security and privacy.
When exporting data, the chosen obfuscation method is automatically applied to sensitive fields to ensure confidentiality. Users are prompted to select the obfuscation method during the export process.
In more detail, administrators can configure sensitivity settings for individual fields, deciding which ones should be considered sensitive. Sensitivity enforcement applies obfuscation to sensitive fields upon export, hiding or transforming the data. Administrators can choose from different obfuscation methods like CharClassObfuscator, DigestObfuscator, NumericObfuscator, ConstantValueObfuscator, and DictionaryObfuscator.
Each method has its own way of transforming or masking the data. By selecting a specific obfuscation rule for sensitive fields, administrators can control how the data will be transformed when exported.
Examples of obfuscation methods include replacing digits and letters, converting values into hash codes, modifying numeric values, returning constant values, or mapping data to different values using a dictionary.
Overall, Qlik Catalog provides a way to manage sensitivity and apply obfuscation methods to protect sensitive data when published, ensuring that it remains secure and confidential.
To use the sensitivity feature for source fields:
Note:
The sensitivity feature for fields only applies when you publish to a target location using the Publish option in Catalog.
Qlik Catalog
After upgrading QlikView to May 2023 IR, charts may show as blank objects in Qlik NPrinting.
Qlik NPrinting Designer displays the images correctly in preview mode.
Qlik NPrinting Any version
QlikView May 2023 IR
Nprinting Reports: Excel, PowerPoint, PDF
This is currently being investigated.
The issue is found to be with QlikView May 2023 IR not with any Qlik NPrinting versions. It works perfectly fine with QlikView May 2022 SR2 and earlier supported QlikView versions.
Also, the problem occurs when Qlik View Server Connection is used in Qlik NPrinting connections.
QV-24977
Information on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID QV-24977 for reference.
Attempting to start the Data Movement server on Linux (service repagent start) fails with the following error:
Failed to start service
One of following error messages can be seen in the repsrv.log file in such scenarios.
Failed to write file
Failed to write entire file
The root cause is likely a lack of storage. See the Data Movement system requirements for details: Recommended hardware. Either free up storage by removing unnecessary files or directories, or increase the available capacity.
To verify current capacity run df -h from the root ( / ) directory.
To review which directories take up the most space run the following from root:
sudo du -h --max-depth=1 | sort -rh
To find files larger than 100MB which may clutter the storage, run:
sudo find / -type f -size +100M -exec ls -lh {} \;
Directory has reached 100% capacity and has consumed all of the storage that was available.
Qlik Data Movement
Opening the Qlik Enterprise Manager Analytics tab fails with the following error:
SYS-E-JSERVNAVAIL, Java service 'AnalyticsCtlClient' not yet available
SYS,JAVA_SERVICE_NOT_AVAILABLE,AnalyticsCtlClient(statusCode: 500
Reviewing the service log files indicates:
Failed to start jetty server. Failed to bind to /127.0.0.1:3102
A simple reboot of the server running the Qlik Enterprise Manager may resolve the issue. If the issue persists after a reboot, the process occupying port 3102 may need to be killed manually.
After upgrading to QlikView 12.70 SR2 users cannot open documents from the AccessPoint once the session timeout is reached. The following error is displayed:
Failed to open document, You don't have access to this document
QlikView May 2022 (12.70) IR to SR2
QlikView May 2023 (12.80) IR
This is caused by QV-24743 and QV-24830.
Fix scheduled to be released in:
Upgrade to the appropriate version when it has become available. Refer to the QlikView Release Notes for details once the versions have been released.
QV-24743 and QV-24830
In this article, we will outline steps listed in the user guide with the addition of screenshots for Windows installations for replacing self-signed certificates. We take these steps to ensure a secure connection to Replicate.
1. Stop the Replicate UI and Server services
2. As administrator, from the following location, C:\Program Files\Qlik\Replicate\bin, run
RepUiCtl.exe certificate clean
3. Create a new private key file (note this will be generated in the current working directory):
openssl genpkey -algorithm RSA -out private.key -outform PEM
4. Create the cert.crt file based on the private key file created earlier:
openssl req -new -addext "subjectAltName = DNS:SSL-TEST.exampledomain.com" -key private.key -x509 -days 365 -out cert.crt
5. Create the cert.pfx file based on previous info:
openssl pkcs12 -export -certpbe PBE-SHA1-3DES -keypbe PBE-SHA1-3DES -nomac -inkey private.key -in cert.crt -out cert.pfx
6. Import the newly created certificate, by double clicking on the cert.pfx file generated in previous step. This will open the 'Certificate Import Wizard.'
Select, 'Local Machine' and click next.
7. Specify the cert.pfx file you want to import. Click 'Next' and then enter the password from step #3.
8. Select 'Automatically select the certificate store based on the type of certificate', then click 'Finish'.
9. Open up Windows MMC for Certificates on Local Computer.
10. Place the newly imported certificate in the 'Trusted Certificates' folder
11. Run the command to delete anything current
netsh http del sslcert ipport=0.0.0.0:443
12. Double click on the certificate in trusted certs folder to find the certificate thumbprint under the details tab
13. Use this thumbprint in the certhash of following command:
netsh http add sslcert ipport=0.0.0.0:443 certhash=b26fae671d12ab9afcc82cd93321f7e00dc300d6 appid={4dc3e181-e14b-4a21-b022-59fc669b0914}
Restart the services and check if you have the lock icon on your Replicate URL.
Note: For chrome, you may need to also add the certificate to chrome://settings/security -> 'Manage device certificates' -> Trusted Root Certificate Authorities.
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 can occur when using SAP BW Connector to extract data from InfoProvider/CompositeProvider.
--------
[ERR] [QVX] RfcAbapException:JOB_CANCELLED
Job aborted, check log for Job /QTQVC/READ_MPDATA in Job Overview (transaction SM37)
---------
Reported bug QB-18952 was closed by R&D as WAD(working as designed) .
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-18952 for reference.
From the SAP System,
The allowed maximum width is 8192 characters.
From the INFOPROVIDER, if the field is of, for example 15282 characters wide, a simple workaround would be to split the extraction into two or more extractions. Then in Qlik Sense or QlikView, depending on your data model, use JOIN / CONCATENATE.
Product Defect ID: QB-18952
The native Qlik PostgreSql connector (ODBC package) does not import strings with more of 255 characters. Such strings are just cut off, the following characters are not shown in the applications. No warnings are thrown during the script execution.
The problem affects the Qlik connector but not all the DNS drivers.
Qlik Sense February 2023 and higher versions
Qlik Cloud
When TextAsLongVarchar is set, and the Max String Length is set to 4096, 4096 characters are loaded.
Notice that there still are limitations to this functionality related to the datatype used in the database. Data types like text[] are currently not supported by Simba and they are affected by the 255 characters limitation even when the TextAsLongVarchar parameter is applied.
Qlik has opened an improvement request to Simba to support them.
As workaround, it is possible to test a custom connector using a DSN driver to deal with these data types.
QB-21497
Qlik Replicate can read SQL Server backup transaction logs stored in Rubrik.
The setup requires the Rubik administration team to use the attached script and to modify it accordingly to guarantee compatibility with your deployment.
This script is provided as is. Qlik Support cannot provide continued support or maintenance of the solution. For assistance, contact our Professional Services.
Creating a subscription based on a visualization or a sheet in Qlik Cloud, the following error is displayed:
An SMTP server must be configured if you want to receive subscription emails. Please contact an administrator
Verifying the subscription in the Management Console shows:
There was a problem sending your email. please review your settings.
Creating a subscription | Qlik Cloud Help
Sometimes it might be necessary to deallocate licenses using the Qlik Command Line Interface, for instance in case of licenses allocated to users no longer in the system.
[
{
"created": "2023-04-03T11:24:05.101Z",
"excess": false,
"name": “Enzo Bearzot”,
"subject": "auth0|12345678”,
"type": "professional",
"userId": “userid1”
},
{
"created": "2022-08-17T11:50:04.647Z",
"excess": false,
"name": “Vittorio Pozzo”,
"subject": "auth0|910111213”,
"type": “analyzer”,
"userId": “userid2”
},
{
"created": "2022-08-17T11:50:04.647Z",
"excess": false,
"name": “Ferruccio Valcareggi”,
"subject": "auth0|14151617”,
"type": "professional",
"userId": “userid3”
},
{
"created": "2022-06-07T11:36:15.704Z",
"excess": false,
"subject": “18192021”,
"type": “professional”
},
{
"created": "2022-06-03T13:50:14.105Z",
"excess": false,
"subject": “22232425”,
"type": "analyzer"
},
]
The syntax below is for Unix shells. For usage in Windows Powershell add a "backslash" before each "doublequote" sign. '[{"subject"... will have to become '[{\"subject\"...
'[{"subject":"USERSUBJECT","type":"ASSIGNEDLICENSE"}]'
For instance, in the case of the final user in the list above it will be '[{"subject":"22232425","type":"analyzer"}]'
feed the string into this command:
qlik license assignment delete --delete STRING
With the example above you will run:
qlik license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
Run the command and wait for the result.
A "200" will confirm that the removal worked
% qlik license assignment delete --delete '[{"subject":"22232425","type":"analyzer"}]'
[
{
"status": 200,
"subject": "22232425",
"type": "analyzer"
}
]
Check the "Home" section of the management console to confirm that the allocation was removed
If Oracle is configured with a Physical Standby, and the Oracle LOG_ARCHIVE_DEST_n initialization parameter is configured with the DELAY option, running a Full Load and Apply Changes task on an Oracle Physical Standby instance may result in missing or erroneous data in the target database.
The following warning may be thrown in the log files:
Using standby database could have caused the missing events problem during Full Load and CDC synchronization.
If you do not have the DELAY parameter configured and there is no data loss, this warning message can be ignored. Please check with your DBA if the DELAY parameter is set.
This issue can be resolved using an internal parameter: standbyDelayTime, which should be set to a value little bit bigger than the Delay parameter of LOG_ARCHIVE_DEST_n initialization parameter. Units are in minutes.
For information on how to set internal parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?
This solution may lead to redundant records for a table without PK/UI if there were INSERT operations during that period. Example - LOG_ARCHIVE_DEST_2 = 'DELAY=10'
Reloading the Qlik Sense Connector in Qlik Lineage Connector Client Managed may fail with:
Connector of type 'QlikSense' not included in license. Canceling execution
You will also see an "Invalid License" error on the Cloud link.
#Qlik Lineage Connector
It may be necessary to remove line feeds (LF) and carriage returns (CR) from BLOB or CLOB datatype fields. However, Qlik Replicate tasks have a limitation on LOB fields preventing functions from being used on them.
Use a source lookup to retrieve the field value, bypassing the inherent data type.
The general form of the function is as follows:
source_lookup(TTL,'SCHM','TBL','EXP','COND',COND_PARAMS)
Use of the standard replace chars function:
replaceChars(X,Y,Z)
Combined usage for both functions for the transformation expression:
ReplaceChars(source_lookup(1,'DBO','table','field','id=?',$id),X'0A','|')
Qlik Replicate Transformation: Source Lookup - CLOB datatype - limitations on string functions
Data Enrichment functions
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.
SAML is not supported by default in QlikView but can be implemented by creating a custom authentication module that will convert SAML requests/responses to QlikView Ticket to log the user in.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, contact our Professional Services or engage in our QlikView Integrations forum.
Currently, this solution only works for SP initiated authentication. Making it work for IDP-initiated authentication might require further code changes in the library/module source code.
This has been tested with QlikView 12.10 SR7.
<GetWebTicket url="/QvAjaxZfc/GetWebTicket.aspx"/>
to<GetWebTicket url="/QvAjaxZfc/GetWebTicket.aspx">
<TrustedIP>fe80::b178:730a:5c2a:86d2%11</TrustedIP>
</GetWebTicket>
public void ValidateAttribute(SamlAttribute samlAttribute)
{
if (!Uri.IsWellFormedUriString(samlAttribute.Name, UriKind.Absolute))
throw new DKSaml20FormatException("The DK-SAML 2.0 profile requires that an attribute's \"Name\" is an URI.");
after
public void ValidateAttribute(SamlAttribute samlAttribute)
{
/*
if (!Uri.IsWellFormedUriString(samlAttribute.Name, UriKind.Absolute))
throw new DKSaml20FormatException("The DK-SAML 2.0 profile requires that an attribute's \"Name\" is an URI.");
*/
<QlikViewSaml
accessPointUrl="https://qlikserver1.domain.local/"
authenticatePage="QvAjaxZfc/Authenticate.aspx"
webTicketPage="QvAjaxZfc/GetWebTicket.aspx"
tryPage="https://qlikserver1.domain.local/qlikview/"
backUrl="https://qlikserver1.domain.local/webticketerror.html" />
Replace https://qlikserver1.domain.local/ by your qlikview server URL in the above code.<AllowedAudienceUris>
<Audience>https://qlikserver1.domain.local</Audience>
</AllowedAudienceUris>
<Federation xmlns="urn:dk.nita.saml20.configuration">
<SigningCertificate findValue="CN=qlikserver1" storeLocation="LocalMachine" storeName="My" x509FindType="FindBySubjectDistinguishedName"/>
*In this case, we use a certificate that has "CN=qlikserver1" as its distinguished name.<IDPEndPoints metadata="C:\idpdata\">
...
Qlik Sense or QlikView may not load all data from a CSV file.
Sometimes a special character is used to mark the end of the file. If this character is found in the middle of a text file (for example, enclosed by quotation marks), the file may not load correctly. In this instance, we can modify how Qlik Sense and QlikView read data.
Qlik Sense:
QlikView
Due to a problem with quotes or special characters in the file. See Help Site File Wizard: Type
Qlik Sense all supported versions, including Qlik Cloud
QlikView all supported versions
Previewing Qlik NPrinting report templates in the Qlik NPrinting Designer leads to the error:
An error occurred while elaborating the entity tags.
Please check if the entities are properly placed inside their level tags.
Error message:
TemplateEntities list does not contain this column
Parameter name: templateEntities
Qlik NPrinting Designer May 2023 IR, May 2023 SR 1
Upgrade to Qlik NPrinting May 2023 SR 2.
Information on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID OP-95892 for reference.
Replace the current Qlik.Reporting.Adapters.dll file in C:\Program Files (x86)\NPrinting\Designer\libs.
For this workaround to function, the installed Qlik NPrinting designer version must be May 2023 SR1.
Upgrade to May 2023 SR2 when released.
Qlik NPrinting May 2023 SR 2
OP-95892