Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team
You can open and build an app on Qlik Cloud using a direct link.
To obtain the link:
Qlik Cloud
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.
Qlik offers a range of opportunities to assist you in troubleshooting, answering frequently asked questions, and contacting our 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 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)
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)
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.
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 Contact Support 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:
How to create a case using chat
Log in to manage and track your active cases in Manage Cases. (click)
Your advantages:
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.
Qlik Cloud is a modern analytics and data platform built on the same software engine as QlikView and Qlik Sense Client-Managed and adds significant value to empower everyone in an organization to make better decisions daily. Qlik Cloud allows you to use one common platform for all users – executives, decision-makers, and analysts.
Migrating to Qlik Cloud can help your organization:
This site provides you the tools to monitor, manage, and execute a migration from Client-Managed Qlik Sense to Qlik Cloud.
No two client-managed Qlik Sense Enterprise deployments are the same. And no two migrations will be the same. The processes, procedures, and instructions in this section shouldn’t be considered a cookbook. Rather, they’re meant to guide you.
The Qlik Cloud Migration Center provides a general approach to migration along with sequencing, strategy, and best practice recommendations. It also includes tools such as a Qlik Sense app, scripts, and worksheets to aid in planning elements of the migration.
If your organization has a complex deployment with custom tooling, or sophisticated or complicated data integration pipelines, consider contacting your Qlik Customer Support representative.
This site provides comparisons of QlikView and Qlik Cloud, as well as best practices on how to move content, including information about migration assessments and QlikView document conversions.
When either preview and NPrinting Report containing a straight table or pivot table, the following error is generated:
Going to retrieve archived REDO log with sequence 2056016, thread 1 but fails REDO log with sequence not found error. The Archived Redo Log has Primary Oracle DB as DEST_ID 1 and the Standby DEST_ID 32 pointing to the correct location.
Cannot use DEST_ID greater than 31 for Primary or Standby Oracle Redo Log locations
Replicate only supported the DEST_ID 0 through 31
https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/V-ARCHIVE_DEST.html
JIRA RECOB-6332 case 00058856
In some cases, an organization may decide to prevent entirely or limit access to the NPrinting Newsstand
Disable the Newsstand (note that this will disable access for all NPrinting users and administrators)
"C:\Program Files\NPrintingServer"
Limit NPrinting User Access to the Newsstand (update NPrinting User Role: Remove Newsstand Role)
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.
After upgrading Qlik Sense Enterprise on Windows May 2022 patch 11 or August 2022 patch 6, some reload tasks which are showed as failed but in the script log are successfully completed.
In the Engine\System log called Service_Engine_TIMESTAMP.log
You will have such error:
13 31.11.2.0 20230130T151057.527+0100 WARN QLIKSERVER XXXXX-b9df-48dc-a868-XXXX 20230130T151057.522+0100 12.1386.6.0 Command=Doc::DoSave;Result=409;ResultText=Warning: Conflict 0 0 1111411 QLK QLIKUSER XXXXX-47c2-4ea4-94c2-XXXXXX XXXXX-95f5-46e2-8b92-XXXXX ApplicationQLIK Engine Not available Doc::DoSave Doc::DoSave 409 Object write failed. XXXXXX-b9df-48dc-a868-XXXXX
And to confirm the issue you will also have the below error in the Repository Engine\Trace log called System_Engine_TIMESTAMP.log:
2072 20230129T193052.695+0100 ERROR QLIKSERVER System.Repository.Repository.Core.Repository.Common.TransactionUtility 185 XXXXX-d7f0-4983-8905-XXXX QLK\QLIKSERVICEUSER Error when committing The custom property value already assigned at Repository.Core.Validation.Common.CustomPropertiesValidator.<ValidateCustomProperties>d__3`1.MoveNext()↵↓
Warning: Modifying the repository manually is not supported and need to be done with caution and prefer to take a backup of the database before changing anything in the repository database.
Connect to the QSR Postgres database with the super admin user, using PGadmin.
In order to identify the list of duplicate custom property, you can use below query:
SELECT "ID", "Value", "App_ID" FROM (SELECT "ID", "Value", "App_ID" , ROW_NUMBER() OVER (PARTITION BY "Value", "App_ID" ORDER BY "App_ID" DESC, "ID") rn FROM "CustomPropertyValues") t1 WHERE rn > 1 AND "App_ID" IS NOT null;
If you found any duplicates in the query above, you can use below cleanup script to delete them:
DELETE FROM "CustomPropertyValues"
WHERE "ID" IN
(SELECT "ID"
FROM (SELECT "ID", "Value", "App_ID"
, ROW_NUMBER() OVER (PARTITION BY "Value", "App_ID" ORDER BY "App_ID" DESC, "ID") rn FROM "CustomPropertyValues") t1
WHERE rn > 1 AND "App_ID" IS NOT null);
This is caused by a fix QB-9058, which has been introduced in May 2022 Patch 11 and August patch 6:
Qlik Sense: Possible to apply same custom property value more than once:
Fixed an issue where it was possible via QMC or API request to apply the same custom property value belonging to the same custom property definition more than one to the same resource.
So from those patch it is no longer possible to have any application with a Duplicate custom property.
When having duplicate, you'll be able to find the below error in the Qlik Sense logs:
The custom property value already assigned
If you had these custom properties multiple times injected before the patch was applied, you will see this issue occurring.
QB-17917, QB-9058
QlikView Server, Desktop, and QlikView Publisher have a built-in email functionality in order to send alerts and notifications according to triggers, but the functionality is limited. Please review our more extensive offering using Qlik NPrinting or utilising Alerting in our Cloud offering.
Standalone, QlikView allows you to:
Note that a Publisher license is required for most options.
This article is intended to clarify and elaborate on the differences and the different options that exist with sending emails from within the QlikView products. In general, only "Alerts" in QlikView Desktop are transferred with a document to QlikView Publisher, and in some scenarios user-made macros and third-party extensions. This means that this article only handles functionality that is part of the core product.
This article assumes that the reader has some knowledge about how to create tasks in Publisher, what NTLM, NTFS, SMTP, QVB and QDS stands for, how to create and open documents and e.g. the difference between a reload and/or a distribution.
Under Settings > User Preferences > Mail, one can find the email settings for the QlikView Desktop program.
Sender - Can be set to pretty much anything, as long as the user account running the services is trusted by the SMTP server to send emails.
Server - Defines the SMTP server, which is usually outside QlikView control.
Authentication method - defines by which user account the client can send emails. "None" means anonymous, and NTLM is mostly used in older domains. If you get an error message when using NTLM as the authentication method, try "None". If you are using a Active Directory Domain, you are already logged on and authentication on the domain, and the computer is a member of the domain. This means that the SMTP server recognizes the address being used as well as the computer, which allows you to send emails. This also means that you do not need to run QlikView Desktop with a domain user account in order to send emails, but this can instead depend on what your domain policies and SMTP server allow.
Built into this Mail setting tab inside "User Preferences" is also "Test", which allows you to send a test mail. Due to the architecture of the product there are a few differences that might impact how it behaves in your environment, e.g. Test mail works, but an email from a Macro, an alert or extension does not work. It can also depend on the user account running the document at the time being, and if it is logged in or not.
Most built-in functionality that uses the mail settings inside QlikView Desktop can be found under "Tools" > "Alerts". Here one can define an email to be sent during certain circumstances, due to certain triggers. This "Alerts" functionality will be activated if used on QlikView Publisher/Server, but the email will be sent by the QVB process instead of the QDS. Configuration of email settings can be done for the settings.ini of the QVB, located at C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch . Neither QlikView Desktop or the QVB support SSL for email alerts: you should therefore use other sorts of notifications and alerts if your SMTP server is SSL-only. As mentioned, there are more ways to configure email notifications, which can transfer some email notification settings to QlikView Publisher, available for further development outside the core functionality, e.g. by Macros (Tools > Edit Module) or Extensions (e.g. Settings > Document Properties > Extensions).
In the QMC, under System > Setup > Mail Server, one can find the email settings for the QlikView Distribution Service.
Location - Defines the SMTP server, which is usually outside QlikView control.
Miscellaneous - "From adress" can be set to pretty much anything, as long as the user account running the services is trusted by the SMTP server to send emails. E-mail format can be of choice, either plain or HTML.
Authentication method - defines by which user account the client can send emails. Anonymous does not try to authenticate towards the SMTP server, but works if the server is within the domain and/or the SMTP server allows anonymous emails to be sent. "Use Distribution Service account" let's you authenticate with the service account being used for the service, in case the SMTP server requires a domain account to be authenticated in order to send emails. Finally, "User name and password" lets you define custom credentials to an SMTP server. This is mostly used when using external mail servers like GMail and similar.
For test purposes and not to spam other people's inboxes when doing tests, one can set a single email address to be used to receive all emails. Remember to change this back if being used.
Built into this Mail Server settings tab is also "Send test e-mail". Due to the architecture of the product, there are a few differences that might impact how it behaves in your environment, e.g. Test mail works, but an alert email, a notification email or a distribution does not work. It can also depend on the user account running the document at the time being, and if it is logged in or not. The major difference, as of v11.20 SR10 is that the test email is sent by the QlikView Management Service and not the QlikView Distribution Service. If you have many servers used for QlikView in your environment, the test email might be sent from a different server than the alert email. The test functionality is also using a simple .NET SMTP client, and do not use the DSC to look up an email address, it just takes the email and sends it.
Some users can be set to be QlikView Publisher Document Administrators, which are allowed to distribute documents via e-mail.
You may find general QDS setting for alert and notification emails under QMC > System > Setup > Distribution Services > QDS@servername. There are two tabs here, "Alert E-mail", which let's you define which system administrators who should receive an alert email whenever a distribution has a warning or an error. On the next tab you can define "E-mail templates", for attachments, notifications and alerts. The different types of emails is explaining in the next section. The email templates can be customized with different variables, found in Help, in the upper right corner. As of 11.20 SR6 and later, a few new variables have been added, e.g. [TaskLogHyperlink], [DocumentLogHyperlink] and [DocumentLog].
For this to work, a Publisher needs to be authorized to send PDFs, which is determined by the license, e.g. :
PDF_GENERATION;YES;;
QlikView Information Access Server and QlikView Extranet Server does not have this in their licenses. The QlikView Distribution Service is responsible for the email being sent in this feature, where the QDS gets a recipient list and looks it up with the help of the DSC. The recipients emails are based on their ID (e.g. DOMAIN\username) or a plain name (e.g. account@mail.com). This process also validates the email address to ensure it is valid. The email will contain the text template defined within the QDS settings with the PDF/QVW attached. The email distribution setting is to be found on the same tab as "Distribute to server" or "Distribute to folder":
The QDS can distribute a PDF or a QVW to email addresses at the same time as it becomes available on the AccessPoint, meaning distribution is not limited to a single type of publication. The type of document of choice, a report via PDF or the full document via QVW, can be set under the "File Typ" subtab. Depending on the size of the QVW, limitations on the filesize may be subject to mail server settings. If you do not get the option to specify users or groups, no Mail Server has yet been configured.
Done by the QDS as well, with the same mechanism. When setting up a document in QlikView Publisher, one can configure a notification to be set, so that specific users are notified when there is a new version of a document on the AccessPoint. Under QMC > Documents > Source Documents > Document > Taskname (assumes the task has already been created) > Distribute > Notify, you can check whether or not the e-mail recipients should receive a notification or not.
This is not intended to use for distribution, only notification, meaning the "Distribute via E-mail" does not need to be used, instead the end-user get's a notification when a document is distributed to a QVS or a folder. If there is an email-distribution as well, it is redundant to first send the QVW/PDF via email and subsequently an email with a notification, meaning no notification will occur. A major difference to the "Distribution via E-mail" is that the notification functionality uses a queue system, where the thread runs every 30 seconds to send mail.
The email functionality that is used most by far in QlikView Publisher, is the "Alerts email". Using a template defined in the QDS setting, the QDS sends an email to defined recipients in case of a failing task. After a task fail, the QDS runs a cleanup method where it checks if "Alerts" have any recipients. The recipients list, which mostly consists of QlikView Server Administrators, can be set in the QDS Settings > Alert "E-mail":
For every task that is failing an email would be sent to the full list of administrators, along with an excerpt of the error message. The alert email functionality uses the same functionality as "Distribute via e-mail" and "Notification", meaning the QDS gets a recipient list and looks it up with the help of the DSC. The recipients emails are based on their ID (e.g. DOMAIN\username) or a plain name (e.g. account@mail.com).
In the QMC, under System > Setup > Mail Server, one can find the email settings for the QlikView server program.
Location - Defines the SMTP server, which is usually outside QlikView control.
Miscellaneous - "From adress" can be set to pretty much anything, as long as the user account running the services is trusted by the SMTP server to send emails. E-mail format can be of choice, either plain or HTML.
Authentication method - defines by which user account the client can send emails. Anonymous does not try to authenticate towards the SMTP server, but works if the server is within the domain and/or the SMTP server allows anonymous emails to be sent. "Use Distribution Service account" let's you authenticate with the service account being used for the service, in case the SMTP server requires a domain account to be authenticated in order to send emails. Finally, "User name and password" lets you define custom credentials to an SMTP server. This is mostly used when using external mail servers like GMail and similar.
For test purposes and not to spam other peoples inboxes when doing tests, one can set a single email address to be used to receive all email. Remember to change this back if being used.
Built into this Mail Server settings tab also "Send test e-mail". Due to the architecture of the product there are a few differences that might impact how it behaves in your environment, e.g. Test mail works, but an alert email, a notification email or a distribution does not work. It can also depend on the user account running the document at the time being, and if it is logged in or not. The major difference, as of v11.20 SR10 is that the test email is sent by the QlikView Management Service and not the QlikView Distribution Service. If you have many servers used for QlikView in your environment, the test email might be sent from a different server than the alert email. The test functionality is also using a simple .NET SMTP client, and do not use the DSC to look up an email address, it just takes the email and sends it.
Some users can be set to be QlikView Server Document Administrators, which are allowed to distribute documents via e-mail. You can ready more about Document Administrators in the QlikView Server Reference Manual, see here .
You may find general QDS setting for alert and notification emails under QMC > System > Setup > Distribution Services > QDS@servername. There are two tabs here, "Alert E-mail", which let's you define which system administrators who should receive an alert email whenever a distribution has a warning or an error. On the next tab you can define "E-mail templates", for attachments, notifications and alerts. The different types of emails is explaining in the next section. The email templates can be customized with different variables, found in Help, in the upper right corner. As of 11.20 SR6 and later, a few new variables have been added, e.g. [TaskLogHyperlink], [DocumentLogHyperlink] and [DocumentLog]. See the Release Notes for more information about the new variables, page 7.
Test-email does not confirm the email-addresses being used in the test, it simply sends an email. The alert email functionality matches the email address with the DSC to look it up. If you can't look up the email address under "Users", it might be possible that resolving email addresses is not working properly. You may also try to change the mail server authentication method from .e.g "Use Distribution Service account" (which might not have an email-address registered, is not allowed to send emails or does not have an account at the SMTP server), to the "Anonymous" checkbox. Some SMTP servers allows anonymous emails which could simplify sending emails. Using an account does thus force authentication towards the SMTP server which it doesn't accept.
If you use port 465 or 587 for port under Location, change the QVManagementService.exe.config that is located at C:\Program Files\QlikView\Management Service. You will need to change <add key="UseSSLForSMTP" value="false"/> from false to true. Change the QVDistributionService.exe.config that is located at C:\Program Files\QlikView\Distribution Service. You will need to change <add key="UseSSLForSMTP" value="false"/> from false to true.
Wait for at least 30 seconds and see if it was in the outbox. If sending a lot of emails it might take some time before the email reaches the end-user. The advice here would be to wait a further 10 minutes to confirm it is just not a delay on the mailserver end. Confirm that the issue solely is located to notification emails by trying to distribute a document via email, and report to support.qlik.com in case of further issues.
PostgreSQL hosted on Aurora behaves differently than an on-prem instance of PostgreSQL when data types of unlimited size are processed from the source by Qlik Replicate. Qlik Replicate will truncate all the data in those columns to NULL values.
This can lead to tasks not loading all tables or a high CPU load.
We recommend setting a size limit on the data type to prevent this behaviour or setting an internal parameter unboundedVarcharMaxSize and giving it a value based on your capacity. This parameter will assign the value to the data type for the size limit if the column is originally unlimited in size.
For information on how to set internal parameters, see Setting advanced connection properties.
Example:
With an internal parameter value at 200:
varying character will turn to varying character(200)
varying character(100) will stay as varying character(100)
0066686
HTTP Response Header exposes Microsoft-HTTPAPI/2.0 as the server source. An attacker could use this information to expose known vulnerabilities for the server source.
This header is included in the HTTP header by .NET framework, which means it can not be directly controlled by Qlik software.
The header is only added in Qlik software that runs in Windows environment, for example Qlik Sense Enterprise for Windows and QlikView Web Server.
There are two main approaches to removing this HTTP header;
Qlik Sense Enterprise on Windows, all version
QlikView, all versions
Qlik NPrinting, all versions
Replicate reported errors during resume task if source MySQL running on Windows (while MySQL running on Linux then no problem)
[SOURCE_CAPTURE ]I: Stream positioning at context '$.000034:3506:-1:3506:0'
[SOURCE_CAPTURE ]T: Read next binary log event failed; mariadb_rpl_fetch error 1236 (Could not find first log file name in binary log index file)
Replicate reported errors at MySQL source endpoints sometimes (does not matter what's the MySQL source platforms):
[SOURCE_CAPTURE ]W: The given Source Change Position points inside a transaction. Replicate will ignore this transaction and will capture events from the next BEGIN or DDL events.
Upgrade to Replicate 2022.11 PR2 (2022.11.0.394, released already) or higher, or Replicate 2022.5 PR5 (coming soon)
If you are running 2022.5 PR3 (or lower), then keep run it, or upgrade to PR5 (or higher) .
No workaround for 2022.11 (GA, or PR01) .
Jira: RECOB-6526 , Description: It would not be possible to resume a task if MySQL Server was on Windows
Jira: RECOB-6499 , Description: Resuming a task from a CTI event, would sometimes result in missing events or/and a redundant warning message
support case #00066196
support case #00063985 (#00049357)
Qlik Sense offers a range of Monitoring Applications that come pre-installed with the product. This article aims to provide information on where to find information about them or where to download them.
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 can I track the usage of my Tenant over time? How are my entitled users using the Tenant?
How can I better understand the usage of Analyzer Capacity vs. Analyzer & Professional Entitlements?
These are a couple of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Entitlement Analyzer for Qlik Sense Enterprise SaaS!
For more information and to download the app and usage instructions, see The Entitlement Analyzer for Qlik Sense Enterprise SaaS customers is available NOW!
These are a couple of the questions that you can answer with the App Analyzer.
For more information and to download the app and usage instructions, see The App Analyzer for Qlik SaaS customers is available NOW!
“How can I monitor reloads across the tenant?”
“How can I see what data connections and files are being used?”
“How can I view reload concurrency and peak reload RAM over time?”
These are a few of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Reload Analyzer for Qlik SaaS!
For more information and to download the app and usage instructions, see The Reload Analyzer for Qlik SaaS customers is available NOW!
“What users and groups have access to space <X>?”
“What users and groups have access to app <X>?”
“How does a user have access to app <X>; via direct assignment, group, or app share?”
“Are there redundancies in policies? E.g., does a user have the same access to a space via a direct assignment as well as a group?”
“Who has what roles across the tenant?”
These are a few of the questions we frequently hear. To enable you to find better answers for those, we are happy to share with you the new Access Evaluator for Qlik SaaS!
For more information and to download the app and usage instructions, see New Monitoring App for Qlik Cloud: Access Evaluator
The OEM Dashboard is an application for Qlik Cloud designed for OEM partners to centrally monitor data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas—which would otherwise be a tedious process. This application includes data from the App Analyzer, Entitlement Analyzer, and the Reload Analyzer, all of which are other monitoring applications for Qlik Cloud that provide deep levels of detail on their respective areas. Together, a complete picture can be formed which is crucial to the successful management of an OEM environment.
For more information and to download the app and usage instructions, see OEM Dashboard - Qlik Cloud Application.
The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.
Basic information can be found here:
The License Monitor
The Operations Monitor
Both apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
System Performance Analyzer
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
A user is getting the error:
QVX_SYNTAX_ERROR:........Size of dataset is higher than maximum size allowed by license. Please contact your Qlik sales representative for upgrade options.
when using QGA Base there are limits route calculations and location lookups per call. The max route calculations is 400 per call and 50000 location lookups per call. Check out the license metrics for QGA for more info> https://www.qlik.com/us/legal/license-terms
It's good practice to split up large tables when making the connector calls, here's a guide: Splitting up GeoAnalytics connector operations.
The Qlik sense engine Service stops but engine.exe still running.
Qlik Sense Enterprise on Windows
This is usually due to a high memory consumption, so when you stop the Qlik Sense Engine Service, the engine.exe will keep running it has released the memory. This can take a long time.
Possible error message in Windows events log:
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Engine.exe (77404) consumed 66804117504 bytes, dotnet.exe (29264) consumed 581591040 bytes, and dotnet.exe (49860) consumed 523714560 bytes.
To resolve this you can kill the engine.exe task but this will restart the service (as the services recovery properties are by default set to restart when the task fails), so you will have to stop the service again.
Windows successfully diagnosed a low virtual memory condition
Users who have been assigned Analyzer Licenses in Qlik SaaS (Qlik Sense Business or Qlik Sense Enterprise SaaS) cannot publish bookmarks.
See Assigning user allocations
Analyzer access: intended for users who only consume sheets and apps created by others. A user with analyzer access cannot create, edit, or publish sheets or apps, but can create stories, bookmarks and snapshots based on data in apps that are shared with them. The user can also generate on-demand apps, print objects, stories, and sheets, and export data from an object to Microsoft Excel.
Analyzer access (minutes): intended for providing time-based analyzer access.
This video demonstrates the basics on how to switch from Client Access Licenses (CALs) to the new Professional and Analyzer Access licensing.
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.
Note: This documentation is only to used to validate and test ADFS SAML while using Apache as a Reverse Web Server and HTTPS/SSL is enabled. This example is under the assumption there's an understanding of the environment and having the proper permissions to perform the actions shown. Accounts used are all Local Administrators and the servers are open, with nothing blocked and no other programs installed on them.Read the entire documentation to verify access and understanding of all actions stated within prior to starting the install and configuration. Any other versions or configurations of any software may need other steps/options/settings/etc ... that are not documented here. Use this at your own discretion as Qlik does NOT support Apache/OpenSSL/ADFS in their installation/configuration or use.
Download (Recommended to verify the zip file is not Blocked: Right click on the zip file -> Properties -> General -> Click Unblock -> Apply), Extract the Zip file and Read the "readme_first.html" then use the instructions to Install Apache Web Server as Service on a separate machine from Sense and ADFS - https://httpd.apache.org/docs/2.4/platform/windows.html. Verify Apache is running under HTTP/HTTPS.
Location Installed: C:\Apache24\
Note: Tested with http://www.apachehaus.com version Apache 2.4.33 x64 Distribution File: httpd-2.4.33-o110h-x64-vc14-r2.zip
Place a valid certificates .crt and .key files on the Apache Web Server.
Location used: C:\Apache24\conf\ssl
Note: Process used: How to convert a certificate for NPrinting to the .key and .crt files for HTTPS/SSL in the Web Console and/or the NewsStand
Navigate to the location and Edit the "httpd.conf" file (Location used: C:\Apache24\conf\). Then uncomment certain modules used in this example and save the file.
Search for and then uncomment the following modules:
Find and uncomment the following line so that the reverse proxy will use the configuration that will be written later:
Include conf/extra/httpd-vhosts.conf
Note: To uncomment the option/module remove the pound ( # ) symbol in front of the line and save the file.
Navigate to and Edit the file "httpd-vhosts.conf" under the directory (Location used: C:\Apache24\conf\extra) to add the virtual host that will used for Qlik Sense and save the file.
Example "httpd-vhosts.conf":
# Virtual Hosts
#
# Required modules: mod_log_config
# If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
#
# Please see the documentation at
# <URL:http://httpd.apache.org/docs/2.4/vhosts/>
# for further details before you try to setup virtual hosts.
#
# You may use the command line option '-S' to verify your virtual host
# configuration.
#
# Qlik Sense configuration needed:
#
# - Create a new virtual proxy with SAML called adfsapache
# - Add reverse proxy name and IP address to whitelist of virtual proxy
#Put IP address of reverse proxy as LOCAL_ADDR
#Put IP address of Qlik Sense server as REMOTE_ADDR
#Put your virtual proxy prefix as VIRTUAL_PROXY
Define LOCAL_ADDR 172.16.16.102
Define REMOTE_ADDR 172.16.16.100
Define VIRTUAL_PROXY adfsapache
<VirtualHost *:443>
ServerAdmin name@qlik.com
DocumentRoot "${SRVROOT}/htdocs"
ServerName ${LOCAL_ADDR}:443
ServerAlias qlikserver3.domain.local
SSLProxyEngine on
SSLEngine on
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
#Location of the SSL certificate used for this virtual host in their .crt and .key file format
SSLCertificateFile "${SRVROOT}/conf/ssl/QlikServer3Certificate.crt"
SSLCertificateKeyFile "${SRVROOT}/conf/ssl/QlikServer3Certificate.key"
ProxyRequests Off
ProxyPreserveHost On
KeepAlive On
RewriteEngine On
# If it is a websocket request forward as websocket traffic
RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
RewriteRule ^/(.*) wss://${REMOTE_ADDR}%{REQUEST_URI} [P]
<Proxy *>
Require all granted
</Proxy>
<Location /${VIRTUAL_PROXY}>
ProxyPass https://${REMOTE_ADDR}/${VIRTUAL_PROXY} connectiontimeout=5 timeout=300
ProxyPassReverse https://${REMOTE_ADDR}/${VIRTUAL_PROXY}
</Location>
</Virtualhost>
Note: Some parameters/options may need to be turned off or on depending on your certificates and other configuration items.
For Steps 5 & 6, refer to Article Quick Guide to installing ADFS for testing SAML starting from Step 5 until Step 11 and apply where needed
Configure a Virtual Proxy in Qlik Sense called "adfsapache"
Note: Verify the Host allow list has the correct IPs/DNS (FQDN/Servername/Alias) added to it,
Create the Relaying Party Trust for the "adfsapache" Virtual Proxy in ADFS
Restart the Apache Web Server service and attempt to log into a URL from a machine that's NOT the Apache Server. Example URL: https://qlikserver3.domain.local/adfsapache
Note: Reason for attempting it outside the Apache Web Server is that certain OS level settings may not allow access to the FQDN/Servername locally to the machine. Review this article if you're able to connect to it locally with IP/Localhost: Authentication failed repeatedly when using external DNS alias locally on the server
When requesting an export to Excel or Print using the QlikView Ajax client, QlikView Server creates a temporary Excel file on the server. The file will be removed after one hour (3600s).
The time until deletion can be customized.
By default, QlikView Server scans through the temp folder once an hour and removes all the files that are at least one hour old. This means that a file is stored somewhere between 1 and 2 hours, depending on when the file was created in relation to when the latest scanning occurred.
The value you can change is ServerTempSecTimeout (default 3600) which changes both time values.
E.g. if the setting is changed to 1800 (30 minutes), QlikView Server will scan the temp folder every 30 minutes. Any file that is at least 30 minutes old will be removed.
The temporary folder can be found in \QlikTech\QlikViewServer\Temp Folder
In our example, we configure the files to be deleted immediately after download.
This article explains how the Reporting connector in Qlik Application Automation can be used to generate multi-page PowerPoint reports. It also explains how to store the generated report on a cloud storage tool, like Microsoft SharePoint.
The following steps describe how to build the demo automation. You will find a version of this automation attached to this article: "Store-a-simple-multi-page-PowerPoint-report-to-Microsoft-SharePoint.json".