Qlik Sense patches can be downloaded from the Qlik Download page. 

Patches are cumulative and only one patch can be installed at a time.

Example: Patch 4 for Qlik Sense February 2019 will include all fixes from 3, 2, and 1.

Environment:

Qlik Sense Enterprise on Windows 

To install:

1. Download the required patch 
2. Schedule a brief down period as the server will need to be restarted
3. Execute the patch installation package and follow the on-screen instructions
4. Restart the Windows server host

To uninstall:

Executing a patch installation package will automatically uninstall the previous patch and install the new one. If you need to uninstall a patch manually:

1. Open the Windows Add and Remove Programs menu
2. Click View installed updates from the left panel
3. Locate the Patch
4. Uninstall the Patch
5. Restart the Windows Server host

If uninstall through Control Panel is not possible:

We look for the Qlik_Sense_update.exe installer package in C:\ProgramData\Package Cache\[guid]\. If the package required for the uninstall has been removed or renamed, a possible workaround is to obtain an exact copy (same version, release) of the Qlik_Sense_update.exe from a different environment and manually replacing it.

Installing, upgrading, and managing the Qlik Cloud Monitoring Apps for user-based subscriptions has just gotten a whole lot easier! With two new Qlik Application Automation templates coupled with Qlik Data Alerts, you can now: 

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. Repeat Step 1 to complete the update. 

The above allows you to deploy the monitoring apps to your tenant with a hands-off approach. Dive into the individual components below. 

Content:

• Part One: 'Qlik Cloud Monitoring Apps for user-based subscriptions' template overview
• Part Two: 'Qlik Cloud Monitoring Apps API Key Rotator' template overview
• Part Three: How to setup a Qlik Alert to know when an app is out of date
• A Qlik Cloud Monitoring Apps Workflow Demo (Video)
• FAQ

Part One: 'Qlik Cloud Monitoring Apps for user-based subscriptions' template overview

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.

Features

• Can install/upgrade all or select apps.
• Can create or leverage existing spaces.
• Programmatically handles pre-requisite settings, roles, and entitlements.
• Installs latest versions from Qlik’s OSS GitHub.
• Creates required API key.
• Creates required analytics data connection.
• Can create custom reload schedules.
• Can reload post-install.
• Tags apps appropriately to track which are installed and their respective versions.

Click-through installer:

Flow:

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.

 

Part Two: 'Qlik Cloud Monitoring Apps API Key Rotator' template overview

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.

Configuration

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.

Part Three: How to setup a Qlik Alert to know when an app is out of date

Each Qlik Cloud Monitoring App has the following two variables:

• vLatestVersion: the latest version of the app released on Qlik’s OSS GitHub.
• vIsLatestVersion: a Boolean of whether the app’s current version is equal to the latest version of the app released on Qlik’s OSS GitHub (1 if true, 0 if false).

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:

1. Right-click on a chart in the app, select Alerts and then Create new alert.
2. Clear out the defaults and provide the alert with a name such as <Monitoring App Name> is Out of Date.
3. Select Add measure and select the fx icon to enter a custom expression. Enter the expression ’$(vLatestVersion)'. Ensure it is wrapped in single quotes, then provide the label for the expression Latest Version.
4. Select Add measure and select the fx icon to enter a custom expression. Enter the expression $(vIsLatestVersion), then provide the label for the expression Is Latest Version.
5. Confirm the Details & data tab resembles the following:
   
   
   
   
6. Navigate to the next tab, Conditions.
7. Set the Measure to Is Latest Version, the Operator to Equal to, and the Value to 0. This way, if the app is not the latest version (0), it will trigger the alert.
8. Confirm that the Conditions tab resembles the following:
   
   
   
   
9. Navigate to the Distribution tab and confirm that the alert is evaluated When data is refreshed.

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:

A Qlik Cloud Monitoring Apps Workflow Demo (Video)

FAQ

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.

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. 

Before modifying the cache-controls

Please note the following before modifying cache control headers:

• It is generally not recommended to manually alter the cache-control headers.
• Make sure that you understand how the browser caching behavior is affected by the changes.

• Prior to applying any changes in a production environment, evaluate the risks of the changes.

Enable the feature

The feature is disabled by default.  For details, see Configuring content cache-control.

1. Open C:\Program Files\Qlik\Sense\Repository\Repository.exe.conf
   
   
2. Modify the following key and set it to true:
   
   <add key="ContentCacheControl" value="true" />
   
   Save the file.
   
   
3. Open C:\Program Files\Qlik\Sense\CapabilityService\capabilities.json
   
   
4. Add the following flag:
   
   {"contentHash":"2ae4a99c9f17ab76e1eeb27bc4211874","originalClassName":"FeatureToggle","flag":"QMC_CONTENT_CACHE_CONTROL","enabled":true}
   
   Save the file.
   
   
5. Restart the Qlik Sense Repository Service and Qlik Sense Dispatcher Service

Modify cache-controls in the Qlik Sense Management Console

1. After enabling cache-control, open the Qlik Sense Management Console
2. Go to Content Libraries
   
   
   
   
3. Open the Content Library you wish to configure
   
   
   
   
4. In the Associated Items menu, select Content cache-controls
5. Click Link new content cache control
   
   
   
   
6. Configure the cache-controls as per Content cache-controls  and click Add
   
   The cache control will automatically be linked.
   
   
   
   
7. Restart the Qlik Sense Service Dispatcher and Qlik Sense Repository Service

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
    ]
}

To modify the cache-control policy on a global level

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
}

Database Query example:

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);

• Please update the values of "CreatedDate", "ModifiedDate", "ModifiedByUserName" keys and keep the rest of them unchanged. The ID can be any unique quid value.
• Please modify the value of "Filter" to a customised filter by using regex as per Content cache-controls.

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.

Related Content 

What's new in Qlik Sense February 2022 
What's new in Qlik Sense May 2022 

Environment

Qlik Sense Enterprise on Windows 

Internal Investigation ID(s):

QB-11410

End of Support for Qlik products follows Release Management Policy, as documented in the Product Terms found on the Qlik Site: On-Premise Products Release Management Policy

For detailed information on end of life and release dates, see:

Qlik Sense Enterprise on Windows Product Lifecycle  
Qlik NPrinting Product Lifecycle 
QlikView Product Lifecycle  

Related Content:

• NPrinting 16 to NPrinting 19+ Migration Playbook
• QlikView Release Management and End of Life
• On-Premise Products Release Management Policy

This article describes how to resolve the NPrinting connection verification error:

x Qlik NPrinting webrenderer can reach Qlik Sense hub error

Environment

• NPrinting: all versions
• Qlik Sense: all versions
  • multi-node QS proxy environment
  • NLB (Network Load Balancer or Alias URL) server address used in front of cluster of Qlik Sense proxy nodes (which are linked to a Virtual Proxy. Proxy nodes will not work with NPrinting unless they are linked to a QS virtual proxy)

Resolution

• Although it is possible to use an NLB address in front of your QS proxy nodes that are used by NPrinting, the error generated in the NP connection verification process will appear as described in the article title
• This error can safely be ignored as this does not affect generation of NPrinting connections
• To eliminate the 'error' message, you would need to update your NPrinting connection to use a virtual proxy node address/computer name behind the NLB address . It must be the computer name and not an alias url).
• The proxy node used must be linked to a virtual proxy with the following required attribute
  
  • Microsoft Windows NTML authentication on the Qlik Sense proxy. (SAML and JWT are not supported. If your virtual proxy uses SAML or JWT authentication, you need to add a new virtual proxy with NTLM enabled for Qlik NPrinting connections).
  • A link between the proxy node and virtual proxy.
  • For all NPrinting to Qlik Sense requirements visit https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#anchor-1

Related Content

• https://help.qlik.com/en-US/nprinting/Content/NPrinting/Troubleshooting/Verify-connection-to-Sense-errors.htm
• https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#Requirem

Internal Investigation ID

• QB-2871

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. 

Environment:

Qlik Sense Enterprise on Windows November 2017 and later versions 

Resolution: 

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

1. Connect to the QSR database using PGADMIN4
   • Reference: Installing and Configuring PGAdmin 4 to access the PostgreSQL database used by Qlik Sense or NPrinting
   • Qlik Support does not support the direct query and access to the underlying product's database hosted by PostgreSQL. If any issues arise for which direct queries are deemed responsible, Qlik Support will reserve the right to request that a previous working backup is restored to the system in order to bring back full operation or resolve any isolated issue(s). The steps described here in this article are only used by Qlik Support for troubleshooting purposes.
2. Right-click the QSR database and bring up the Query Tool. 
3. Run the following command to look at the default value of the idle_in_transaction_session_timeout. 
   

   SHOW idle_in_transaction_session_timeout;​

4. By default, this is set to 0. 
5. Update the value by running the following command: 
   

   alter system set idle_in_transaction_session_timeout to '5min';​

6. Confirm the value has been updated running the following: 
   

   SHOW idle_in_transaction_session_timeout;  
   # reload the configuration     
   select pg_reload_conf();​

   
   Example:
   
   
   
7. The same setting could be done by editing the following file:
   
   C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\9.6\postgresql.conf
   
   By searching for:
   

   #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. 

Cause:

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. 

 

The syntax used for creating expressions on column names that contain the symbol '$' differs between Qlik Replicate versions. This article documents the two different methods.

The syntax changed with the May 2023 release. Previously, the syntax allowed the full column name to be recognized with a '$' symbol in front of the column name. With the current syntax, Qlik Replicate interprets these expressions as containing two separate columns and will error out. 

Content:

• Qlik Replicate May 2023 and later
• Qlik Replicate versionspriorto May 2023

Qlik Replicate May 2023 and later

Starting with the May 2023 release, extra '$' symbols are treated as an additional column name. To correctly format the expression to read it as a single column, the setting Support special characters in column names used in expressions must be enabled and the syntax of double quoting the column name should be used.

Enable the transformation setting:

1. Open your Endpoint's Task settings
2. Go to Task settings
3. Go to Transformations and Filters 
4. Open Expression Defaults
5. Check Support special characters in column names used in expressions
   
   
   

Syntax example:

Column name: IXF$RP
Expression: "IXF$RP"

If support for special characters is not toggled on, the Parse expression will not parse.

If the extra '$' is used, the expression will treat the column name as two separate columns. Running the expression as is will lead to the task failing with "Failed to init column calculation expression".

Qlik Replicate versions prior to May 2023

Previous syntax example:

Column name: IXF$RP
Expression: $IXF$RP

Related Content

Transformations and Filters 

The warning and example provided in the user guide refer to string literals used in an expression and not the column name. Single quotes should be used for the string literals and not the column name.

Environment

Qlik Replicate

This article is intended to get started with the Microsoft Outlook 365 connector in Qlik Application Automation.

Authentication and Authorization

To authenticate with Microsoft Outlook 365 you create a new connection. The connector makes use of OAuth2 for authentication and authorization purposes. You will be prompted with a popup screen to consent a list of permissions for Qlik Application Automation to use. The Oauth scopes that are requested are:

• Mail.Send
• User.Read
• Offline_access

Sending Email with the Microsoft Outlook 365 connector

The scope of this connector has been limited to only sending emails. Currently, we do not enable sending email attachments and are looking to provide this functionality in the future. The suggested approach is to upload files to a different platform, e.g. Onedrive or Dropbox and create a sharing link that can be included in the email body.

The following parameters are available on the Send Email block:

• To: A comma separated list of recipients;
• CC: A comma separated list of recipients to which the email should be copied;
• BCC: A comma separated list of recipients to which the email should be blind copied;
• Subject: A title for your email;
• Type: Choose between plain text email or HTML;
• Body: The content of your email. You can use HTML for your email if chosen as the type.

Generating a report and sending an email with the report

As we do not currently support email attachments, we need to first generate a sharing link in Onedrive or an alternative file sharing service. The following automation shows how to generate a report from a Qlik Sense app, upload the report to Microsoft Onedrive, create a sharing link and send out an email with the sharing link in the body. This automation is also attached as JSON in the attachment to this post.

Environment:

Qlik Application Automation 

During a Replicate Full Load, incoming changes occur while the Full load is in progress. What happens to those changes?

Qlik replicate starts the CDC thread before starting the Full load and all the changes show as cached events while the Full load is running. For example, 2 billion records are applied in the Full load state and Replicate again check at the end of the Full load for committed changes.  If 100k changes are also committed before finished then it will also be applied in the full load otherwise the 100k changes will go to CDC.

Another example, for a full load takes 12 hours, then updates during the 12 hours full load window are also applied. Note- these two examples assume you have CDC enabled in the task.

If CDC is turned off during a full load task, then Replicate will not capture the cached events.

Environment

• Qlik Replicate 

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.

This article explains how to change the default locale in QlikSense Server when you create a new app on the hub.

Environment:

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. 

1. Open the IIS Manager console and navigate to (a) Default Website, (b) QvAjaxZfc, (c) Application Settings
   
   
   
   
2. Check for the entry: StrictRedirection with a value as false
   
   
   
   
3. If StrictRedirection entry isn't present, click (a) Add under the Actions menu, and then enter (b) StrictRedirection under Name: and False under Value:
   
   
   
   
4. Click the OK button, then test by restarting the browser running the AccessPoint and log in again.

Environment

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)

Cause

The error indicates that a virus scan or malware scan was active while the Qlik Compose task was run. This locked the files needed. 

Resolution

Option One: Exclude Qlik Compose from virus scans

Exclude the Qlik Compose installation folder from the virus scan. The default path is: C:\Program Files\Qlik\Compose

Option Two: Schedule scans while no tasks run

Do not run any Qlik Compose task to run during scheduled virus scans.

Using a Sybase ASE source endpoint, Qlik Replicate may not capture or simply ignore all DDL (Data Definition Language) commands, while DML (Data Manipulation Language) commands (Insert/Update/Delete) are captured and applied successfully. 

Example of DDL in a source database:

alter table db_test.dbo.tb_test add notes varchar(50) null

Qlik Replicate ignores the above DDL. Reviewing the task logs (if set to trace or verbose logging level) shows:

[SOURCE_CAPTURE ]T: Captured DDL / type for table dbo.tb_test (identified by objid 672002394) is not known to metadata manager. Irrelevant DDL - ignored... (sybase_endpoint_metadata.c:710)

Resolution

Verify the user's privileges as per Required permissions for SAP Sybase AES.

Example of how to create a user (qruser) which owns sufficient permissions and works fine with DML/DDL operations:

create login qruser with password qruser123
sp_adduser qruser
grant role sa_role, replication_role, sybase_ts_role to qruser
sp_displaylogin qruser;

Internal Investigation ID(s) 

#00112248 

Environment

• Qlik Replicate all versions , on both platforms: Windows and Linux
• Sybase ASE all versions , on both platforms: Windows and Linux

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. 

Resolution

1. Verify if a separate PDF-XChange printer is listed in the Devices and Printers applet under  \Control Panel\Hardware and Sound\Devices and Printers 
2. If a separate PDF-XChange printer exists, manually uninstall it
3. Ensure the Spooler (Print Spooler) service is running via Windows Task Manager
4. Then re-Install Qlik NPrinting Engine
5. Confirm that the Qlik NPrinting printer driver appears in the Devices and Printers applet under  \Control Panel\Hardware and Sound\Devices and Printers

    

   

Related Content

NPrinting: PDF reports generation fails after disabling the Windows Spooler service

Environment

Qlik NPrinting 

Internal Investigation ID(s):

QB-14941

Description of Property "force-unused-resolvers-closure-policy":

• On the NP Server add a setting to a scheduler.config file that will force closure of the internal connections (qv.exe processes) once they have become idle. 
• Forcing resolver closures may be useful if engine machines have low RAM capability and/or in case of NP connections to Large* Qlik Applications.
• "0" is Default Value/Default NPrinting Behavior: a resolver will be closed only if it is the best option based on current load and what the internal algorithm determines
• "1" force closure of all open resolvers: when the system does not have open execution requests upon them
• "2" force closure of idle connections: if the connection is used occasionally - weekly, monthly, yearly etc. vs connections that a used with reports that run on a schedule trigger daily or hourly.

*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) 

Environment

Qlik NPrinting June 2018 or higher. Do not apply to previous versions. 

Resolution

NOTE: Please ensure to back up the scheduler.config file before proceeding

1. Stop the NPrinting services on the NPrinting Server. Please stop all NP engines if installed on different server computers.
2. Make a copy of "C:\Program Files\NPrintingServer\NPrinting\Scheduler\scheduler.config"
3. Launch Notepad as an admin and edit "C:\Program Files\NPrintingServer\NPrinting\Scheduler\scheduler.config"
4.  Add the following key:
   <add key="force-unused-resolvers-closure-policy" value="1" /> 
   right before the final  </appSettings> line
5. Save the file and restart all the NP services. 
6. Please restart all NP engines if installed on different server computers.

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.

Environment

• Qlik NPrinting Nov 2019 SR1 and above 
• QlikView 

Resolution

1. Stop the NPrinting services
2. Open the file: 
   C:\Program Files\NPrintingServer\NPrinting\Scheduler\scheduler.config
3. Look for the line:
   

   <!-- <add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" /> -->​

4. Un-comment it as follow:
   

   <add key="qlikview-stuck-process-monitor-settings" value="300:10000:15:0.0005" />​

5. Restart the NPrinting services.

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. 

Resolution

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.

1. Locate the data directory for Qlik Replicate
   
   If the data directory was installed in a different location,  check by going to: 
   
   
   1. Services in the Start Menu
   2. Locating Attunity Replicate Server (May be named Qilk depending on installation)
   3. Right-click and choose Properties
      
      
      
      
   4. Data Directory location will be displayed after -d
      
      
2. Open the data directory
   
   
3. Open ServiceConfiguration.xml found in the Qlik Replicate data directory with any text editor
   
   Add the following to the ending of the service configuration:
   
   

   testHttps = "false"

   
   Full example:
   
   

   <ServiceConfiguration url="https://demo.com:443/attunityreplicate;http://demo.com:80/attunityreplicate" allowUnsafeProtocols="false" testHttps = "false" />

   
   
4. Save the file and reboot the machine
   
   
5. Clean the old SSL certificate and import the new certificate
   
   If the data directory is installed in a different location, add the data directory path to the certificate clean command:
   
   

   RepUiCtl.exe -d f:\data certificate clean​

Environment

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:

1. Go to Qlik Sense Hub
2. Under streams on the left hand side, click on "Monitoring apps"
3. Then click on "Operations Monitor" app
4. Then we can filter the Audit Logs we enabled before so we can check which actions have been performed on sheet/app level by any user
5. In the example we can see in the gif below, we are performing the following selections to filter:
   1. We first filter by app (where we performed the selections on the bar chart)
   2. Then the gif also shows more filter examples that you could use to filter your data from Audit Logs

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

Environment

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.

Related Content 

How to enable Audit Logging in Qlik Sense Enterprise on Windows

This article gives an overview of the Splunk Connector in Qlik Application Automation.
The Splunk connector has been created with the following use cases in mind:

• Being able to perform searches to a Splunk instance
• Inserting new events into Splunk using the HTTP Event Collector

Connecting the Splunk connector

The Splunk connector makes use of basic authentication. When connecting the connector, you will be prompted with the following popup screen:

Hostname: The hostname or IP address of the Splunk instance. Exclude the http(s):// part and the port number of the URL.
Username: The username you use to login to Splunk
Password: The password you use to login to Splunk
Use SSL: Select whether the management service of Splunk makes use of SSL. Default yes.
Management port: The port on which the management service of Splunk is running. Default is 8089. Providing no value will omit the port from the final URL.

Performing a search on Splunk

To perform searches using the Splunk connector it is possible to perform a synchronous search as well as an asynchronous search. The synchronous search has a timeout of 50 seconds, with the asynchronous search it is possible to have a longer window before the automation will timeout.

Synchronous Search

The synchronous search can be done using the Synchronous Search block. In the Search Query block you will have to provide a splunk search query.

Asynchronous Search

The asynchronous search block can be manually done using the block Asynchronous Search block. Then perform polling using the Get Search block using the returned Search ID. When finished, results can be obtained using the Get Results From Search block.

Alternatively it is possible to use the block Do Asynchronous Search and get Results. This block will perform the polling, only a search query has to be provided to obtain a list of results.

Sending data into Splunk

The other use of the Splunk connector is to send data into Splunk by making use of the HTTP Event Collector. An example usecase for this would be to send reload logs of a Qlik Sense app into Splunk.
To do this we will first have to create an HTTP Event Collector on the Splunk side.

To do this in Splunk go to Splunk in the web browser and go to Settings > Data > Data Inputs.
On this page you will see Http Event Collector. Press the Add new button.

Provide a name for the token and go to the next page. Select indexes to which this token can write. Click on Review and Submit. You will be given a token that you need to configure on the block.

In Qlik Application Automation make use of the Send Event block. For the inputs, enter the HEC token value. Provide the port for the HTTP event collector. This can be obtained from the Splunk HTTP Event Collector page when clicking on the Global Settings button. You can also find whether SSL is enabled for the HTTP Event Collector, select this value for the Hec_Use_Ssl parameter. Next, provide the index to which you're writing your events and provide a source string.
For data, you can map JSON message in the Event parameter.

The following example will perform a reload and send the reload log to Splunk:

In Splunk it is then possible to view the logs of the reload:

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 is legacy mode?
Legacy mode in Qlik Sense allows users who have access to the data load editor to write load statements which reference file paths rather than through LIB statements.

Simple example:
Standard Mode:
LOAD * 
FROM [lib://data/data.csv]
(txt, codepage is 28591, embedded labels, delimiter is ',', msq);

Legacy Mode:
LOAD * 
FROM C:\data\data.csv
(txt, codepage is 28591, embedded labels, delimiter is ',', msq);

What are the security considerations when using legacy mode?

Out of the box, for a user to do development in Qlik Sense, they need some combination of two types of access:

1. An ability to create a data connection
2. An ability to read (or see) a data connection

This security model is the intermediary between the user inside of Qlik Sense and the data sources.

When using legacy mode, any user who has access to the Data Load Editor can now access the file system of the local Qlik Sense server as well as any network file shares that the Qlik Sense service account independent of the security rules configured on the Qlik Sense deployment. In this example, the user has access to AttachedFiles, which all users would out of the box, as well as a Salesforce data connection, yet they are still able to load from the data.csv:

This means that the traditional mechanism for ensuring governance and security over data access inside of the Data Load Editor will no longer apply and the user(s) will be accessing the files as the Qlik Sense Service account

What are the benefits of using Legacy Mode?

This is difficult to answer in an exhaustive manner, but generally the benefits are narrowly scoped to deployments where app development, self-service capabilities are disabled or where this level of access is restricted to a vetted set of administrators. Some benefits include:

• The ability to use relative paths in load scripts (e.g. LOAD * FROM ..\..\Customer1\sales.csv). Often used in conjunction with include scripts which allow easy deployment to multiple customers or tenants.
• The ability to use the EXECUTE function (in conjunction with an additional Settings.ini change) to directly call external processes during script execution
• The ability to re-use load statements from QlikView documents in Qlik Sense
• And others

Is legacy mode recommended by Qlik?
For most deployments, no, legacy mode is not recommended. It can be useful in some deployment scenarios where the security concerns are mitigated.

How do I switch to Legacy mode / disable standard mode?
Disabling standard mode - Enabling Legacy Mode - Qlik Sense on Windows

Qlik Sense Legacy mode

Qlik Sense Legacy Mode - Qlik Design Blog