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.
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
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.
! 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:
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
Qlik NPrinting and Qlik Sense are installed on Azure cloud machines. The configuration respects all the requirements. in particular, the NPrinting Engine user is present on both the NPrinting and Sense servers with the same domain and SSID.
The Metadata reload test fails with a "Not a domain user" message. On the other side, the Metadata reload is successful when launched (ignoring the Test error) even if the NPrinting Engine logs show these error and warning messages:
Engine.Navigator.QlikSense.SDK.QlikSenseDiagnose 20231128T103337.642+01:00 ERROR NP-SERVER _NAME 0 0 0 0 0 0 0 0 PerformDiagnosis found a problem. ERROR: System.Exception: Not a domain User : Domain\NPUser↓↓ at Engine.Navigator.QlikSense.SDK.QlikSenseDiagnose.<>c__DisplayClass8_0.<PerformDiagnosis>b__3() in C:\Jws\release-may2023-SwCB9Sd4b\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\QlikSenseDiagnose.cs:line 90↓↓ at Engine.Navigator.QlikSense.SDK.QlikSenseDiagnose.GetStep(DiagnoseStep step, Action stepCode) in C:\Jws\release-may2023-SwCB9Sd4b\server\NPrinting\src\Engine.Navigator.QlikSense.SDK\QlikSenseDiagnose.cs:line 40
Engine.Navigator.QlikSense.SDK 23.20.5.0 Engine.Navigator.QlikSense.SDK.QRSApi
20231128T103350.840+01:00 WARN NP-SERVER _NAME 0 0 0 0 0 0 0 0 Domain user check failed for Domain\NPUser. ERROR: System.Runtime.InteropServices.COMException (0x8007200A): The specified directory service attribute or value does not exist.↓↓↓↓ at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)↓↓ at System.DirectoryServices.DirectoryEntry.Bind()↓↓ at System.DirectoryServices.DirectoryEntry.get_SchemaEntry()↓↓
Ignore the error message and proceed with the metadata reload.
According to the current analysis, the error message is shown because Azure does not organize users and permissions as on-premise Windows servers do. NPrinting does not receive the expected answers from Azure AD Connect and interprets this as missing access levels in Azure during the connection tests.
On the other side, when the environment is correctly configured, the NPrinting Engine user has access to the Qlik Sense applications, so the metadata reload and the tasks executions are completed successfully at the end.
This issue can occur in non Azure environments as well. Proceed with the same solution.
This article contains steps on how to do backup and restore the Qlik Sense Enterprise on Windows (QSEoW) site.
For full instructions on how to backup and restore a Qlik Sense site, see the online help under Backup and restore Qlik Sense Enterprise on Windows.
For sole database backup information article can be found here: How to backup PostgreSQL database in Qlik Sense
Backup and Restore Targets:
Environment:
Note: These steps are provided as-is based on latest version available of Qlik Sense product at the time of writing and/or last update to the article. Please make sure to cross-reference these steps with the official documentation for your product version under Backup and restore Qlik Sense Enterprise on Windows.
Backing up Qlik Sense Repository Database:
! Downtime is required.
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\pg_dump.exe -h localhost -p 4432 -U postgres -b -F t -f "c:\backup\QSR_backup.tar" QSR
Restoring Database (PostgreSQL):
Option 1: Restoring on the same machine (PostgreSQL)
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\dropdb.exe -h localhost -p 4432 -U postgres QSR
.\createdb.exe -h localhost -p 4432 -U postgres -T template0 QSR
.\pg_restore.exe -h localhost -p 4432 -U postgres -d QSR "c:\backup\QSR_backup.tar"
For further reference, consult the Qlik Sense Help Site for your respective version.
Option 2: Restoring on a different machine (PostgreSQL)
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\dropdb.exe -h localhost -p 4432 -U postgres QSR
.\createdb.exe -h localhost -p 4432 -U postgres -T template0 QSR
.\pg_restore.exe -h localhost -p 4432 -U postgres -d QSR "c:\Backup\QSR_backup.tar"
cd "C:\Program Files\Qlik\Sense\Repository"
.\repository.exe -standalone -restorehostname
Backing up The Certificate
Please refer to the Backing up Certificates Help site documentation for details and verify that the information matches your current version.
Restoring The Certificate
Please refer to the Restoring certificates Help site documentation for details and verify that the information matches your current version.
Backing up the Apps used by Qlik Sense
Restoring Apps used by Qlik Sense:
Backing up the Repository Content used by Apps:
Normally, It is similar to the section for apps, the path where these files live is in the StaticContent folder on the Share path.
Restoring the Repository Content used by Apps:
Restoring a Qlik Sense site to a machine with a different hostname
Advanced options is not visible when editing a sheet. This can happen on a specific app even if the option was present before.
You can activate the "Show Sheet Header" option in the app settings to make the "Advanced option" button visible again.
For some reasons, the "Show Sheet Header" could be deactivated in an app. "Advanced Options" is invisible when this happens, because it is located in the sheet header that is removed. The app looks like this in editing mode:
This Techspert Talks session covers:
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
Click here to see video transcript
Also see a related video posted on Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly
This option is available in Qlik Sense June 2018 Patch 1 and later releases.
Description of related problem:
Getting errors "Connection to the Qlik Sense engine failed for unspecified reasons. Refresh your browser or contact our system administrator" for external users on other browsers except for IE when they open the Qlik sense app and leave it inactive until it exceeds the Firewall session idle timeout. This is followed by a connection reset for the TCP WebSocket session.
For Qlik Sense Enterprise for Business (Cloud), see Loading of an app is hanging when using QlikSense Cloud.
TCP WebSocket connection is terminated by the firewall because the firewall is not receiving any TCP traffic such as keep-alive packets from client browser (e.g. Firefox, older Chrome versions). Specific web browsers have their own tcp keep-alive behavior.
This issue may be found with less frequency with IE because it sends the TCP Websocket keep-alive more frequent than any other main stream browser. Here are the default intervals for the three main browsers latest releases as of September 2020:
Default TCP-Keep-Alive intervals:
This functionality is by default switched off not to affect any existing customers. Customers who do not experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it will send unnecessary traffic on the network. See How are WebSockets used in QlikSense ? for more information.
<add key="WebSocketPingInterval" value="0"/> <!-- Interval in seconds for the web socket ping to the client (a value of "0" is disabling the ping)–>
Where value is a suitable positive number depending on the inactive web socket timeout setting in the network. The effective interval that the Qlik Sense Proxy server will send keep-alive messages towards the client my oscillate between 2 x value and 1 x value, since it also takes into account backend inter-process socket activity. Eg: setting the value of WebSocketPingInterval to 30 may lead to keep-alive messages sent to the client every 30 or 60 seconds.Multi-Factor Authentication (MFA) adds additional security for logging into Qlik Cloud Services. Qlik recommends enabling MFA on your Qlik account.
If the device used for MFA is bein replaced, or if MFA needs to be disabled temporarily, this can be achieved in your My Qlik Portal.
You have been running Qlik Sense normally for quite some time. Over time you have accumulated an abundance of reload tasks configured in your Qlik Sense QMC.
Recently however, you have noticed that Qlik Sense QMC reload tasks are in the following state:
To resolve the issue, it is recommended to add an additional scheduler node (or nodes) in order to manage the ever increasing number of reload tasks in the affected Qlik Sense environment.
As time goes on, add additional scheduler nodes in proportion to the increasing number of reload tasks added/deployed in your environment.
The existing Qlik Sense scheduler nodes simply cannot manage the additional burden placed upon it by ever increasing reload tasks.
Concurrent Reload Settings in Qlik Sense Enterprise
QB-20013
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.
Upgrading Qlik Sense Enterprise on Windows with a standalone PostgreSQL database to August 2023 or later fails. The installer does not return an error on-screen.
A Qlik Sense Enterprise on Windows environment can have a bundled PostgreSQL database or a standalone database.
If your Qlik Sense environment has relied on a standalone PostgreSQL database since its initial setup, and still has its PostgreSQL 9.6 database and binaries, additional steps are required to prepare for an upgrade to any versions beyond Sense August 2023.
These binaries will be in the following folder:
C:\Program Files\Qlik\Sense\Repository\PostgreSQL\version number
Where version number is 9.3 or 9.6.
The old binaries need to be uninstalled and new binaries installed (on all nodes).
Qlik Sense August 2023 and higher as the target version
Qlik Sense May 2023 and lower as the source version
Before proceeding with an upgrade:
The msi will be revealed.
The msi will be revealed.
The upgrade will be blocked when a 9.6 or 9.3 database binary folder is found. These folders can be in either:
C:\Programdata\Qlik\Sense\Repository\PostgresSQL\version number
C:\Program Files\Qlik\Sense\Repository\PostgresSQL\version number
When attempting to upgrade Qlik Sense to a newer version, you may encounter a situation where the upgrade process treats it as a fresh installation rather than detecting the existing version.
Additionally, you might encounter the following warnings before encountering the upgrade issue:
These warnings are triggered because there is already an active and working version of Qlik Sense installed on the system.
To address this issue, follow the steps below:
Locate the installation packages for Qlik Sense. These packages are typically stored in the following directory: C:\ProgramData\Package Cache
.
If any packages are missing from the specified directory, it can lead to the behavior where the previous version is not detected during the upgrade process.
To resolve this, you need to restore the missing folders in the C:\ProgramData\Package Cache
directory. If you have a backup of these package folders, simply place them back into the correct location.
In case you don't have a backup of the package folders, you can retrieve them by installing the same version of Qlik Sense on a test machine. This will ensure you have the correct folders needed for the server.
By following these steps, you should be able to upgrade Qlik Sense successfully without encountering the issue of the previous version not being detected.