Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor and License Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

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 that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor and License Monitor

The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.

Basic information can be found here:

The License Monitor 
The Operations Monitor 

Both apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.

QVS files (read more) cannot be uploaded to Managed Spaces in Qlik Cloud.

Resolution

.qvs (QlikView Script) files cannot be directly uploaded to a managed space in Qlik Cloud. QlikView Script files are intended as reusable load script blocks and are not considered application files (such as .qvf and .qvw). 

To use a .qvs file, copy the script's contents into an app's load script editor or use an $(Include=...) statement to reference the file, which needs to be stored elsewhere and made accessible to the app.

Related Content

• Creating QVS files
• Uploading and sharing a QlikView app in Qlik Cloud

Environment

• Qlik Cloud Analytics

This article aims to answer the following questions:

• Is Stitch real-time?
• Why is my data taking so long to replicate?
• What is the ETL process for Stitch like?
• And what can it tell me about where my data is? 

Stitch Replication Overview

Stitch is a cloud-based ETL platform, which means it is not real-time and may experience latency due to the nature of cloud infrastructure and its step-based processing model.

Replication Process

Stitch’s replication process consists of three independent steps: 

Extraction → Preparation → Loading

Each step takes time to complete and is influenced by various factors.

For more information, see: Stitch’s Replication Process | stitchdata.com

Performance Factors

The speed and efficiency of Stitch’s replication process can be affected by:

• Volume and size of data: Impacts both extraction and loading times.
• Data structure: Flat data is processed more quickly; nested structures (e.g., JSON) can slow extraction.
• Source system/API limitations: API quotas and rate limits can delay extraction.
• Destination system performance: Affects how quickly data can be loaded.

These factors can vary over time and across integrations, which is why replication durations are not always predictable.

Extraction

The replication frequency determines how often Stitch initiates a new extraction job (when one isn’t already in progress). Stitch tracks your tables and updates them based on the replication method you’ve selected.

However, this frequency does not guarantee that data will be prepared and loaded within the same time window. For example, a 30-minute frequency does not mean the full replication cycle completes in 30 minutes.

Stitch extracts one table at a time per integration (sequentially). It must finish extracting one table before moving to the next.

Preparation

Once data is extracted, Stitch begins the preparation phase, which involves cutting records into rectangular staging files. This step is batch-based and starts as soon as data is returned from the source. The duration of this phase depends on the structure and volume of the data.

Loading

Stitch can load up to 5 tables concurrently per destination. If 5 tables are already loading, others must wait until a slot becomes available. For example, with 10 integrations and 20 tables each, Stitch will load 5 tables at a time per destination.

Stitch’s loading systems check every 15–20 minutes for batches of records that are fully prepared and ready to be loaded into your destination.

What may appear as missing data is often just incomplete processing. Most data discrepancies resolve themselves once Stitch finishes processing.

Related Content

• Replication Frequency
• System architecture
• Data Loading

Environment

• Qlik Stitch

This template was released on September 29, 2025.

Many customers rely on the Capacity Consumption Report in Qlik Cloud to understand usage and billing patterns. Until now, deploying and refreshing this app required repetitive manual steps: downloading from the admin console, publishing it into a managed space, and re-publishing every time a new version was needed.

This approach made monitoring difficult and often left customers with out-of-date insights.

What's new

A new Qlik Automate template automates the end-to-end deployment of the consumption app into a managed space of your choice. Once set up, the app is refreshed daily - ready for admins or billing users to work with.

With this in place, you can:

• Stay current – The app refreshes once per day (morning CET), so your analytics reflect the latest usage data.

• Collaborate easily – Place the app directly into a managed space for shared access.

• Enable subscriptions and alerts – Users can subscribe to sheets or KPIs, or create alerts on thresholds that matter to them.

• Maintain governance – The template creates/uses the right spaces and applies roles automatically.

• Eliminate manual work – No more re-publishing or searching through personal space copies.

How it works

• The automation checks that you are on a capacity-based subscription (your app size must be 100MB or less; larger data sets still need to be deployed manually or via script).

• It ensures you are a TenantAdmin (required for license and app access).

• It creates a staging space (for imports) and a managed space (for sharing).

• It imports the latest version of the app into staging, then publishes it to the managed space.

• You can configure how many historic versions you want to keep in the shared space. By default, no staged apps are kept.

Scheduling

Since the underlying data is refreshed once per day in the morning CET, we recommend scheduling this automation to run around midday CET. This ensures that your managed space always holds the latest daily version of the app.

Requirements

• TenantAdmin role

• Capacity-based subscription

• Report size ≤100MB (larger reports cannot currently be deployed with Qlik Automate)

Get Started

1. Create a new automation, navigate to the App Installer category, and select the Capacity consumption app deployer template.

2. Update the variables (space names, versions to keep).

3. Test manually once.

4. Schedule it to run daily (around midday CET).

Once enabled, you’ll have a single source of truth for consumption reporting - ready to drive alerts, subscriptions, and collaborative analysis across your admins.

Related Content

• Review the Help documentation on the capacity report to understand its metrics and counters.

Environment

• Qlik Cloud

This article is provided as is. For further customization or assistance, reach out to Qlik's Professional Services or engage in our Qlik Sense Administration and Configuration forum.

This details the steps required to use a Microsoft Excel (XLS) file as a User Directory in the User Directory Connector (UDC).

The instructions in this article are written for Microsoft Office 2016, which has reached end of life as of October 2025. As an alternative, use Microsoft 365 Access Runtime. See Download and install Microsoft 365 Access Runtime.

The required Microsoft Excel Driver may not be installed by default.  

1. Verify if the drivers are already installed on your server:
   
   Open the Windows Registry Editor and navigate to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\
   
   
    

   

   
   
   If it is not installed, download the latest Microsoft package.
   
   This file can be directly sourced from the Microsoft Download site. The 64-bit version is required.
   
   Example: Microsoft Access Database Engine 2016 Redistributable
   
   
   
2. Run the installer
   
   
3. Refresh the registry editor and verify that the drivers are correctly installed
   
   
   
   
4. Create an XLS file that contains your users
   
   A sample XLS file is attached to this article:
   
   
   • This file contains two sheets, "MyUsers" and "Attributes"; they can be renamed to fit your naming convention
   • The first sheet contains two columns: "userid" and "name"; those names are important and mandatory.

     Do not change them, or the import will fail.

   • The second sheet contains three columns: "userid", "type", and "value"
     
     
5. Create a new UDC
   1. Navigate to your User Directory Connector in the Qlik Sense Management Console
   2. Create a new connection: Excel (via ODBC)
   3. Untick the checkbox Sync user data for existing users
   4. User table Name must match your first sheet ("[MyUsers$]" here)
   5. Attribute table name must match the second sheet ("[Attributes$]" here)
   6. Modify the connection string to point to your Excel file: DRIVER={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};DBQ=C:\temp\SomeUsers.xls
      
      
      
      
6. Validate and check in the logs
   
   The following should be logged:
   
   Connection creation verified.
   Connection open verified.
   Tables verified.
   The userid field of the [MyUsers$] table is verified successfully.
   The name field of the [MyUsers$] table is verified successfully.   
   The userid field of the [Attributes$] table is verified successfully.   
   The type field of the [Attributes$] table is verified successfully.     
   The value field of the [Attributes$] table is verified successfully.  
   
   
7. Sync the UDC and check the logs
   
   Started synchronizing all users for ...
   Started syncing users
   ODBC dataReader have been successfully created
   Retrieved 3 entities from directory 'TEST' of type Repository.UserDirectoryConnectors.ODBC.OdbcExcel
   Database done with 3 users and 0 groups in user directory (TEST, ...)
   Ended saving users in repository
   Finished synchronizing all users for ...
   
   
8. Verify that the users were added in the Qlik Sense Management Console
   
   
   
   
9. Verify the attributes are reflected in the user's properties
   
   
   

Troubleshooting

The following errors you may be logged in C:\ProgramData\Qlik\Sense\Log\Repository\Trace\<SERVER>_UserManagement_Repository.txt
 

Verify that the name and userid columns in the file are correctly named and have not been renamed. 

Environment 

• Any version of Qlik Sense

Is it possible to migrate users and data connections from one Qlik Cloud Analytics tenant to another?

You cannot migrate users and data connections from an existing tenant to a newly purchased tenant.

The following will need to be done:

• All data connections must be recreated
• Apps and scripts in the new tenant need to have their data connections updated to reference the new connections
• For users, it will be necessary to send new invitations or configure your identity provider to manage access to your new Qlik Cloud tenant

What about apps and scripts?

Apps can be migrated from one tenant to another using the following Qlik CLI automation: Migrate apps between Qlik Cloud tenants 

This tutorial is not exhaustive, and does not migrate other resources such as spaces, automations, data alerts, subscriptions, notes, etc. Qlik offers solutions via Qlik Professional Services for complete tenant to tenant migrations.

For scripts, follow the process of exporting them manually from the old tenant and then importing them to the new tenant. See Exporting scripts.

To make the process easier for you, Qlik's customer support team can link the newly purchased tenant license to a trial tenant, and you can continue to use the trial tenant. The trial tenant will be updated to a Standard, Premium, or Enterprise version after linking the license (depending on which package was purchased).

Do you need iterative planning and support assistance?

If you're looking to perform a manual transfer but need assistance with iterative planning or direct engagement by Qlik, our Professional Services are ready to assist.

Additional References

• Exporting apps | help.qlik.com 
• How to export QVD files from a Qlik Cloud Tenant 

Environment

• Qlik Cloud Analytics

The "Enable IP Allowlist" option has been enabled, and several IPs have already been added to the list to restrict access solely to those on the allowlist. However, other IPs are still able to access TMC.

Cause

To configure an IP allowlist in Talend Management Console, the user account needs to possess the Security Administrator role.
Only accounts granted the "Users - Manage" permission can bypass the IP allowlist. (This permission is encompassed within the Security Administrator role.).

1. Verify the user's role; it must NOT include a role such as Security Administrator, as this role possesses the "Users - Manage" permission, which can bypass the IP allowlist. For more details about TMC role, please read this documentation page.
2. Verify the permissions assigned to the role. If you are uncertain whether this role possesses the "Users - Manage" permission, review the role's permissions as illustrated in the screenshot below.

Resolution

Once the IP allowlist is enabled, the same user account must take one of the following actions:
Either create additional users without the "Users-Manage" permission, Or remove its own Security Administrator role.
This guarantees that the IP allowlist is effectively enforced for the account.

Consequently, IP addresses not included in the IP allowlist will be unable to connect to TMC, as illustrated below:

Related Content 

Setting up IP allowlist policy to restrict user access

Environment

• Talend Cloud 8.0.1

***Changes must be made to all Qlik servers that will not be provided with internet access.***

For servers not connected to the internet, they may be prompted with a pop-up error when browsing in the Hub or in the Data Load Editor with the following errors:

• The Hub has continuous bubbles while loading forever
• The Hub is stuck on the initial loading bar

Browser Debug tools may display the following error in the console:

Cause:

This was originally defined as an issue with the Qlik Sense DataMarket connector executable, which is cryptography signed for authenticity verification, and the .NET Framework's verification procedure when launching an executable includes checking OCSP and Certificate Revocation List information, which means fetching it online if the system doesn't have a fresh cached copy locally.

Even without the QlikData Market being in use, the solutions provided can be deployed when encountering issues with Qlik Sense Enterprise Windows servers that have no internet access. Internet access is recommended.  
 

Resolution

Only deploy one of the below options.

Option 1 will persist through upgrades, whereas Option 2 would have to be reapplied after every Sense upgrade. 

Option 1:

1. Stop all Qlik Sense services on all nodes
2. Edit C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config
   1. If there is an empty <runtime/> tag, change it to

      <runtime>     
           <generatePublisherEvidence enabled="false"/>  
      </runtime>

   2. If there is no <runtime/> tag, add the below anywhere above the closing </configuration> tag.

      <runtime>
          <generatePublisherEvidence enabled="false"/> 
      </runtime>

   3. If the <runtime> section has existing content, add generatePublisherEvidence.

      <runtime>
        <some other key="value"/>
        <generatePublisherEvidence enabled="false"/>
      </runtime>

      Example:
      
3. Save machine.config
4. Repeat on all nodes (if applicable)
5. Start services on all nodes

Qlik Sense Enterprise on Windows facilitates the export of an Audit from the Qlik Sense Management Console. See Exporting audit query results.

This export works as expected unless the Audit result is filtered by one app and one user. If only one user and one app are used in the filter, the resulting Excel file is empty.

Resolution

This is a known defect (QCB-32416), which is expected to be fixed in a future release. Review the Qlik Sense Enterprise on Windows Release Notes for details.

Workaround:

Filter by more than one app and one user.

Internal Investigation ID(s)

Product Defect ID: QCB-32416

Environment

• Qlik Sense Enterprise on Windows May 2025 up to Patch 4
• Qlik Sense Enterprise on Windows November 2024 up to Patch 16

When using Talend Administration Center, you may encounter the following message

Error: License token will expire in xx days

This message refers to the license token expiring, not the license itself.

Resolution

Talend Administration Center has Internet access

• TAC automatically validates the license token.
• No manual action required.

Talend Administration Center has no Internet access

If TAC does not have Internet connectivity, follow these steps

1. Go to Talend Administration Center page and click:
   • Validate your license manually OR
   • Generate Validation Request (button name depends on TAC version).
2. A popup window will display a validation link (e.g. https://www.talend.com/api/get_tis_validation_token_form.php).
3. Copy this link into a text file.
4. On a machine with Internet access:
   • Paste the link into a browser.
   • Retrieve the validation token (e.g. 5xEfMp1ozPyiDTTUqzUHI8K3Xuvqx/iipc+).
5. Return to TAC on the offline system.
6. In the popup window:
   • Paste the validation token.
   • Click Enter validation token.

Your license token is now validated manually.

Cause

Talend Administration Center (TAC) requires an Internet connection during license token validation and the license token must be periodically validated.

• If TAC has Internet access, the token is validated automatically.
• If TAC does not have Internet access, you must manually validate the license token.

Related Content 

• Refer to the generating-validation-request-without-internet-connection for more details.
• You can also configure notifications to alert administrators before the license token expiration date managing-notifications.

Summary

If TAC has Internet access, license token validation is automatic. If not, use the manual validation process by generating a request, retrieving the validation token from another machine, and pasting it back into TAC.

Environment

• Talend Administration Center 
• Talend Studio 

Erlang/Open Telecom Platform (OTP) has disclosed a critical security vulnerability: CVE-2025-32433.

Is Qlik NPrinting affected by CVE-2025-32433?

Resolution

Qlik NPrinting installs Erlang OTP as part of the RabbitMQ installation, which is essential to the correct functioning of the Qlik NPrinting services.

RabbitMQ does not use SSH, meaning the workaround documented in Unauthenticated Remote Code Execution in Erlang/OTP SSH is already applied. Consequently, Qlik NPrinting remains unaffected by CVE-2025-32433.

All future Qlik NPrinting versions from the 20th of May 2025 and onwards will include patched versions of OTP and fully address this vulnerability.

Environment

• Qlik NPrinting

Monthly monitoring of the data volume used in Qlik Cloud (Data for Analysis) is essential when using a capacity-based subscription.

This data is accessible in the Qlik Cloud Administration Center Home section:

For an overview of how the Data for Analysis is calculated, see Understanding the subscription value meters | Data for Analysis; its calculation considers the size of all resources on each day, and the day with the maximum size is treated as the high-water mark, which is then used for billing purposes. 

However, you may sometimes notice that the usage does not decrease as expected, even after reducing your app data. In such cases, it is recommended to review unused or rarely reloaded apps, as the previous app reload size may still be used for the calculation.

Resolution

To review the detailed usage, you can use a Consumption Report.

1. Distribute a consumption report; see Distributing detailed consumption reports | help.qlik.com for details on how to achieve this.
2. Review your data usage on the Data for Analysis sheet.
3. If you observe unexpected usage in apps, such as apps with reload infrequently, the is possible that the size is carried over from the previous reload.

To prevent the previous reload size from being carried over into the following month in similar use cases (specifically for apps that are not actively in use), a possible workaround is to reload apps using small dummy data to update the previous reload size of the apps.

Note that while offloading QVD files to, for example, S3 incurs no cost, any subsequent reload of those QVDs into Qlik Cloud will be counted toward Data for Analysis. Users should carefully evaluate whether this approach is beneficial.

Cause

Example case:

1. Extract external data into an app during reload.
2. Store the data as QVD files, and save the files outside Qlik Cloud (such as AWS S3).
3. Drop the source tables from the data model at the end of the script.
4. Reload completes; the final data model contains no tables.

The app is reloaded only once a month (or even less frequently) for the purpose of creating QVD files. At the end of the script, all tables are dropped, and the final app size is empty.

In this scenario, the usage of Data for Analysis won't be reset in the following month since it takes into consideration the size of loading the app. Therefore, the loading size continues to be charged in the next month as a previous reload.

Environment

• Qlik Cloud Analytics

Related Content

Qlik Cloud Analyticsの キャパシティ容量の仕様に関する解説(Explanation of Qlik Cloud Analytics capacity specification) 

Click here for Video Transcript

The Qlik Sense Virtual Proxy has two different authentication options by default: Forms and Windows Authentication. The Windows Authentication Pattern setting determines which one is used. 

The setting is accessed through the Qlik Sense Management Console > Virtual Proxies > [Virtual Proxy] > Authentication

See Figure 1:

When a client connects to Qlik Sense, the browser sends a User-Agent string to as part of the standard connection process.

The Qlik Sense Proxy service reads this string and checks for the presence of the value found in Windows Authentication Pattern. If the string is present windows authentication is used and if the browser supports NTLM the user may be automatically logged in. If the automatic login fails they will get a pop-up asking for username and password.

If the Windows Authentication Pattern value is not found then we fall back to forms authentication where instead we use a form and always require a username and password for login.

The default value for Windows Authentication Pattern is "Windows", which is present in all windows browser user-agent strings. If you change it to say Chrome or Firefox instead only those browsers will be offered Windows authentication. If you want to use Windows Authentication on all browsers try setting it to another string found in all user-agents (besides Windows), for example, "Mozilla".

Related Content:

• Integrated Windows Authentication (IWA) with Qlik using Internet Explorer, Chrome and Firefox 
• Logging out of Qlik Sense: Using Forms authentication to log in and out of the Sense Hub 
• Qlik Sense Enterprise on Windows Default Authentication Module 
• Qlik Sense and Authentication

When using SAML or ticket authentication in Qlik Sense, some users belonging to a big number of groups see the error 431 Request header fields too large on the hub and cannot proceed further.

Resolution

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.

The default setting will still be a header size of 8192 bytes. The fix adds support for a configurable MaxHttpHeaderSize.

Steps:

1. To configure add it at the top section of the file under [globals] (C:\Program Files\Qlik\Sense\ServiceDispatcher\service.conf)

   [globals]
   LogPath="${ALLUSERSPROFILE}\Qlik\Sense\Log"
   (...)
   MaxHttpHeaderSize=16384

2. Once the change is done, save the file and restart the Qlik Service Dispatcher service.

Note: The above value (16384) is an example. You may need to put more depending on the total number of characters of all the AD groups to which the user belongs. The max value is 65534.

Environment:

Qlik Sense Enterprise on Windows 

If Qlik NPrinting tasks do not complete and will only continue if the operating system is restarted, review the Qlik NPrinting log files for the following error:

io: read/write on closed pipe

This error indicates the Windows Operating System is damaged (after a faulty restart, a failed upgrade, or similar root causes).  

Resolution

Reinstalling Qlik NPrinting will not be sufficient to resolve the error. The Operating System will need to be reinstalled. 

Example solution:

1. Take a backup of your Qlik NPrinting database; see Backup and restore Qlik NPrinting for details.
2. Store the backup in a location off the current server
3. Reinstall Windows
4. Restore your Qlik NPrinting database; see Backup and restore Qlik NPrinting for details.

Environment

• Qlik NPrinting

To decrypt the Qlik Talend Data Integration (QCDI) verbose task log files:

1. Open the Qlik Talend Data Integration Project in the Web UI
2. Navigate to your project in the Qlik Talend Data Integration (formerly QCDI) browser interface
3. Locate the Task Name
   1. Go to the Tasks tab
   2. Click on the ... (ellipsis) button next to the relevant task
   3. Select View task logs
      
      
      
      
   4. Identify the unique task name (example: TASK_aRBItFnknSU0vR5LX0AgkA)
      
      
      
      
4. SSH into the Linux Gateway machine using the qlik user and log in
5. Navigate to the movement/bin Directory:
   cd /opt/qlik/gateway/movement/bin
6. Source the Qlik Talend Data Integration environment:
   source arep_login.sh
7. Decrypt the Task Log File by running the repctl dumplog command:

   repctl dumplog "/opt/qlik/gateway/movement/data/logs/TASK_aRBItFnknSU0vR5LX0AgkA.log" log_key="/opt/qlik/gateway/movement/data/tasks/TASK_aRBItFnknSU0vR5LX0AgkA/log.key" > "/opt/qlik/gateway/movement/data/logs/TASK_aRBItFnknSU0vR5LX0AgkA_Decrypted.log"

   In the example command, replace TASK_aRBItFnknSU0vR5LX0AgkA with your actual task name.
   
   
8. (Optional) Compress and download the decrypted Logs
   
   To bundle and download the decrypted logs:

   tar -czf decryptedLogs.tar.gz TASK_aRBItFnknSU0vR5LX0AgkA_Decrypted.log reptask_TASK_aRBItFnknSU0vR5LX0AgkA__250806061702_Decrypted.log

   Then, download decryptedLogs.tar.gz from the Linux gateway and send it to Qlik Support.

Related Content

How to Decrypt Qlik Replicate Verbose Task Log Files

Environment

• Qlik Talend Data Integration (QCDI)

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

• Requirements
• Using the Log Collector
• What does the Qlik Sense Log Collector access?
• Manually collecting log files
• Older Qlik Sense Versions (3.1 and earlier)

Requirements

The user must be a root admin and have administrative permissions.

Using the Log Collector

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. 

1. Login to Windows Server on Qlik Sense node
2. Open Windows File Explorer
3. Navigate to Log Collector folder at C:\Program Files\Qlik\Sense\Tools\QlikSenseLogCollector
4. Press Shift key and right click on QlikSenseLogCollector.exe 
5. Select Run as different user
6. Enter Qlik Sense service account credentials.
7. Configure log collection
   • Date range to collect logs from (minimum of 5 days if possible)
   • Support case number to include in ZIP file name
   • Select options 
   • Include Archive logs
8. Click Collect
9. If Qlik Sense is not automatically accessible on the node, further options are presented.  
   • Qlik Sense is running and on this host
     this option to get more options on automatic log collection
   • Qlik Sense is not running or accessible
     this option allows to define the path to local Qlik Sense log folder
   • Qlik Sense is located elsewhere
     this option allows to enter FQDN of remote Qlik Sense server
10. Wait until collection is finished
11. Click Close
12. Open generated ZIP file in C:\Program Files\Qlik\Sense\Tools\QlikSenseLogCollector
    Note, no need to unzip the file, simple double click on the ZIP file to browse its content
    • Confirm it contains JSON and TXT files, if system info options were enabled in Step 6
    • Confirm there is one folder per node in the deployment, named in same way as the node
    • Confirm there is a Log folder representing Archived Logs from persistent storage
13. If ZIP content is incomplete, repeat steps above or contact support for further guidance
14. If ZIP content is accurate, attach ZIP file to support case for further analysis by Qlik

What does the Qlik Sense Log Collector access?

This list provides an overview of what system information the Qlik Sense Log collector accesses and collects.

• WhoAmI (information)

  C:\Windows\System32\whoami.exe

• Port status (information)

  C:\Windows\System32\netstat.exe -anob

• Process Info (information)

  C:\Windows\System32\tasklist.exe /v

• Firewall Info (information)

  C:\Windows\System32\netsh.exe advfirewall show allprofiles

• Network Info (information)

   C:\Windows\System32\ipconfig.exe /all

• IIS Status (iisreset /STATUS Display the status of all Internet services.)

   C:\Windows\System32\iisreset.exe /status

• Proxy Activated (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "ProxyEnable"

• Proxy Server (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "proxyserver" 

• Proxy AutoConfig (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "AutoConfigURL" 

• Proxy Override (information)

   C:\Windows\System32\reg.exe query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings" | find /i "ProxyOverride" 

• Internet Connection (information)

   C:\Windows\System32\ping.exe google.com

• Drive Mappings (information)

   C:\Windows\System32\net.exe use

• Drive Info (information)

   C:\Windows\System32\wbem\wmic.exe /OUTPUT:STDOUT logicaldisk get size

• Localgroup Administrators (information)

   C:\Windows\System32\net.exe localgroup "Administrators"

• Localgroup Sense Service Users (information)

   C:\Windows\System32\net.exe localgroup "Qlik Sense Service Users"

• Localgroup Performance Monitor Users (information)

   C:\Windows\System32\net.exe localgroup "Performance Monitor users"

• Localgroup Qv Administrators (information)

   C:\Windows\System32\net.exe localgroup "QlikView Administrators"

• Localgroup Qv Api (information)

   C:\Windows\System32\net.exe localgroup "QlikView Management API"

• System Information (information)

   C:\Windows\System32\systeminfo.exe

• Program List (information)

   C:\Windows\System32\wbem\wmic.exe /OUTPUT:STDOUT product get name

• Service List (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "gwmi win32_service | select Started

• Group Policy (information)

  C:\Windows\System32\gpresult.exe /z

• Local Policies - User Rights Assignment (information)

   C:\Windows\System32\secedit.exe /export /areas USER_RIGHTS /cfg

• Local Policies - Security Options (information)

   C:\Windows\System32\secedit.exe /export /areas

• Certificate - Current User(Personal) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\currentuser\my | Format-list"

• Certificate - Current User(Trusted Root) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\currentuser\Root | Format-list"

• Certificate - Local Computer(Personal) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\localmachine\my | Format-list"

• Certificate - Local Computer(Trusted Root) (information)

   C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -command "Get-ChildItem -Recurse Cert:\localmachine\Root | Format-list"

• HotFixes (information)

  $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

• UrlAclList (information)

   C:\Windows\System32\netsh.exe http show urlacl

• PortCertList (information)

   C:\Windows\System32\netsh.exe http show sslcert

Manually collecting log files

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.

• Default storage (before archiving): C:\ProgramData\Qlik\Sense\Log
• Default archive storage: C:\ProgramData\Qlik\Sense\Repository\Archived Logs
• Manual retrieval of Reload logs: How to find the Script (Reload) logs in Qlik Sense Enterprise

For information on when logs are archived, see How logging works in Qlik Sense Enterprise on Windows.

Older Qlik Sense Versions (3.1 and earlier)

Persistence Mechanism Current Logs(Active Logs) 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.

Related Content

How logging works in Qlik Sense Enterprise on Windows