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 the Case Portal. (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:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
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.
Question I
What are the compatible operating systems?
The compatible operating systems can be found in the article: compatible-operating-systems.
Please check the section: Talend Remote Engine.
Question II
What are the compatible Java environments?
Java 8, Java 11, Java 17 can be used for task executions. By default, Talend Remote Engine uses Java 17 to run tasks. The compatible Java environments can be found in the article: launching-talend-cloud-remote-engine-for-aws-via-cloudformation.
Please check the section: Procedure ⇒ Step 10.
Furthermore, there are no differences whether Talend Cloud Remote Engine for AWS is launched using Cloud Formation or AMI.
Question III
Where is the Remote Engine installed?
It is installed in the following directory.
/opt/talend/ipaas/remote-engine-client/
Question IV
Where can I find the settings file to make parameter changes?
The settings file is located in the following directory.
/opt/talend/ipaas/remote-engine-client/etc/
Question V
Where can I find further details on Talend Cloud Remote Engine for AWS?
Please refer to Qlik Talend Documentation: talend-cloud-remote-engine-for-aws.
For general advice on how to troubleshoot Qlik Replicate latency issues, see Troubleshooting Qlik Replicate Latency and Performance Issues.
If your task shows latency issues, one of the first things to do is to set the logging component performance to trace and run the task you identified for five to 10 minutes and review the resulting task log.
We advise you to:
This will list all available latency information. We can now identify a trend.
Remember, Target latency = Source latency + Handling latency.
[PERFORMANCE ]T: Source latency 0.00 seconds, Target latency 0.00 seconds, Handling latency 0.00 seconds (replicationtask.c:3703)
The source, target, and handling latency are all at 0 seconds.
[PERFORMANCE ]T: Source latency 7634.89 seconds, Target latency 7634.89 seconds, Handling latency 0.00 seconds (replicationtask.c:3793)
[PERFORMANCE ]T: Source latency 7663.00 seconds, Target latency 7663.00 seconds, Handling latency 0.00 seconds (replicationtask.c:3793)
[PERFORMANCE ]T: Source latency 7690.12 seconds, Target latency 7693.12 seconds, Handling latency 3.00 seconds (replicationtask.c:3793)
[PERFORMANCE ]T: Source latency 7710.25 seconds, Target latency 7723.25 seconds, Handling latency 13.00 seconds (replicationtask.c:3793)
The source latency is higher than the handling latency. The key point is to look at handling latency, it must be lower than the source latency.
Cause:
If the source latency decreases during your monitoring, it is a good sign that the latency will recover; if it increases, review the causes mentioned above and resolve any outstanding source issues. You will want to consider reloading the task.
[PERFORMANCE ]T: Source latency 2.05 seconds, Target latency 7116.05 seconds, Handling latency 7114.00 seconds (replicationtask.c:3793)
[PERFORMANCE ]T: Source latency 2.77 seconds, Target latency 7150.77 seconds, Handling latency 7148.00 seconds (replicationtask.c:3793)
[PERFORMANCE ]T: Source latency 2.16 seconds, Target latency 7182.16 seconds, Handling latency 7180.00 seconds (replicationtask.c:3793)
The target latency is higher than the source latency.
Cause:
If the target latency continues to increase, consider reloading the task.
Identifying whether or not you are looking at handling latency or target latency can be tricky. When the task has target latency, the queue is blocked, so the handling latency will automatically be higher as well (remember: Target latency = Source latency + Handling latency).
The key point to decide if it is handling latency is to check if there are a lot of swap files saved in the sorter folder inside the task folder of the Qlik Replicate server.
In addition, if the task log shows when the task is resumed, the handling latency increases dramatically from 0 seconds (or a low number) to a much higher value in a very short time. This can then be clearly identified as a handling latency:
2023-05-10T08:21:02:537595 [PERFORMANCE ]T: Source latency 5.54 seconds, Target latency 5.54 seconds, Handling latency 0.00 seconds (replicationtask.c:3788)
2023-05-10T08:21:32:610230 [PERFORMANCE ]T: Source latency 4.61 seconds, Target latency 55363.61 seconds, Handling latency 55359.00 seconds (replicationtask.c:3788)
This log shows handling latency increased from 0 seconds to 55359 seconds after only 30 seconds of a task's runtime. This is because Qlik Replicate will read all the swap files into memory when the task is resumed. In this situation, you need to reload the task or resume the task from a timestamp or stream position.
After a DB2 LUW upgrade from 11.1 to 11.5, Qlik Replicate tasks which read from the upgraded DB2 LUW Source Endpoint fail with the error:
[SOURCE_CAPTURE ]I: Error reading log buffer (db2luw_endpoint_proc.c:679)
[SOURCE_CAPTURE ]E: Error at 'Reading log records': Unexpected Error. Original SQLCODE -1263: ' message SQL1263N The archive log file "S0534570.LOG" is not a valid log file for
database "R3P" on database partition "0" and log stream "0".
Perform a reload of the Qlik Replicate Task(s) and Table(s) which use the DB2 LUW Source Endpoint.
Upgrading a DB2 LUW environment changes the DB2 Transaction log format.
References:
Start Event Viewer (Windows Server)
https://technet.microsoft.com/en-us/library/cc766401.aspx
What information appears in event logs? (Windows Server)
https://technet.microsoft.com/en-us/library/dd349798(v=ws.10).aspx
Open Event Viewer (Windows 7)
http://windows.microsoft.com/en-au/windows/open-event-viewer#1TC=windows-7
What information appears in event logs? (Windows 7)
http://windows.microsoft.com/en-au/windows/what-information-event-logs-event-viewer#1TC=windows-7
Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch.
All Qlik Replicate versions older than the 2024.5 SP03 release are affected.
Upgrade to Qlik Replicate 2024.5 SP03 or later once available.
In the meantime, Qlik has made early builds of 2023.5, 2023.11 and 2024.5 available.
Download the early builds here:
2023.5 SP07: https://files.qlik.com/url/qjfazk7fxftjmncu
password: cdesfgb8
2023.11 SP05: https://files.qlik.com/url/ndafzunah2srntqt
password: bl3xrefv
2024.5 SP03: https://files.qlik.com/url/fbfsznjidxt5nzra
password: cygie73l
The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly.
RECOB-8698
Oracle Database 19c Release Update July 2024 Known Issues
As a general reminder, all changes to the environment such as operating system patches, endpoint and driver patches, etc. should be tested in lower environments before promoting to production.
Using the qlik-cli it is possible to import a list of users to a tenant from a csv file.
It will be then possible to assign roles, entitlements and space permissions to the users before they log in to the tenant.
Here's a possible example of how to do that.
Name,Email
Mick Case,Mick.Case@example.com
Davide Bironi,Davide.Bironi@example.com
Kenny Handsley,Kenny.Handsley@example.com
Leigh Kersriver,Leigh.Kersriver@example.com
Gerry Vain,Gerry.Vain@example.com
Tommy Ioni,Tommy.Ioni@example.com
Terence Attendant,Terence.Attendant@example.com
John Oughborne,John.Oughborne@example.com
William Guard,William.Guard@example.com
Renato Padovano,Renato.Padovano@example.com
# Import the csv file as an array of objects
$csv = Import-Csv -Path userlist.csv
# Initialize a counter for the subject
$counter = 1
# Loop through each object in the array
foreach ($row in $csv) {
# Generate the subject using the counter
$subject = "ExampleSubject" + $counter
# Execute the qlik-cli command with the column values and the subject
qlik user create --name $row.Name --email $row.Email --subject $subject
# Increment the counter
$counter++
}
#!/bin/bash
# Get the number of lines in the csv file
lines=$(wc -l < userlist.csv)
# Loop from the second line to the last line (skipping the header row)
for ((i=2; i<=lines; i++))
do
# Get the name and email values from the ith line using cut
name=$(cut -d, -f1 userlist.csv | sed -n "${i}p")
email=$(cut -d, -f2 userlist.csv | sed -n "${i}p")
# Generate the subject using the counter
subject="ExampleSubject$counter"
# Execute the qlik-cli command with the column values and the subject
qlik user create --name "$name" --email "$email" --subject "$subject"
# Increment the counter
((counter++))
done
NOTE: users will be created with a temporary SubjectId like "ExampleSubject1", "ExampleSubject2", and so so on. After the first login, users will get a proper SubjectId.
Roles, entitlements and space permissions will follow the users to the new subject.
Alternatives ways of adding users via scripts might be achieved via the an /api/v1/users CALL with the POST method and a payload like:
PAYLOAD:
{
"email": "name@example.com",
"name": "First Lastname",
"subject": "SubjectXYZ"
}
The information and the files in this article are provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
Since QlikView 12.90 IR, the QlikView event log will no longer track license events (such as entitlement or CAL usage) when the log verbosity is set to medium.
Top track usage data set the verbosity to high.
Previous versions tracked license events at the medium log level. The behavior in 12.90 IR was identified as a defect which is aimed to be resolved with 12.90 SR1.
QV-25376
If a Qlik Sense document uses Section Access to restrict user access, the following error may be seen during data load:
Access was denied after reload. Check that the user that reloads the script is included in the section access part of the script.
Multiple root causes and matching solutions exist:
Verify that the user executing the script has ADMIN access in the Section Access table.
All field data (such as userID, email) must be written in upper-case.
Make sure the column names are correct. If these are not matched, use an "as" prefix to adjust it.
Example: ACCESS, USERID, USER.EMAIL
LOAD ACCESS,
EMAIL as USER.EMAIL,
REDUCTION,
OMITGROUP;
SELECT ACCESS,
EMAIL,
REDUCTION,
OMITGROUP
When using Google Cloud BigQuery as the target endpoint, tables are created without a Primary Key (PK) by default, even if the source table has a PK defined. This behavior is by design. In this article, we demonstrate how to modify this behavior, allowing Qlik Replicate to create a Primary Key in the target table when the source table has a PK defined.
To change the behaviour, add the Internal Parameter $info.query_syntax.create_primary_key to the Google Cloud BigQuery target endpoint:
When working with Google Cloud BigQuery as the target endpoint, the NUMERIC data type in the source database (e.g., IBM DB2 for iSeries) is mapped to the NUMERIC data type in Google Cloud BigQuery by default. Specifically, it defaults to NUMERIC(38,9), where the precision is 38 and the scale is 9. This allows for the exact representation of decimal fractions, making it suitable for financial calculations.
However, there are scenarios where optimizing data type mapping can help save storage space. This article is useful if you want to modify the default precision and scale. For example, instead of mapping the source NUMERIC(18,2) to the default NUMERIC(38,9) in Google Cloud BigQuery, you might prefer to map it directly to NUMERIC(18,2).
Additionally, the CHAR and VARCHAR data types in the source database map to STRING in BigQuery. By default, it maps to STRING, which implicitly means STRING(65535). This can be adjusted as needed to further optimize storage. In this sample, it maps to STRING($LENGTH). For example the CHAR(20) in source database maps to STRING(20) in GBQ.
From the Qlik Replicate computer where you want to import the task, open the Qlik Replicate command line console by doing the following:
From the Start menu, expand Qlik Replicate and then select Qlik Replicate Command Line.
A command-line console is displayed with the correct prompt for Qlik Replicate.
Alternatively, open a Windows Command Prompt using As Adinistrator and change to "<product dir>\Attunity\Replicate\bin" (default location)
repctl.exe getprovidersyntax syntax_name=BigQuery >> BigQuery_2024_5_NumericStringLength.json
command getprovidersyntax response:
[getprovidersyntax command] Succeeded
"provider_syntax": { "name": "BigQuery", "query_syntax": {Modified:
"provider_syntax": {
"name": "BigQueryNumeric",
"repository.provider_syntax": {
"name": "BigQueryNumeric",
"query_syntax": {
"rep_type": "kAR_DATA_TYPE_NUMERIC",Modified:
"provider_data_type": "NUMERIC",
"has_precision_condition": true,
"from_precision": 1,
"to_precision": 38,
"rep_type": "kAR_DATA_TYPE_NUMERIC",Original:
"provider_data_type": "NUMERIC(${PRECISION},${SCALE})",
"has_precision_condition": true,
"from_precision": 1,
"to_precision": 38,
"rep_type": "kAR_DATA_TYPE_STR",Modified:
"provider_data_type": "STRING"
"rep_type": "kAR_DATA_TYPE_STR",
"provider_data_type": "STRING(${LENGTH})",
repctl putobject data=BigQuery_2024_5_NumericStringLength
Do not add the additional suffix ".json" in the end of the command as this will cause the command to fail.
This article gives an overview of the available blocks in the Monday.com connector in Qlik Application Automation, as well as expand on basic example use-cases.
Monday.com is a powerful project management system — a complete Work OS designed to help your team complete projects efficiently, collaborate effectively, and grow online. And Qlik Application Automation supports implementations involving Monday.com.
Content:
Assets
Boards
Column
Folders
Groups
Items
Notifications
Raw API
Tags
Teams
Updates
Users
Workspaces
Similar use-cases can be implemented with other ITSM tools like Service-Now etc.
The Qlik Sense log files can be easily collected using the Log Collector.
The Log Collector is embedded in the Qlik Sense Management Console. It is the last item listed in the Configure Systems section.
For instructions on how to use the Log Collector, see Log collector (help.qlik.com).
Content
The user must be a root admin and have administrative permissions.
The best way to gather these logs is to use the Qlik Sense Log Collector. If the tool is not included in your install, it can be downloaded from this article.
This list provides an overview of what system information the Qlik Sense Log collector accesses and collects.
C:\Windows\System32\whoami.exe
C:\Windows\System32\netstat.exe -anob
C:\Windows\System32\tasklist.exe /v
C:\Windows\System32\netsh.exe advfirewall show allprofiles
C:\Windows\System32\ipconfig.exe /all
C:\Windows\System32\iisreset.exe /status
C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "ProxyEnable"
C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "proxyserver"
C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "AutoConfigURL"
C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "ProxyOverride"
C:\Windows\System32\ping.exe google.com
C:\Windows\System32\net.exe use
C:\Windows\System32\wbem\wmic.exe /OUTPUT:STDOUT logicaldisk get size
C:\Windows\System32\net.exe localgroup "Administrators"
C:\Windows\System32\net.exe localgroup "Qlik Sense Service Users"
C:\Windows\System32\net.exe localgroup "Performance Monitor users"
C:\Windows\System32\net.exe localgroup "QlikView Administrators"
C:\Windows\System32\net.exe localgroup "QlikView Management API"
C:\Windows\System32\systeminfo.exe
C:\Windows\System32\wbem\wmic.exe /OUTPUT:STDOUT product get name
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "gwmi win32_service | select Started
C:\Windows\System32\gpresult.exe /z
C:\Windows\System32\secedit.exe /export /areas USER_RIGHTS /cfg
C:\Windows\System32\secedit.exe /export /areas
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\currentuser\my | Format-list"
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\currentuser\Root | Format-list"
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\localmachine\my | Format-list"
C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\localmachine\Root | Format-list"
$FormatEnumerationLimit=-1;$Session = New-Object -ComObject Microsoft.Update.Session;$Searcher = $Session.CreateUpdateSearcher();$historyCount = $Searcher.GetTotalHistoryCount();$Searcher.QueryHistory(0, $historyCount) | Select-Object Title, Description, Date, @{name="Operation"; expression={switch($_.operation){1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"}}}} | out-string -Width 1024
C:\Windows\System32\netsh.exe http show urlacl
C:\Windows\System32\netsh.exe http show sslcert
Any versions of Qlik Sense Enterprise on Windows prior to May 2021, do not include the Log Collector.
If the Qlik Sense Log collector does not work then you can manually gather the logs.
For information on when logs are archived, see How logging works in Qlik Sense Enterprise on Windows.
Persistence Mechanism Current Logs(Active Logs) Archived Logs
Shared (Sense 3.1 and newer) | C:\ProgramData\Qlik\Sense\Log | Defined in the QMC under CONFIGURE SYSTEM > Service Cluster > Archived logs root folder Example enter (\\QLIKSERVER\QlikShare\ArchivedLogs) |
Synchronized (Sense 3.1 and older) | C:\ProgramData\Qlik\Sense\Log | C:\ProgramData\Qlik\Sense\Repository\Archived Logs |
Note: Depending on how long the system has been running, this folder can be very large so you will want to include only logs from the time frame relevant to your particular issue; preferably a day before the issue began occurring.
Qlik NPrinting SLK License cannot be applied or updated after the upgrade.
Licensing fails with:
The Licence Service is not responding. Restart the Qlik NPrinting License service
The Qlik NPrinting log files read:
"errorMessage":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": dial tcp: lookup license.qlikcloud.com: getaddrinfow: This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server.","errorType":"LICENSES-InternalServerError","level":"info","logTraceId":"bf71fd0bcf272dd3528824ac4fb5f3a6","statusCode":500
"error":"Post \"https://license.qlikcloud.com/v1/definitions/signed\": context canceled","level":"error","logTraceId":"d7c48ffd76242e3522db613652462ee5","message":"Failed to fetch license definition."
"errorMessage":"Too much time has passed since the last license update","errorType":"LICENSES-OutdatedLicense","level":"info","logTraceId":"e7c3a2cc454f5dc843b68e5bb5e6840c","statusCode":403
This issue is being caused by the license server being unreachable. If the server has internet connectivity, then the likely root cause is a proxy being deployed.
Follow these steps to troubleshoot and resolve the issue:
When you upgrade the Qlik Nprinting Server, the existing configurations files will be overwritten to default configurations files, and any changes done before the upgrade have to be updated again.
So make sure to take a backup of the Files (Eg: Config) and Folders before performing the upgrade.
Licensing service proxy authentication
Licensing Qlik NPrinting offline
Oracle-to-Oracle bidirectional tasks fail after an upgrade to Qlik Replicate 2024.05.
The tasks crash without an error or start failing with a duplicate constraint error on the attrep_loopback_prevention table.
This issue may also impact bidirectional tasks with other endpoints.
No fix or workaround is currently available. Qlik is diligently working on a solution and will provide a timeline for a patch by the end of September 2024.
QB-29163
When changing the name of a dataset, the source name still stays the same. This can be seen by uploading a “firstname.qvd" and renaming it to “secondname.qvd”.
The dataset's detail will show "firstname.qvd" as the source.
As a consequence:
Trying to load “FROM [lib://DataFiles/secondname.qvd]” will produce a "(Connector error: File not found)" error.
This is not a defect, it's how the product is designed.
A dataset represents a data resource with its properties such as name. The value of that is that you are able to use more user-friendly names of datasets without having to change the source names, which can be useful when the dataset is pointing to a database table for instance.
In the future, there is a plan to add the possibility of calling the name of the datasets in the script.
Consulting (often referred to as Professional Services) needs to be contacted when either one of the following is true:
To begin a Consulting services engagement, begin at Qlik Consulting: Boost your success with our expertise or contact your Account Manager.
Expect font not appearing in NPrinting Pixel Perfect PDF reports.
By Default, there are two fonts that can be selected in Pixel Perfect reports that will show the Chinese Characters,
Most of the other languages will not show the characters.
In the Pixel Perfect Editor, simply switch to MS Gothic font
Chinese, Japanese ,German, Spanish, Portuguese languages will now appear in the PDF format report export.
After upgrading from Talend Data Catalog version 8.0 to 8.1, installing remote harvesting server, and adding a server with Type: Local Network, Talend Data Catalog cannot connect to the server.
Since version 8.1, the default installation of a remote harvesting agent server only allows for a Local Network connection.
You must first use $MM_HOME/Setup.sh -wa MIMBWebServices on that remote harvesting server to be reachable by the main MM server.
For more information and new features about Talend Data Catalog 8.1, please refer to Qlik Talend Documentation
Talend-Data-Catalog-8.1
If a TCP connection is possible with Qlik's licensing server endpoint, testing the connection to license.qlikcloud.com will return the message default backend - 404.
When testing whether or not your Sense installation can successfully connect to the license backend, always test the connection with all nodes.
The 404 HTTP error code indicates the server was reached but could not find any content to be displayed in the URL address specified.
Another test would be to use telnet (which needs to be installed on the server) to confirm a connection to port 443 is possible:
If different results are returned:
There was an error when getting license information from the license server