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:
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.
The max concurrent reloads can be configured in the Qlik Sense Management Console.
<ServerName>_System_Scheduler.txt
Domain\qvservice Engine connection released. 5 of 4 used
Domain\qvservice Engine connection 6 of 4 established
Domain\qvservice Request for engine-connection dequeued. Total in queue: 25
Use the "Max concurrent reloads" to limit the maximal concurrent tasks can be run at same time on current node. By default, it's set to 4, which means only 4 tasks can be run at same time on this node.
When the 5th task comes in:
On a multi-node deployment, tasks will be balanced from the manager node to any node(s) designated as workers.
It's highly advised to check if the central node configured is set to Manager and Worker or Manager. When set to Manager, it will send all reload jobs to the reload/scheduler nodes, as it should. However if a central node is set to Manager and Worker, this means the Central node will also be involved in performing reloads. This is not recommended.
The work flow looks as follows:
The improvement to track the Max concurrent reloads can, if desired, be disabled. This reverts Sense to an older load balancing method that relies only on CPU usage.
To disable the setting:
In our example, we allow one concurrent reload, but we assume that two reloads are executed at the same time.
If a tenant previously had an incomplete SMTP configuration with their Qlik Cloud, an error message will now be shown to the Tenant Administrator:
To resolve this error a Tenant Admin can enter valid SMTP credentials.
At the moment, it is not possible to delete/clear the previous credential entry in the authentication. An option to clear the credentials is being prepared to support a return to a default (non-configured/empty) state and is expected to be available in the coming weeks.
We will update this article when the ability to clear becomes available. Example SMTP Error
With the release of the SMTP service connectivity for Microsoft O365 from the Management Console, more stringent error checking was added to the basic authentication configuration.
If interested, Admins can still successfully connect to Microsoft 0365 SMTP with this error showing. More details on the new available 0Auth2 authentication can be found here: Qlik Cloud: Introducing OAuth2 authentication for ... - Qlik Community - 2444243
You may get the errors, "A call to SSPI failed, see inner exception" and "The certificate chain was issued by an authority that is not trusted". While they should have no impact on your end-users, you'd still like to clean them up from the logs.
Qlik Sense otherwise functions without issues.
Example error:
System.Proxy.Qlik.Sense.Communication.Communication.Tcp.StreamFactory 16 c2972806-6ae3-4559-8ebf-c7c2201335f3 xx\xxx Failed to authenticate stream as Server The client and server cannot communicate, because they do not possess a common algorithm↵↓A call to SSPI failed, see inner exception. NO-STACKTRACE↵↓ at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
These, unfortunately, are not Qlik Sense errors, but rather errors from Windows that Qlik Sense reports. You should also be able to see them in your Windows Application logs. For more information, please search out Windows Support.
See Security Support Provider Interface Architecture for additional details.
Possible root causes:
The Oracle Redo compatibility version 0b200100 is not supported
Upgrade to a supported Oracle version.
While planning the upgrade, a workaround can be applied.
This workaround must not be used as a permanent solution.
An unsupported version of Oracle, such as 11.2.0.1. Verify the supported version: Supported source endpoints | Oracle.
! Note: Do NOT modify the NPrinting Database for any reason using PG Admin postres query or any other execution tools as this will damage your NPrinting Deployment and prevent successful NPrinting Database backup and restore operations.
! Note: Do NOT restore an older version of an NPrinting Database to a New NPrinting server or restore a newer version of the NPrinting database to an older version of NPrinting Server.
Examples:
These rules apply to general releases and service releases: The point version of the NPrinting Database being restored must match the point version of NPrinting Server being restored to (see Backup and restore Qlik NPrinting).
! Note: From NPrinting February 2020 and later versions, it is NOT necessary to enter a superuser database password
! Note: If you are making a backup for the Qlik Support team, please add the following NPrinting user information so that we can log onto the NPrinting Web Console following the local restore of the database (also ensure that NPrinting Authentication is enabled. Go to Admin > Settings > Authentication
This procedure is meant to backup and restore (partial backup and restore of these individual items is not possible*):
NP Web Console Items:
NP Backup zip File Contents (do NOT open and modify the contents of this file):
NOTE:
c:\nprintingbackups
Before Proceeding: Please log on as the NPrinting service account used to run the NPrinting Web Engine and Scheduler services before proceeding
Open the Windows Service Manager (services.msc), and stop the following services (by right-clicking them, and then clicking Stop). This will ensure any manual or scheduled NPrinting Publish Tasks are not executed during the backup or restore process:
C:\NPrintingBackups
Do NOT modify any syntax or add any additional unnecessary spaces
Open the command prompt making sure to run cmd.exe as Administrator and change directory as follows:
cd C:\Program Files\NPrintingServer\Tools\Manager
Qlik.Nprinting.Manager.exe backup -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin" --pg-password YourSuperuserDBpasswordHere
or with Current Supported versions of NPrinting (no password required)
Qlik.Nprinting.Manager.exe backup -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin"
Qlik.Nprinting.Manager.exe restore -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin" --pg-password YourSuperuserDBpasswordHere
Qlik.Nprinting.Manager.exe restore -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin"
File C:\Users\domainuser\AppData\Local\Temp\2\nprintingrestore_20201203082300\files\xxxxxxxxxxxxxxxxxxxxxxxxxxxx does not exist in the source backup package.
! Note: If re-installing on existing or restoring to a different NPrinting server environment, ensure that the destination NPrinting server license is enabled/activated before restoring the NP database.
NPrinting Engine:
NP Connections:
Qlik Sense Certificates (if using NPrinting Qlik Sense connections)
C:\Program Files\NPrintingServer\Settings\SenseCertificates
Other helpful information about the NP Backup and Restore tool and process:
C:\ProgramData\NPrinting
Note:The pre and post upgrade backup files are appended with the NP version number and backup dateC:\ProgramData\nprinting\logs\nprinting_manager.log
*NOTE:
When working with Oracle source endpoint, permissions are required for Change Data Capture (CDC) tasks by default. However, in some scenarios, we only need Full Load (FL) tasks, which require fewer permissions.
The minimum permissions required for a Qlik Replicate Full Load ONLY task are as follows. In this example, the Oracle account name is "FLONLYUSER":
GRANT SELECT ANY TABLE TO FLONLYUSER;
GRANT CREATE SESSION TO FLONLYUSER;
GRANT SELECT ON V_$PARAMETER TO FLONLYUSER;
In some environments, DBAs may be unwilling to grant V_$PARAMETER permission. For such cases, refer to the Alternative Resolution.
Please ensure to disable the advanced option "Automatically add supplemental logging" in Oracle source endpoint, as it is unnecessary for a Full Load ONLY task.
#00154133
A Qlik Replicate full load ONLY task reports the following error/warning messages when loading data from an Oracle source database:
[METADATA_MANAGE ]E: ORA-00942: table or view does not exist [1020416]
[METADATA_MANAGE ]W: Cannot execute statement 'select value from v$parameter where name='enable_goldengate_replication''
This issue typically arises because the Oracle account used by Qlik Replicate lacks the necessary permissions to access the v$parameter view.
Required Permission:
To resolve this, the following permission needs to be granted to the Oracle account. In below sample the account name is "FLONLYUSER":
GRANT SELECT ON V_$PARAMETER TO FLONLYUSER;
In some environments, DBAs may be unwilling to grant this permission. While the full load task completes successfully, the error/warning messages persist without the permission.
To resolve these messages, you can create a table under the Oracle account as follows. This example uses the "FLONLYUSER" account to connect to the Oracle source database:
CREATE TABLE FLONLYUSER.V$PARAMETER AS SELECT * FROM V$PARAMETER;
Here:
Explanation: When a table and a system view share the same name within the same account, the table takes precedence. Thus, Qlik Replicate will query the FLONLYUSER.v$parameter table instead of the v$parameter system view, eliminating the error/warning messages.
#00154133
In Qlik Replicate when manipulating datetime data on the transformation page, the microsecond precision is truncated to the first three digits after the transformation is performed.
Qlik Replicate utilizes SQLite syntax, which is a limitation since SQLite only supports fractional seconds up to SS.SSS. If we perform the same syntax in an SQLite command prompt, we would see the same result.
sqlite> select strftime('%Y-%m-%d %H:%M:%f','2024-06-27 12:00:00.123456','+8 hours');
2024-06-27 20:00:00.123
After manipulating the datetime, you can treat it as a string and concatenate the microseconds using a combination of SQLite functions, like this:
substr(strftime('%Y-%m-%d %H:%M:%f', $TS, '+8 hours'), 1, 19) || substr(strftime('%Y-%m-%d %H:%M:%f', $TS), 20)
This is working as designed. Qlik Sense Enterprise on Windows uses self signed certificates for service communication (Certificates | Qlik Sense for administrators Help) and as the out-of-the-box proxy certificate.
This is not considered a security vulnerability.
If you have run a security scan and receive reports of vulnerabilities which are of concern to you, see Qlik Security Vulnerability Policy on how to report them to Qlik.
To improve the security of your system, consider the following actions:
Installing, upgrading, and managing the Qlik Cloud Monitoring Apps has just gotten a whole lot easier! With two new Qlik Application Automation templates coupled with Qlik Data Alerts, you can now:
The above allows you to deploy the monitoring apps to your tenant with a hands-off approach. Dive into the individual components below.
Some monitoring apps are designed for specific Qlik Cloud subscription types. Refer to the compatibility matrix within the Qlik Cloud Monitoring Apps repository.
Content:
This automation template is a fully guided installer/updater for the Qlik Cloud Monitoring Applications, including but not limited to the App Analyzer, Entitlement Analyzer, Reload Analyzer, and Access Evaluator applications. Leverage this automation template to quickly and easily install and update these or a subset of these applications with all their dependencies. The applications themselves are community-supported; and, they are provided through Qlik's Open-Source Software GitHub and thus are subject to Qlik's open-source guidelines and policies.
For more information, refer to the GitHub repository.
Note that if the monitoring applications have been installed manually (i.e., not through this automation) then they will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring applications and check their versions, etc. This is due to the fact that the applications are tagged with "QCMA - {appName}" and "QCMA - {version}" during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.
This template is intended to be used alongside the Qlik Cloud Monitoring Apps for user-based subscriptions template. This automation provides the ability to keep the API key and associated data connection used for the Qlik Cloud Monitoring Apps up to date on a scheduled basis. Simply input the space Id where the monitoring_apps_REST data connection should reside, and the automation will recreate both the API key and data connection regularly. Ensure that the cadence of the automation’s schedule is less than the expiry of the API key.
Enter in the Id of the space where the monitoring_apps_REST data connection should reside.
Ensure that this automation is run off-hours from your scheduled monitoring application reloads so it does not disrupt the reload process.
Each Qlik Cloud Monitoring App has the following two variables:
With these variables, we can create a new Qlik Data Alert on a per-app basis. For each monitoring app that you want to be notified on if it falls out of date:
Here is an example of an alert received for the App Analyzer, showing that at this point in time, the latest version of the application is 5.1.3 and that the app is out of date:
Q: Can I re-run the installer to check if any of the monitoring applications are able to be upgraded to a later version?
A: Yes. Run the installer, select which applications should be checked and select the space that they reside in. If any of the selected applications are not installed or are upgradeable, a prompt will appear to continue to install/upgrade for the relevant applications.
Q: What if multiple people install monitoring applications in different spaces?
A: The template scopes the applications install process to a “target” space, i.e., a shared space (if not published) or a managed space. It will scope the API key name to `QCMA – {spaceId}` of that target space. This allows the template to install/update the monitoring applications across spaces and across users. If one user installs an application to “Space A” and then another user installs a different monitoring application to “Space A”, the template will see that a data connection and associated API key (in this case from another user) exists for that space already and it will install the application leveraging those pre-existing assets.
Q: What if a new monitoring application is released? Will the template provide the ability to install that application as well?
A: Yes. The template receives the list of applications dynamically from GitHub. If a new monitoring application is released, it will become available immediately through the template.
Q: I would like to be notified whenever a new version of a monitoring applications is released. Can this template do that?
A: As per the article above, the automation templates are not responsible for notifications of whether the applications are out of date. This is achieved using Qlik Alerting on a per-application basis as described in Part 3.
Q:I have updated my application, but I noticed that it did not preserve the history. Why is that?
A: The history is preserved in the prior versions of the application’s QVDs so the data is never deleted and can be loaded into the older version. Each upgrade will generate a new set of QVDs as the data models for the applications sometimes change due to bug fixes, updates, new features, etc. If you want to preserve the history when updating, the application can be upgraded with the “Publish side-by-side” method so that the older version of the application will remain as an archival application. However note that the Qlik Alert (from Part 3) will need to be recreated and any community content that was created on the older application will not be transferred to the new application.
When using Qlik REST connector to load data from API sources that return JSON or XML response, sometimes a huge data model with many tables is returned although the response contains only a single table.
For example, the following JSON message is parsed into 5 single-row tables instead of one table with 5 rows:
Environment:
The JSON response has a "nested" structure, i.e each data record is stored as a separated JSON object, which is not member of an array.
Qlik REST connector applies a standard strategy for parsing JSON response:
As a result, nested JSON response is parsed as multiple tables instead of a single flat table. You can find the same strategy in other JSON parsing tool, such as http://json2table.com/.
The same logic applies to nested XML responses.
Qlik REST connector does not yet support loading JSON/ XML responses with nested structure. There is an ongoing improvement request to support this structure in future releases of the connector.
Meanwhile, please consider the following work-around solution:
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.
When extracting data from AWS DynamoDB using ODBC connector, the following IAM policy can be configured for an IAM user and thus, pull data from only one table into Qlik i.e. viewing the expected table in "Select data" UI instead of providing access to all AWS DynamoDB database tables.
{
"Statement": [
{
"Action": [
"dynamodb:Scan",
"dynamodb:ListTables",
"dynamodb:DescribeTable"
],
"Effect": "Allow",
"Resource": "arn:aws:dynamodb:eu-west-2:*:table/my-table-name",
"Sid": "EcrDynamoDBReadAccess"
}
],
"Version": "2012-10-17"
}
However, with above IAM policy, select data is empty and the following error is displayed
error "(Connector error: ERROR [42S02] [Simba][SQLEngine] (31740) Table or view not found: ..my-table-name)"
When given access through DynamoDB UI console or AWS API, the above IAM policy is valid from AWS DynamoDB perspective. But, ODBC and JDBC drivers need access to fetch metadata, hence ListTables access is required. As ListTables is just read access, it should not be an issue.
Use the following reviewed IAM Policy
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "ListTablesAccess",
"Effect": "Allow",
"Action": [
"dynamodb:ListTables"
],
"Resource": "*"
},
{
"Sid": "SpecificTable",
"Effect": "Allow",
"Action": [
"dynamodb:DescribeTable",
"dynamodb:Get*",
"dynamodb:Query",
"dynamodb:Scan"
],
"Resource": "arn:aws:dynamodb:*:*:table/<MyTable>"
}
]
}
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-27013 for reference.
Product Defect ID: QB-27013
Analyzer Capacity Licenses can be assigned automatically based on Analyzer Capacity License Rules. These rules can be set up to provide Analyzer Capacity to users, groups, or anonymous users.
This article covers what function the license type has, how to assign it, and how to track usage.
Index:
The Qlik Sense Analyzer Capacity license type is automatically assigned to users not assigned a Professional or Analyzer license and consumes time during an active session with the minimum session length set to 6 minutes.
Overview:
Details:
No setup is required. If no Professional or Analyzer License was assigned, Analyzer Capacity is automatically allocated.
See Enabling dynamic license assignment for details.
The Entitlement Analyzer for Qlik Cloud provides detailed usage data for Analyzer Capacity, but a tenant admin can gain an overview through the Management Console at any time:
The Entitlement Analyzer is only available for Qlik Cloud.
The bundled License Monitoring app provides usage data for Analyzer Capacity, but an administrator can gain an overview through the Qlik Sense Management Console at any time:
Analyzer capacity license and monitoring (Client Managed)
Qlik Licensing Service Reference Guide
Assigning user allocation (Qlik Cloud)
Analyzer capacity license (Qlik Cloud)
Top 5 things to know about modern Qlik Licensing
This article provides an overview of how to manage users using Qlik Application Automation. This approach can be useful when migrating from QlikView, or Qlik Sense Client Managed, to Qlik Sense Cloud when security concerns prevent the usage of Qlik-CLI and PowerShell scripting.
You will find an automation attached to this article that works with the Microsoft Excel connector. More information on importing automation can be found here.
Content
In this example, we use a Microsoft Excel file as a source file to manage users. A sheet name, for example, Users, must be added and this must also be provided as input when running the automation. The sheet must also contain these headers: userId, Name, Subject, Email, Roles, Licence, and Flag.
Example of sheet configuration:
If users are to be created the Flag column must be set to create. If users are to be deleted, there's no need to include roles, but Flag must be set to delete.
Add the List Rows With Headers block from the Microsoft Excel connector to read the values that have been configured in the Excel sheet.
When running the automation you must provide input to the automation, this includes the name of the worksheet to read data from. You also need to specify the first and last cell to read data from, as well as if users are to be created or deleted. Example :
Input | Value |
Worksheet Name | Users |
Excel Start Cell | A1 |
Excel End Cell | G5 |
Mode | Create |
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.
How to manage space membership (users)
This is a basic example in order to get started with Advanced Analytics Integration in Qlik Sense using PYTHON.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, reach out to our Professional Services or engage in our active Integrations forum.
The architecture at a high-level looks like this:
With this new capability, it is possible to add syntax to a chart expression that tells Qlik Sense that a particular expression should not be evaluated on the Qlik Sense server, but instead, all the information and data needed to calculate that expression should be sent via the server side extension on to the back end Python system for calculation.
After the advanced analytic calculations are completed, the data is sent back to the Qlik Sense Server and to the client for visualization.
For an example with video that uses R-Server instead, see R Integration with Qlik Sense
In order to display a "Hello World" message in the Qlik Sense App, Perform the steps below:
Note: To obtain the latest HelloWorld example and other Python examples, see Python Examples in Qlik's Github repository. Make sure to check out the GetStarted.md documentation as well.
SSEPython.ScriptAggrStr('", ".join(args[0])' , HelloWorldData)
Eight script functions are automatically added to the functionality of the plugin. What is needed to be covered on the plugin side to fulfill
the functionality is to implement the Script aggregate rpc function.
The syntax of these functions is <EngineSSEName>.<FunctionName>(Script [,Parameter...])
where the Script is a Python script to be evaluated & Parameter is the data sent from Qlik's end.
Here, the ScriptAggrStr function is used which accepts argument of type String & returns a String after an aggregation. The 'join' function in Python method returns a string, which is the concatenation of the strings in the sequence seq. The separator between elements is the string providing this method. From Qlik side, we pass a field called HelloWorldData which contains the 2 strings as we have loaded.
To use SSE function(s) to load data via application load script, the Extension clause needs to be used. See additional information as well as an example under Load > Argument > Extension and Examples > Loading from Analytic connections via the following link: Script Regular Statements: Load.
This video will demonstrate how to install and configure Qlik-CLI for SaaS editions of Qlik Sense.
Content:
get-command qlik
choco install qlik-cli
if ( -not (Test-Path $PROFILE) ) {
echo "" > $PROFILE
}
qlik completion ps > "./qlik_completion.ps1" # Create a file containing the powershell completion.
. ./qlik_completion.ps1 # Source the completion.
Advanced and additional instructions as seen in the video can be found at Qlik-CLI on Qlik.Dev. Begin with Get Started.
What is the default user session timeout for Qlik Sense Business and Qlik Sense Enterprise SaaS? Can the session timeout for Qlik Cloud be changed?
The default (fixed) value is set to 30 minutes. This is controlled by SESSION_TTL.
It is not currently possible to adjust the session timeouts in the Qlik Cloud.
To eliminate the chance that AntiVirus, AntiMalware, and other security-related software cause corruption or lock up files in the Qlik environment, or cause issues during an installation/upgrade/patch, some folders should be excluded from live scanning.
Impact of AntiVirus/Endpoint Detection and Response (EDR)/Advanced Threat Protection (ATP) scans locking Qlik related files (such as .qvw files, binary Qlik Sense app files as well as NPrinting task files, etc...) can result in loading and refresh failures as well as performance issues.
Please note that usual anti-virus exclusions might not apply to the EDR and ATP setup, talk to the solution vendor to get the exclusions in place. As an example if you use Microsofts Advanced Threat Protection (Microsoft Defender for Endpoint), then the exclusion list is handled by Microsoft and you need to open a ticket with Microsoft to get an exclusion in place.
If Crowdstrike Antivirus monitoring is installed on any Qlik Server
Antivirus exceptions for Qlik Sense- McAfee, Symantec & Other Anti-Virus exclusions absolutely required
Qlik Sense Folder And Files To Exclude From AntiVirus Scanning
You can obtain a list of exclusions to use with your EDR or ATP system by running the following script:
$Scanfolders = @("C:\Program Files\Common Files\Qlik","C:\Program Files\Qlik","C:\ProgramData\Qlik")
Foreach ($i in $Scanfolders)
{
Get-ChildItem -Path $i -Recurse -Include "*.exe" | % {Get-FileHash $_.FullName -Algorithm MD5} | Out-File C:\temp\exclusion_findings.txt -Append -Width 1000
}
This script was uses Qlik Sense Enterprise on Windows as an example. Replace the defined folders, such as C:\Program Files\Qlik, should they not apply for the product you are using.
In addition, if you need to use a different hash than MD5, replace it by any of the available values:
For generic information not necessarily related to Advanced Threat Prevention, see:
QlikView Folder And Files To Exclude From Anti-Virus Scanning
Qlik Replicate and Qlik Enterprise Manager directory to exclude from Anti-Virus scanning
NPrinting Server and NP Designer Anti Virus Folder Exclusions
Qlik Alerting Anti Virus Folder Exclusion