Is it possible to load Shape (SHP) files into Qlik using Qlik GeoAnalytics and if so is any conversion required?

Environment:

Qlik Sense Enterprise on Windows, all versions
Qlik GeoAnalytics / GeoAnalytics+ , all versions
 

Resolution

Shape (SHP) files can either be loaded from a local file using Qlik GeoAnalytic+ or through an URL using Qlik GeoAnalytics Connector.
 

Prerequisites

• A shapefile (see attached for example) in zipped format containing the .shp, file
• Qlik GeoAnalytics Plus installed

Example Qlik Sense

1. Copy the zipped shapefile attached to this article to any location (C:\tmp\CHE_Adm3.zip in this example)

Make sure the downloaded zip file is unblocked and accessible to the service account (if running Qlik Sense Enterprise)
 

 

2. Launch Qlik Sense, select Create new app and name the app. Press Create and Open app

3. Go to Data load editor and Create new connection

4. Select Qlik GeoAnalytics Connector

5. In the drop-down make sure to select GeoAnalytics Plus and give the connection a meaningful name

6. Press Test Connection to verify the connection and then Save

7. Press Select data 

 8. Set the following:

• Operation: Simplify (in this example the geometry will be simplified during load)
• Resolution: Auto
• Name: Myshape
• Type: File based geo dataset
• URL: file:///<path to zip file> (in this example, file:///c:\tmp\CHE_Adm3.zip)
• File Type: ESRI shape file
• CRS: EPSG:4326* (this can be found by loading the shapefile into QGis or similar tools)

 9. Press Next, and in the Select data to load check the tables Dataset_simplified as well as Dataset 

10. Press Insert script to insert the script into the Data load editor

11. Press Load data to fetch the data into the data model

12. Once data has been loaded into the data model, create a new GeoAnalytics Map object and a GeoAnalytics Area Layer in a new sheet

13. Click Add dimension on the GeoAlaytics Area Layer and select the field Dataset_Simplified_Geometry 

14. Verify the shapefile is shown correctly on the map

Note that there may be occasional issues with SHP file quality and the use of differing Coordinates Reference Systems.
 

This article explains a workaround to schedule automations between specific hours & days of the week. This workaround can be used until a native solution is delivered.

Getting started

1. Download the attached automation file and import it in a blank automation workspace.
2. Configure the timezone in the first variable block. 
   
3. Update the first condition block to set the latest time (hour) & day of week for which you want the automation to run. The hour should be in 24h format and day in a 1 (Monday) to 7 (Sunday) format. For example 5pm on a Friday would be 17 (hour) & 5 (day).
   
4. Configure the Schedule Start and Time Interval parameters on the first Update Automation Schedule block. For Schedule Start you should only edit the time parameter, no changes are required to the date formula.
   
5. Update the second condition block to set the earliest and latest time (hour) which you want the automation to run on business days. The hours should be in 24h format. For example 9am to 5pm would be 9 to 17.
   
6. Now configure the other Update Automation Schedule blocks in a similar way as step 4. But do not edit the Schedule Start parameter on middle Update Automation Schedule block as this will follow the automation's scheduled interval.
   

    

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

Environment

• Qlik Cloud
• Qlik Application Automation

Over the next few weeks, many of us will take some time to recharge before heading into the New Year. Why not take some of that time to invest in yourself and explore some of the learning resources available to Talend Academy subscribers?

Got a few minutes? Watch a video!

Best Practices videos are a quick way to sharpen your Talend skills in between other activities. They take only a minute or two, but they distill expertise from Talend consultants to deliver a meaningful learning experience.

Find them by logging in to Talend Academy, clicking the Search Talend Academy tile, then selecting Best Practices from the menu.

If you're a Talend partner, log in to the Partner Academy, then click Browse Catalog and select Best Practices from the menu.

Investigate Talend 8

Get a head start on learning more about Talend 8 by spending time with these resources, now upgraded to reflect the new functionality.

Talend Cloud Administration Learning Plan

The learning plan was upgraded to a Talend 8.0 environment, and the Logging and monitoring in Talend Management Console module was updated to integrate the new logging interface. Personal access tokens are now used to connect from Talend Studio to Talend Cloud throughout the learning plan.

 

Talend Data Fabric Installation Foundations Learning Plan

This learning plan now includes a new video, Talend Studio Installation, covering how to maintain a Talend Studio installation in Talend 8 using the new Feature Manager, and explaining how to manage and apply patches.

 

Talend Cloud Hands-on Migration Advanced Use Case

This use case was upgraded to demonstrate migration from a 6.4 on-premises environment to an 8.0 Talend Cloud environment (instead of 7.3) after the release of Talend 8. 

 

Talend Cloud Administrator Professional Exam

This professional exam was upgraded to test participants on their ability to migrate from a 6.4 Talend environment to an 8.0 Talend Cloud environment after the release of Talend 8.

 

Earn a new badge

Sharpen your skills by taking advanced Talend Academy courses in a familiar topic, or by starting a learning plan that's new to you.

Read more about our badging program on the Talend Community — you will gather trophies along the way, and earn a badge that you can share with the world!

 

 

Prepare to get certified

To challenge yourself even further, get ready to pass a certification exam in the new year.

Talend Academy offers certification preparation courses that provide review materials and a practice test to validate your knowedge and increase your confidence in passing the exam. When you do, you'll be awarded a Certified badge.

 

 

Experienced Talend professional?

Even after you've completed courses and created Talend projects, Talend Academy has advanced resources to help you hone your skills and continue learning!

Implementation Accelerators

Talend experts create Implementation Accelerators based on their extensive experience out in the field. They develop tools, frameworks, and scripts that help you optimize tasks such as implementing CI/CD workflows, automating creation of data pipelines, and verifying and cleansing addresses.

Talend Academy's extensive collection of Solution Templates delivers software artifacts and Talend Jobs, as well as instructions for how to use them. You can extend and customize them to fit your own environment and requirements, ensuring that your projects follow Talend best practices.

Find them all by clicking the tile on your Talend Academy home page.

 

Advanced Use Cases

Talend experts also write advanced use cases that describe solutions to real-world scenarios that you might encounter in your own production environment or at a client's site. These solutions use several Talend products together to solve a complex problem, or show how to use Talend products with third-party software to achieve your goals.

This tile is available on your Talend Academy home page.

Loading files larger than 50MB from web storage connectors such Dropbox, Office 365SharePoint, SFTP, Amazon S3 and similar leads to: 

Data file size exceeded file streaming buffer size. Adjust the StreamingBufferSizeMB setting.

Environment

Qlik Sense Enterprise on Windows 
Qlik Cloud 

Resolution

Qlik Sense Enterprise on Windows (client-managed):

The solution requires us to modify the Qlik Sense Engine settings.ini. See How to modify Qlik Sense Engine settings.ini for details on the procedure.

1. Stop the Engine Server
2. Go to C:\ProgramData\Qlik\Sense\Engine
3. Create a backup of the Settings.ini 
4. Open the Settings.ini file
5. Add StreamingBufferSizeMB=1024 line  (higher values are not currently supported by connectors)
6. Add an empty line after the above parameter if the parameter is the last one to be added
7. Save
8. Restart the Engine Service

Qlik Cloud

The value cannot be configured in Qlik Cloud. A workaround is to split the big data files by e.g. months.

Internal Investigation ID(s) 

QLIK-83207
CP-4120
QLIK-82097

Qlik Data Gateway erroring out with "Invalid metadata response (DirectAccess-2201) " message. The error could be due to a different issues. 

Resolution

• Verify Privileges on the space where the Gateway was created and the Space where user is attempting to create the connection, our documentation describes the details  here
• If privileges are correct, try to restart Qlik Data Gateway services on the Server where it resides.
• Verify if the issue is specific to a connection, if one user was able to successfully create a connection, attempt to create a new connection with the user that is getting the error.
• If nobody is able to create a connection for an specific Data Source, attempt to configure a DSN ODBC connection from the Data Gateway Server to verify it succeeds. 

Cause

The cause of the issue is usually configuration, if the suggestions above didn't fix the issue it will be necessary to report the issue for further analysis. 

Related Content

Qlik Data Gateway: Direct Access Data Gateway failing with Internal Error 

Environment

• Qlik Cloud 
• Qlik Data Gateway 

After upgrading Tomcat from version 9 to version 10, you may encounter issues when starting the SSL-enabled Talend Administration Center, as it only supports Tomcat version 10.1 or higher, starting from patch TPS-5553.

Error: -SSLUtil - SSL Keystore path or password missing. Please check configuration.

Resolution

After upgrading to Tomcat 10, ensure that your server.xml file (server.xml file is under <TalendAdministrationCenter_HOME>/apache-tomcat/conf ) is updated to reflect the new and supported SSL attributes.

In Tomcat 10, as several attributes have been deprecated or removed entirely, there are differences that can be found like:

• keystoreFile⇒certificateKeystoreFile
• keystorePass⇒certificateKeystorePassword
• Change in format of the connector section using tags like<SSLHostConfig> 

By configuring the SSL connector with the correct and supported attributes, you should be able to resolve the issue of starting the SSL-enabled Talend Administration Center after upgrading to Tomcat 10.

For Example

SSL Connector with supported attributes configuration

<!-- Define an SSL Coyote HTTP/1.1 Connector on port 1234 -->
<Connector
   protocol="****"
   port="1234"
   maxThreads="150"
   SSLEnabled="true">
 <SSLHostConfig>
   <Certificate
     certificateKeystoreFile="****/.keystore"
     certificateKeystorePassword="****"
     type="RSA"
     />
   </SSLHostConfig>
</Connector>

======================================

Cause

Apache Tomcat version 10 introduced several breaking changes, including the deprecation and removal of certain SSL attributes in the server.xml file. As a result, SSL configurations that were functional in Tomcat 9 may no longer work correctly in Tomcat 10 without some necessary modifications.

Related Content

configure-tls-ssl-in-talend-administration-center

https://tomcat.apache.org/tomcat-10.0-doc/ssl-howto.html

Environment

Talend Administration Center

Port 443 is the outbound port used to connect Qlik DataTransfer to the Qlik Cloud tenant. This port cannot be customized.

Related Content

Configuring Qlik DataTransfer

Environment

• Qlik Cloud
• Qlik DataTransfer

Qlik Sense URL(s) tested on SSLlabs (ssllabs.com) return the following weak Cipher suites:

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 1024 bits FS WEAK
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK

The steps documented in this article are an example of how cipher suites can be disabled. All steps are to be performed by a Windows Administrator on Windows level and cannot be supported by Qlik Support. 

We recommend to consulting with your security or Windows administrator before proceeding as they may have automated practices in place. 

The security in Qlik Sense does not depend only on the Qlik Sense software. It also relies on the security of the environment that Qlik Sense operates in. This means that the security of, for example, the operating system and the cryptographic protocols (such as TLS/SSL) has to be set up and configured to provide the security needed for Qlik Sense. See Protecting the platform.

Configuring TLS Cipher Suite Order

You can review and configure the cipher suites order using a Group Policy. See Manage Transport Layer Security (TLS) | Microsoft Learn.

Please refer to fig 1:

Fig 1

This policy determines the cipher suites used by the Secure Socket Layer (SSL). If you enable the policy setting, SSL cipher suites are prioritized in the order specified.

If you disable or do not configure this policy setting, the factory default cipher suite order is used.

SSL2, SSL3, TLS 1.0 and TLS 1.1 cipher suites:

TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_MD5 SSL_CK_RC4_128_WITH_MD5 SSL_CK_DES_192_EDE3_CBC_WITH_MD5 TLS_RSA_WITH_NULL_SHA TLS_RSA_WITH_NULL_MD5

TLS 1.2 SHA256 and SHA384 cipher suites:

TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_NULL_SHA256 TLS 1.2 ECC GCM cipher suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521

How to modify this setting:

1. Open a blank notepad document.
2. Copy and paste the list of available suites into it.
3. Arrange the suites in the correct order; remove any suites you don't want to use.
4. Place a comma at the end of every suite name except the last. Make sure there are NO embedded spaces.
5. Remove all the line breaks so that the cipher suite names are on a single, long line.
6. Copy the cipher-suite line to the clipboard, then paste it into the edit box. The maximum length is 1023 characters.

Related Content:

Configuring preferred cipher suites for Qlik License Service in Qlik Sense Enterprise on Windows

Environment:

Qlik Sense Enterprise on Windows any version

This video will demonstrate how to install and configure Qlik-CLI for SaaS editions of Qlik Sense.

Content:

• Requirements
• Installation method One
• Installation Method Two
• Enable the Completion Feature (optional, but useful)
• Use Qlik-CLI
• Related Content
• Transcript

Requirements

• The user has access to a Qlik Cloud tenant
• The user has a professional license assigned in the tenant
• The user has the developer role assigned (required for API access)
• An API key can be obtained

Installation method One

1. Download Qlik-CLI from GitHub
2. Copy the executable to a local directory
3. Add the Qlik-CLI as an Environment Variable Path. 
   1. Open your Windows Control Panel
   2. Navigate to System 
   3. Open Advanced system settings in the leftmost menu
   4. Click Environment Variables 
   5. Locate Path in the User's System variables 
   6. Click Edit
   7. Click New
   8. Add the path to Qlik-CLI for example C:\Tools\Qlik-QLI\Modify the User Environment. Add path to Qlik-CLI. ie "C:\Tools\Qlik-QLI\"
   9. Confirm with OK until all windows are closed
4. Confirm the Qlik-CLI location path to verify it the installation completed successfully 
   1. Open PowerShell
   2. Execute:
      

      get-command qlik​

   3. Closer PowerShell

Installation Method Two

1. Download and install Chocolatey as documented on chocolatey.org.
2. Open PowerShell
3. Execute:
   

   choco install qlik-cli

4. This completes the installation.

Enable the Completion Feature (optional, but useful)

1. Verify if a PowerShell profile exists or create a new one
   1. Open PowerShell
   2. Execute:
      

      if ( -not (Test-Path $PROFILE) ) {
         echo "" > $PROFILE
      }​

2. Open the profile with the command notepad $PROFILE:
   

   qlik completion ps > "./qlik_completion.ps1" # Create a file containing the powershell completion.
   . ./qlik_completion.ps1                      # Source the completion.​

3. Save it. 
4. Restart PowerShell

Use Qlik-CLI

Advanced and additional instructions as seen in the video can be found at Qlik-CLI on Qlik.Dev. Begin with Get Started.

Talend Administration Center Application is going to frozen state and unable to open/load the application from the browser until the services are restarted.

From the logs the error message displays as below:

INFO [Catalina-utility-1] org.apache.catalina.core.StandardContext.reload Reloading Context with name [/tac8] has started.
INFO [main] org.apache.catalina.core.StandardServer.await A valid shutdown command was received via the shutdown port. Stopping the Server instanceorg.apache.catalina.startup.HostConfig.deployDescriptor Deployment of deployment descriptor [/data/talend/tomcat/conf/Catalina/localhost/tac8.xml] has finished in [26,138] ms.

Resolution

In <TalendAdministrationCenterInstallation>\apache-tomcat-xx.x.xx\conf>tac8.xml（server.xml）file, need to change the parameter reloadable from "true" to "false" as given below.

From

<Context docBase="/data/talend/apps/tac8.war" reloadable="true" />

to

<Context docBase="/data/talend/apps/tac8.war" reloadable="false"/>

This configuration line in Talend Administration Center refers to the Tomcat configuration used by Talend Administration Center to define the deployment settings for the web application.

Please make sure to stop the services before doing any changes.

Cause 

This performance issue is probably caused by the configuration setting of parameter reloadable in Tomcat server.xml file. When it is set to true, Tomcat will monitor changes in class files and JAR files in the WEB-INF/classes and WEB-INF/lib directories. If there are updates, Tomcat will automatically reload the web application, which can be useful in development but frequent reloading may affect performance and make Talend Administration Center Application is going to frozen state.

Environment

Talend Administration Center

Qlik Replicate version 2024.5 has added support for partitioned tables in PostgreSQL database sources. Sub-partitions on these tables are not currently supported.

Resolution

This limitation could potentially be worked around by using the ODBC CDC source endpoint. ODBC endpoints must be implemented by our Professional Services team. To easily engage with our Professional Services team, contact your Account Manager. 

The feature is on Qlik's roadmap for 2025. Review upcoming Release Notes for details.

To track the current feature request's status, see Qlik's Ideation Portal. 

Name: Qlik Replicate for PG as a source RDS, CDC replication not supporting for Table sub-partition and cascaded partition.
ID: 448952
Link (requires previous login)

Cause

Design limitation.

Internal Investigation ID(s)

00318581

Environment

• Qlik Replicate 2024.5

A newly installed Qlik Data Gateway for Direct Access stays disconnected.

The log files read:

"System.Net.WebSockets.WebSocketException (0x80004005): Unable to connect to the remote server
---> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.
---> System.Security.Authentication.AuthenticationException: The remote certificate was rejected by the provided RemoteCertificateValidationCallback.
at System.Net.Security.SslStream.CompleteHandshake(SslAuthenticationOptions sslAuthenticationOptions)"

and

[Service] [DEBUG] Verifying root certificate with the CA bundle "C:\ProgramFiles\Qlik\ConnectorAgent\caBundle\qcg_ca_bundle.pem" 

Resolution

Remove the software and reinstall it without running the command “connectoragent qcs set_config --ca_bundle_path path-to-ca-bundle-file”

The CA Bundle is needed only in very specific scenarios, as specified in Setting the CA bundle (source, Qlik Help):

Who needs to set the CA bundle?

The CA bundle only needs to be set if you are:

• A Qlik Cloud Government customer
• A Qlik Cloud commercial customer using a security appliance that acts as a proxy and replaces the certificate information received from the Internet with its own CA root certificates

Configuring the bundle unnecessarily will result in connection failures.

If a CA Bundle is indeed needed, verify it is configured correctly.

Cause

Setting up a CA Bundle when not needed might break connections.

Environment

• Qlik Cloud Analytics
• Qlik Data Gateway

As a benefit of our Analytics Modernisation Program (AMP), a signed license key is issued as a unified license key. This enables the use of one license across Qlik Sense Enterprise on Windows and QlikView, granted the license has the required QlikView infrastructure attributes (QV_NODES for QVS, QDS_NODES for Publisher).

This allows for analyzer capacity to be shared across all systems using the same license.

Environment:

QlikView 
Qlik Sense Enterprise on Windows 
With a Signed License Key (SLK) applied as a unified license across multiple environments 

Here is an example;

A QlikView server currently shows 18 minutes of consumption in the QlikView Management Console (Fig 1.) 

This can be accessed through: System > Licenses > Professional and Analyzer access.

Fig 1

If a user accesses and consumes on a linked Qlik Sense Enterprise Server, the Qlik Sense Enterprise Management Console will show the up to date consumption. See Fig 2. Note the 24 minutes, an increase from the 18 we have seen in QlikView.

This can be accessed in the Qlik Sense Management Console > License Management > License usage summary

Fig 2

The usage on the server will be synchronized and shown on the other linked servers within approximately 10 minutes. See Fig 3 and note the 24 minutes, which matches the value in Qlik Sense.

Fig 3

For local consumption data, each server will store its own consumption and user information.   

For Qlik Sense Enterprise on Windows, the License Monitor app will show capacity consumption.

For the QlikView Server, the capacity consumption is shown and stored in the local session log file, with the CAL consumed being Analyzer Capacity, with a log entry like this:

RLS64 12.50.20200.0 20210412T132942.000+0200 20210412T133617.000+0200 C:/ProgramData/QlikTech/Documents/retail store performance.qvw 20190220T113522.000+0200 Socket closed by client 20210412T133601.000+0200 00:00:16 0.000000 10228 1303493 31 2 QTSEL\ghd 1718e2e6-5b1c-4b9e-87a9-d9200f55e37a Ajax QvWS 12.50.20200.0 browser.msie illa/5.0 (windows nt 10.0 On 4747 fe80::df3:cd38:b86f:50bd 58495 Analyzer Capacity 6 315dcfab-7448-4f4b-8209-ef34742b1abe

Many reloads are failing on different schedulers with General Script Error in statement handling. The issue is intermittent.
The connection to the data source goes through our Qlik ODBC connectors.

The Script Execution log shows a  “General Script Error in statement handling” message. Nevertheless, the same execution works if restarted after some time without modifying the script that looks correct.

The engine logs show:

CGenericConnection: ConnectNamedPipe(\\.\pipe\data_92df2738fd3c0b01ac1255f255602e9c16830039.pip) set error code 232

Environment

• Qlik Sense Enterprise on Windows May 2021
• Qlik Sense Enterprise on Windows September 2020 and higher (less frequent occurrence) 

Resolution

Change the reading strategy within the current connector:

Set reading-strategy value=engine in C:\ProgramFiles\Common Files\Qlik\CustomData\QvOdbcConnectorPackage\QvODBCConnectorPackage.exe.config

reading-strategy value=connector should be removed

Switching the strategy to engine may impact NON SELECT queries. See Connector reply error: Executing non-SELECT queries is disabled. Please contact your system administrator to enable it.  for details.

Internal Investigation ID(s):

QB-8346

The TAC configuration page's Artifact section displays an error for JFrog access check：

error unauthorized : https://<JFROG_PLATFORM_URL>:<PORT>/access/api/v1/system/ping

Cause

$ curl -u "admin:password" "https://<JFROG_PLATFORM_URL>:<PORT>/access/api/v1/system/ping"
{
"errors" : [ {
"code" : "UNAUTHORIZED",
"message" : "Unsupported authentication method Basic"
} ]
}

Resolution

For every Access-related API, you must use an admin-scoped Access Token or an Admin Identity Token. For further details, please refer to How to generate access token from JFrog admin UI.

Environment

• Talend Administration Center 8.0.1

Talend Management Console plan is triggered and keeps on "Running" status, but the task shows "Successful" in the status.

Resolution

Need to manually terminate the plan from the screen to check whether it will solve the issue.

Cause 

It may be a bug in the user interface (UI) of the Talend Management Console that Plan might be in an inconsistent status.

Environment

Talend Cloud 

The Qlik NPrinting Designer (February 2024 IR to SR2) may fail to start. The error thrown is:

HTTP Call Error Sending Request

Resolution

This is a known defect (QB-30815) and is actively being investigated. A permanent fix is planned for a future patch of the February 2024 release.

Workaround

This workaround is applied to the Qlik NPrinting Server's webengine.config.

1. Stop all Qlik NPrinting services
2. Navigate to: C:\Program Files\NPrintingServer\NPrinting\WebEngine\
3. Open the webengine.config as Administrator
4. Uncomment the include-user-filters key:
   
   From:

   <!-- <add key="include-user-filters" /> -->

   
   To:
   

   <add key="include-user-filters" />

5. Save the file
6. Restart the Qlik NPrinting services

Cause

Too many user filters.

Internal Investigation ID(s)

QB-30815

Environment

• Qlik NPrinting February 2024 IR to SR2

It is recommended to enable HTTPS for Qlik GeoAnalytics Server. This can be done either during the installation or by editing the config.ini after the installation.  

The deployed SSL certificate may need to be updated regularly, which requires a repeat of the initial installation steps. 

Environment: 

Resolution:

Before you begin

• Make sure you have a certificate in PKCS12 (.pfx, p12) format, including the private key! This can be exported out from Windows Certificate Manager, Qlik Sense Management Console (if using self-signed certificates generated by Qlik Sense) or acquired by your certificate authority
• Make sure the certificate matches the hostname where Qlik GeoAnalytics Server is installed, (example: myserver.domain.local ) 
• Place the certificate where it can be accessed by Qlik GeoAnalytics Server

Set / Change certificate during install

The recommended way to enable HTTPS is to run the installation package and set/change the certificate during install. Setting the certificate during install will automatically obfuscate the password stored in config.ini.

1. Launch the Installer
2. On the second step of Server Settings (Basic) enable HTTPS and browse to the desired certificate. See fig 1.
   
   Fig 1
   
   
3. Proceed with the installation. 

Alternative way to enable HTTPS on an already installed Qlik GeoAnalytics Server

1. Edit config.ini found in %ProgramData%\Qlik GeoAnalytics Server and add the following to the [SSL] section, replacing details to match your environment:
   

   [SSL]
   sslEnabled=true
   sslPort=443
   sslKeystore=c:\\path_to_certificate\\certificate_filename.pfx
   sslPassword=certificate_password​

2. While encryption of passwords is required in later versions, it should still be possible to use clear text password in the ini. However, it's recommended to re-run the installation program to set the parameters and then the password will be obfuscated like enc:0B0115327474.
   
   All obfuscated passwords should start with enc:
   
   
3. Open Qlik GeoAnalytics Configure Service console and restart the service
4. Verify HTTPS working properly.
5. Any errors/warnings about the certificate not being valid, such as missing Subject Alternative Name, issues with the certificate chain etc may result in errors when using the server and needs to be investigated and fixed.

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.