Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
This guide provides step-by-step instruction on how to create an UDC that fetches users from AD in the most common way: default Active Directory UDC. The steps use LDAP Admin for testing the LDAP filter string.
For steps that do not require LDAP Admin see Qlik Sense: Configuring and testing LDAP filters for User Directory Connector
For connecting AD using Generic LDAP connector, follow article How to connect to Active Directory using the Generic LDAP Connector
1. Confirm current server is Central Node and Repository Service is running correctly.
2. In order to confirm AD connectivity, download a 3rd party tool called "LDAP Admin" and run it on current server.
3. In LDAP Admin, create a connection.
4. For the detailed information, consult your Domain Administrator.
5. Make sure the connection passes test.
6. Once connected, go to Search > Custom > set "Path" to the top level > Input appropriate LDAP filter. Make sure there are some users fetched successfully.
For any issues happening before this point, please contact Domain Administrator. For any issues happening after this point, please contact Qlik Support.
[VERY IMPORTANT] Before moving forward, confirm if there is any RootAdmin assigned to a domain user in Qlik Sense.
If there is, make sure that user appears in the search result of above filter otherwise it will be marked as inactive and could potentially lock users out from QMC. Also follow How to avoid the RootAdmin(s) from becoming inactive. But this step should not be relied on so please still make sure the filter fetches current RootAdmin.
7. Go to QMC > User directory connector > Create new > Active Directory:
9. Hit Apply, go back and do a Sync. Confirm the Sync is successful.
10. Go to QMC > Users > Filter by "User directory". Confirm the users are fetched.
With content cache-controls, you can modify the cache behavior of the browser. The cache-control is used on endpoints handled by the repository service. This functionality is disabled by default and can be enabled by modifying the files Repository.exe.conf and capabilities.json, followed by a restart of the Qlik Sense Service Dispatcher and the Qlik Sense Repository Service.
Cache-control for endpoints handled by the repository service was introduced in Qlik Sense Enterprise on Windows February 2022 (Patch 1). In the May 2022 release further enhancements were made to extend caching policies for requests specific to the Hub service. Upgrade Qlik Sense to make use of the new features.
In this article, we walk you through modifying the cache control policy and how to apply it globally across your Qlik Sense Enterprise on Windows environment.
Please note the following before modifying cache control headers:
Prior to applying any changes in a production environment, evaluate the risks of the changes.
The feature is disabled by default. For details, see Configuring content cache-control.
These are the predefined cache-control header values:
"CachePolicyEnum": { "values": [ "0: Normal", -> public, max-age=3600 "1: MustRevalidate", -> public, must-revalidate, max-age=0 "2: PrivateNormal", -> private, max-age=3600 "3: PrivateMustRevalidate", -> private, must-revalidate, max-age=0 "4: NoStore" -> no-store ] }
You can create a global cache control policy (not tied to a content library) by using either the API or an SQL query against the QRS database. A restart of the Qlik Sense Service Dispatcher and Qlik Sense Repository service is required after.
API example:
POST /qrs/ContentCacheControl
{ "id": "e07ca071-7d72-417d-93c2-d60687f747a8", "name": "api", "contentLibrary": null, "filter": "api", "maxAge": 3600, "cachePolicy": 4, "privileges": null }
INSERT INTO public."ContentCacheControls" ("ID", "CreatedDate", "ModifiedDate", "ModifiedByUserName", "Name", "Filter", "MaxAge", "CachePolicy", "ContentLibrary_ID") VALUES ('e07ca071-7d72-417d-93c2-d60687f747a8', '2022-08-19 14:28:48.077709', '2022-08-19 14:28:48.077709', 'RDLUND\svc-silver', 'api', 'api', 3600, 4, null);
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.
What's new in Qlik Sense February 2022
What's new in Qlik Sense May 2022
Qlik Sense Enterprise on Windows
QB-11410
This article describes how to resolve the NPrinting connection verification error:
x Qlik NPrinting webrenderer can reach Qlik Sense hub error
The Qlik Sense Repository Service can suddenly come to a situation where the CPU utilization of the central node increases beyond 95%, which causes effects in the Qlik Sense hub (sheets go blank and other unexpected slow behavior). The process that is consuming the maximum CPU can be seen as the Qlik Sense Repository Service.
Identified in a Problem Investigation with R&D, one of the possible causes is related to large number number of open transactions in the repository database and locks held by large number of sessions impacting on the repository service communication with the repository database.
Qlik Sense Enterprise on Windows November 2017 and later versions
Setting the idle_in_transaction_session_timeout to 5 minutes would clear the threads the repository database and progresses the new threads in the queue
SHOW idle_in_transaction_session_timeout;
alter system set idle_in_transaction_session_timeout to '5min';
SHOW idle_in_transaction_session_timeout;
# reload the configuration
select pg_reload_conf();
#idle_in_transaction_session_timeout = 0 # in milliseconds, 0 is disabled
And changing it to:idle_in_transaction_session_timeout = 300000 # in milliseconds, 0 is disabled
Save, and then schedule a restart.
Changing the value, idle_in_transaction_session_timeout terminates any session with an open transaction that has been idle for longer than the specified duration in milliseconds. This allows any locks held by that session to be released and the connection slot to be reused decreasing over CPU utilization.
This article explains how to change the default locale in QlikSense Server when you create a new app on the hub.
Qlik Sense Enterprise on Windows
When you create a new application on the hub, the default locale is based on the settings on the QlikSense Server.
In order to change this setting, it is required to change the locale settings on the server for the account that is running the services.
If you run services as local system, you will need to use a tool such as Psexec in order to be able to execute the control panel as local system and change this settings.
QlikView Server May 2022 (12.70)
IIS
SAML authentication
A Qlik Compose task may fail during a full load but will run OK after a retry or when started at a different time.
The task error log shows:
main 2023-10-30 08:39:51.396 [engine ] [ERROR ] [] Failed to create temporary file for /com/sun/jna/win32-x86-64/jnidispatch.dll library: C:\Windows\TEMP\jna--187113817\jna4331371764969383844.dll (The process cannot access the file because it is being used by another process)
The error indicates that a virus scan or malware scan was active while the Qlik Compose task was run. This locked the files needed.
Exclude the Qlik Compose installation folder from the virus scan. The default path is: C:\Program Files\Qlik\Compose
Do not run any Qlik Compose task to run during scheduled virus scans.
The Qlik NPrinting Engine cannot resolve requests for tasks which include Qlikview Entity reports that output to PDF or is not printing QlikView Entity reports to PDF.
An error is displayed when attempting to edit or print the QlikView Entity report:
Error: QlikView NPrinting PDF Printer not installed or not properly registered
Or the report fails silently while the following is printed in the Qlik NPrinting logs:
resolution aborted with exception System.Runtime.InteropServices.COMException (0x80004005): Error HRESULT E_FAIL has been returned from a call to a COM component.↵↓ at Tracker.PDFXChange.IPXCControlEx.get_Printer(String pServerName, String pPrinterName, String pRegKey, String pDevCode)↵↓ at Qlik.Reporting.Printers.QlikPdfPrinter.Win64PrinterFactory.get_Item(String pServerName, String pPrinterName, String pRegKey, String pDevCode
When you install Qlik NPrinting, the Windows service “Print spooler” must be up and running. If it is disabled, the Qlik NPrinting Printer will not be added during the installation. Similarly, if a separate PDF-XChange driver is installed, the Qlik NPrinting engine install will not install the QlikView NPrinting PDF-Printer.
NPrinting: PDF reports generation fails after disabling the Windows Spooler service
QB-14941
Description of Property "force-unused-resolvers-closure-policy":
*NOTE: The term 'Large' is relative to the amount of RAM on your NP server. If low Ram like 64 or 128 GB RAM, then 1 GB QVW is 'large' since it may grow as large as 10 GB in memory. Then if you have 8 cores, it will open 16 processes each potentially with 10 GB each since NPrinting will use every core process by default to generate a single report. (https://help.qlik.com/en-US/nprinting/February2019/Content/NPrinting/DeployingQVNprinting/Performance.htm)
Qlik NPrinting June 2018 or higher. Do not apply to previous versions.
NOTE: Please ensure to back up the scheduler.config file before proceeding
Note: Config file changes are overwritten upon upgrading NPrinting. Please apply these changes again after upgrading if the issues persist.
We recommend to follow this article in case the problem persists.
NPrinting tasks connecting to QlikView look stuck in Running status. The task manager on the Engine nodes shows some Qv.exe processes running, but the RAM and CPU usage does not change.
<!-- <add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" /> -->
<add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" />
NPrinting Engine needs to open QlikView Desktop in the background to communicate with the source QVWs during the generation of the reports in the tasks. These Qv.exe processes can be seen in the task manager under the Detail tab.
For some reasons that are currently under investigation, it can happen that the QlikView processes stuck and are not able to send the needed information to NPrinting. Therefore the report creation can't proceed and the tasks remain in Running status without progress.
When the option in 'Resolution' is active, NPrinting monitors the status of the Qv.exe processes and close them when they are stuck. A new Qv.exe process will automatically opened to replace the killed one.
This solution (modifying ServiceConfiguration.xml) is only valid for versions 6.6 to 7.0.
SSL Certificates that are imported are being replaced by Replicate’s self-assigning certificate on reboot.
The Service Configuration parameters need to be changed to allow Qlik Replicate to stop testing the HTTP URL and overriding with a self-assigned certificate.
testHttps = "false"
<ServiceConfiguration url="https://demo.com:443/attunityreplicate;http://demo.com:80/attunityreplicate" allowUnsafeProtocols="false" testHttps = "false" />
RepUiCtl.exe -d f:\data certificate clean
Qlik Replicate 6.6 - 7.0
This article will guide you on how to check audit logs to see users' activity on object/sheet/app.
First of all, we would need to enable Audit Logs on Qlik Sense side, to do so, you can follow this guide.
Once done all the steps from the above's guide, then we can check all user activity on object/sheet/level through the Operations Monitor app (from Qlik Sense 2019 release).
In the example below we will see a graphic example of how to check this information from Audit Logs.
User with ID "f9b8183a-bc07-4571-8ccb-94f7a1c5d9db" navigates into app with ID "1e4a22db-7395-46b3-bd43-78bc4cef811f" and then clicks on sheet with ID "1e4a22db-7395-46b3-bd43-78bc4cef811f" and finally selects a dimension:
User performing selections on an app
As we enabled Audit Logs, all traces coming from users selections will be logged on this path location: C:\ProgramData\Qlik\Sense\Log\Engine\Trace\ServerName_Audit_Engine.txt
Now we can check the audit logs directly from Operations Monitor app:
Checking logs through the Operations Monitor app
Furthermore, you could also check from logs the object ID and action performed on it on the following columns from C:\ProgramData\Qlik\Sense\Log\Engine\Trace\ServerName_Audit_Engine.txt:
Checking object ID and action performed
Qlik Sense Enterprise on Windows
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 enable Audit Logging in Qlik Sense Enterprise on Windows
The user that runs the Qlik Sense Enterprise on Windows services is commonly referred to as the Qlik Sense Enterprise service account. The user is defined as the "Log On As" user in Windows service settings.
In a multi-node deployment it is recommended to use the same domain user for all Qlik Sense services on all nodes the same deployment.
NOTE: Qlik Sense Repository Database service is an exception, and is expected to always run as Local System.
Confirm the current Qlik Sense Enterprise service account;
When exporting data from a Qlik Sense App, the Printing Service creates a temporary file which is stored in a temporary folder.
Exported XLSX files are stored in: C:\ProgramData\Qlik\Sense\Repository\TempContent.
The folder is in the node where the repository is installed.
The data is automatically deleted after 10 minutes by the Engine.
This is not currently a configurable property.
How to change how long temporary excel files are stored by the QlikView server
Previewing or publishing a Qlik NPrinting PowerPoint reports fails with the message:
Some of row's cells lay outside column
Remove any merged cells from the report.
This is caused by the 'Aspose' library Qlik NPrinting uses for generating reports.
There has always been a noticeable gap in Qlik Replicate, where users had no means of importing just an endpoint into Qlik Replicate. This article provides a workaround to that limitation.
{
"cmd.replication_definition": {
"databases": [{
...
}]
},
"_version": {
...
}
}
Verify that your endpoint name is correct.
You may want to skip entering the password and add it later through the user interface. Inputting the password in the JSON is in plain text.
{
"cmd.replication_definition": {
"databases": [{
"name": "DB2z_Source",
"description": "",
"role": "SOURCE",
"is_licensed": true,
"type_id": "DB2ZOS_NATIVE_COMPONENT_TYPE",
"db_settings": {
"$type": "Db2zosSettings",
"additionalConnectionProperties": "MaryHad=aLittleLamb",
"username": "dimae",
"databaseAlias": "DBALIAS",
"server": "lpardns.mydomain.com",
"port": 5035,
"databaseName": "LOCATION",
"CCSIDMapping": "234,ibm-p100-2345",
"ifi306SpName": "R4Z_UDF_ALL_NEW"
},
"override_properties": {
}
}]
},
"_version": {
"version": "2023.5.0.213",
"version_major": 2023,
"version_minor": 5,
"version_revision": 213
}
}
repctl importrepository json_file=NAMEOFFILE.JSON folder_name=DRIVE:\FOLDER
Editing an exported (json) file
ImportAll | Enterprise Manager API
Exporting and importing tasks
Importing tasks
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.
After upgrading from Windows 10 to Windows 11, or applying certain patches to Windows Server 2016, Qlik Replicate may not load in the browser.
The following error is displayed:
ERR_SSL_KEY_USAGE_INCOMPATIBLE
Qlik Replicate 2022.11 (may happen with other versions)
Qlik Compose 2022.5 (may happen with other versions)
Qlik Enterprise Manager 2022.11 (may happen with other versions)
Use of the self-signed SSL certificate
Windows 11
Windows server 2016
This issue has to do with the self-signed SSL certificate. Deleting the existing one and allowing Qlik Replicate/Compose/Enterprise Manager to regenerate them resolves the issue.
For Qlik Compose:
For Qlik Enterprise Manager:
Navigate to the ..\Attunity\Enterprise Manager\bin directory and then run the following command:Qlik Replicate will now allow you to open the user interface once again.
If users still cannot log in and are returned to the log in prompt at each attempt, see How to change the Qlik Replicate URL on a Windows host.
The CPU affinity is not working as expected. The number of CPU affinity for the QVS does not match the cores in the Server.
QlikView
Generation 9 HP servers
This issue comes from a new BIOS setting introduced in Generation 9 of HP servers. A new setting has been added in BIOS that needs to be modified to allow the QlikView services to properly detect all the CPU Cores in the machine.
This can be resolved by changing the BIOS setting "NUMA Group Size" to "Flat". The default setting for "NUMA Group Size" disables QlikView from properly detecting all CPU cores in the hardware.
Accessing the Qlik Sense Enterprise on Windows Hub and Qlik Sense Management Console using the hostname or FQDN, returns the error:
This site can't be reached
ERR_CONNECTION_TIMED_OUT
Accessing either the Management Console or Hub using localhost (localhost/qmc or localhost/hub) works.
The likely root cause is a wrong fixed IPv6 and IPv4 address in the pg_hba.conf file and hosts file.
The paths in the instructions are adapted to a default PostgreSQL installation used as database on a dedicated server. A PostgreSQL database installed by Qlik Sense has the following database path: %ProgramData%\Qlik\Sense\Repository\PostgreSQL\<version>\.
To resolve an IP mismatch:
fe80::1d08:f195:bee:****** is the IPV6 address
172.16.16.**** is the IPV4 address
When a Windows Machine snapshot restore is performed, the IPs will change, and the network will be routed to old/existing IPs fixed in the above-affected config files (hosts and pg_hba.conf). This needs to be replaced with new IPs.
Qlik Sense Enterprise on Windows
Qlik Sense - How to troubleshoot the issue to access QMC and HUB
The Qlik Enterprise Manager has two licensed modules:
Replication Analytics - Provides measurements of server and task metrics over a specific time-period.
A sqlite editor and knowledge on how to use it is required for this change, such as the DB Browser for SQLite: https://sqlitebrowser.org/
The backup step is crucial. Always back up your setup before proceeding with database changes.
The main Analytics tab is shown by default, regardless of whether or not you have registered a Replication Analytics license. If you do not intend to use the Replication Analytics module, you can hide the tab by either clicking the Hide Analytics Dashboards link in the Analytics tab or by following the procedure described below.
This option is only available if no Replication Analytics license is registered.
To show/hide the main Analytics tab:
In the Qlik Enterprise Manager Console, Click Settings (cogwheel on the right)
Select the Licenses tab.
Select the Replication Analytics sub-tab.
Clear or select the Hide Analytics Dashboards check box as required.
Click Save.
Registering and managing licenses