You can access Qlik Sense demo apps from https://demos.qlik.com/.

If you are looking for real-life business examples, our Qlik Gallery hosts a platform meant for sharing apps, outcomes, and ideas. It is not restricted to Qlik-provided demos and mostly consists of customer examples.

If you are looking to download demo apps:

1. Go to https://demos.qlik.com/ 
2. Select Downloadable from the available Tags
   
3. Open the App
4. A Download button will be available (if logged in)
   
   

There are problems occurring related to notifications, for example, the notifications are not being sent to E-mail.

Resolution

1. Check that the E-mail Address is correct
   1. Click on "Profile Preferences"
   2. Click on "About Me"
   3. Check if the email address is correct
2. Check that the event you want to trigger is selected
   1. Click on "Profile Preferences"
   2. Click on "Notifications"
   3. Select the application that you want notifications to be sent
   4. Click on the arrow next to the application to show a drop-down list
   5. Choose the event that will trigger notifications to be sent to the E-mail
3. Check that you have the right permissions to receive notifications  
   1. Click on "Users & Security"
   2. Click on "Roles"
   3. Click on "Role details"
   4. Click on the "Permissions" tab
   5. Check that you have the right permissions by referring to: Talend Management Console email notifications
4. Check that the user has workspace permissions
   1. Click on "Environments"
   2. Click on the "Workspace permissions" tab
   3. Select the workspace
   4. Click on the "Add permissions" button
   5. Select the user permission from the drop down list
5. Check if the problem occurs only on a specific E-mail Address(check if other E-mail Addresses can receive notifications)
6. Please check the following URLs for further details and step by step guidance on E-mail notifications
   • Enabling email notifications
   • Configuring individual email notifications

Cause 

1. The settings to receive notifications may not be set properly
2. No permissions to the workspace where you would like notifications from
3. The E-mail Address is not correct
4. Personal configurations made for the E-mail do not receive notifications (for example: blocking certain sender's E-mail)

Environment

Talend Cloud 

When using Kafka as a target in a Qlik Replicate task, the "Control Table" name in target is created in lower case, for example the Apply Exception topic name is "attrep_apply_exceptions"  (if auto.create.topics.enable=true is set in Kafka broker config/server.properties file), This is the default behavior. 

In some scenarios, you may want to use the non-default topic name or topic name in upper case etc to match the organization naming standards rule. This article describes how to rename control table topics' name.

In this article, we will use the topic name "attrep_apply_exceptions" as an example. You can customize below control topics using the same process:

• attrep_apply_exceptions
• attrep_status
• attrep_suspended_tables
• attrep_history

The same way works for more generic level , not only for Kafka target endpoint. In generic level we may rename other metadata eg "target_schema" too.

Resolution

1. Export the JSON of the task
   
    
   
2. Position to the line of the JSON file and identify the element "exception_table_settings"  (usually is empty, as below):
   
   "exception_table_settings": {
   },
3. Override the element to add the table_name attribute and SAVE the changes:
   
   "exception_table_settings": {
   "table_name": "CUSTOM_NAME_ATTREP_APPLY_EXCEPTIONS_TABLE"
   },
   
   In above sample, we rename the topic  exception_table_settings  name to CUSTOM_NAME_ATTREP_APPLY_EXCEPTIONS_TABLE (it's case sensitive, and in upper case).
   

   Kafka topic names cannot exceed 255 characters (249 from Kafka 0.10) and can only contain the following characters:

   a-z|A-Z|0-9|. (dot)|_(underscore)|-(minus) 

   More detailed information can be found at Limitations and considerations.

   The safest topic name length is 209 (rather than 255/249).

4. Import the JSON of the task
   
   After the import, The topic name shows in GUI is default name still, however the new topics name takes action, the task can be edited by using GUI freely until change the control topics name again by above steps.
5. Run the task.

Environment

Qlik Replicate  (versions 2022.11, 2023.5 and above)
Kafka target

Related Content:

         case #00010983, #00108779

Generate a record to attrep_apply_exceptions topic for Kafka endpoint

This document explains how to manually setup custom connectors within Qlik Sense with Standard mode without legacy mode. More info under Legacy vs. Standard Mode in Qlik Sense: Explainer and Security Considerations 

Pre-requisites:

• QlikView Desktop Client where SAP Connectors has been installed
• Qlik Sense Server installed and working perfectly
• Granted permission to copy files

After installing Qlik SAP Connectors on a Qlik Sense Enterprise Server, some connectors like Qlik SAP Report Connector, Qlik SAP Query Connector..., are not automatically installed. Thus, when migrating from a "QlikView environment" to "Qlik Sense Enterprise", those specific connectors need to be manually set in Qlik Sense.

Step 1:

1. Login to Qlik Sense Hub
2. Create a new app
   
   
   
   
3. Name the Application, then click Create button
   
   
   
   
4. Click Open app button
   
   
   
   
5. Click on Data load editor
   
   
6. Click on Create new connection button 
   
   
   
   
7. Click on OLE DB
   
   
   
   
8. Select OLE DB Provider for Microsoft Directory Service
   
   
   
   
9. Named the Data source as for example Dummy DataSource Connection. Choose the default selection, Specific user name and password
   
   
   
   
10. Put a name for the Connection, for instance, SAP Connection
    
    
    
    
11. Click Test connection button. Test must be successful similar to screenshot below
    
    
    
    

After successful connection, click Create button

Step 2: 

1. Open QlikView Desktop Client
2. Generate a connection string for this example QvSAPQueryConnector
3. CUSTOM CONNECT TO "Provider=QvSAPQueryConnector.dll;ASHOST=10.76.162.44;SYSNR=00;CLIENT=800;XUserId=xxxxxxxxxxxxx;XPassword=xxxxxxxxxxx;";

Step 3: 

1. Login to Qlik Sense Management Console (QMC)
2. Click on Data connections
   
   
   
   
3. Select SAP Connection, press Edit button found at the bottom left of the window
   
   
   
   
4. Remove the entry on the Connection string
   
   
   
   
5. Edit the generated connection string from QlikView Desktop
6. Remove the XUserID and XPassword parameter on the connection string

It should look like:

Step 4: 

• In the QMC, now paste the revised connection string to the Connection string field

• Provide the SAP user credential (UserID / Password), then click Apply button
  
  

Step 4:

• Login or go back to the document created earlier in the Qlik Sense Hub
• Click on Insert Script from Data connections (left corner of the Editor Script Window)
  
  
  
  
• Then, finally copy and paste the Load script generated in QlikView  Desktop to the Qlik Sense Editor window. Note that, in this scenario, you need to copy scripts from QlikView and not generate scripts using Qlik sense editor/select data.
  
  
  
  
• Save the application and press the Load data button
  
  

Optional Steps:

With the latest versions of QlikView and Qlik SAP Connector,  you don't  need to perform this step.

• Login to the machine which has QlikView Desktop Client
• Copy all the folders (by default) under C:\Program Files\Common Files\QlikTech\Custom Data\

• Login to the Qlik Sense server
• Copy over the folders earlier (by default) to C:\Program Files\Common Files\Qlik\Custom Data

• Restart all Qlik Sense services

After upgrading to Talend 8.0.1, we are facing an issue when using phoenix-client-hbase-2.4-5.1.1.7.1.9.6-3.jar to connect to the Phoenix HBase by using JDBC.

This error is being thrown while trying to establish a connection

org.apache.phoenix.query.GuidePostsCacheProvider - Could not load/instantiate class org.apache.phoenix.query.DefaultGuidePostsCacheFactory

Searched for the phoenix-hbase-client jar file and the required classes are present in folder without missing jar issue.
 

Resolution

This issue has been fixed from CDP side.

You need to apply for CDP patch fix and update Cloudera CDP version to 7.1.9 with hot-fix jars. 

Cause

It is a known bug from upstream

https://issues.apache.org/jira/browse/PHOENIX-7290.

https://github.com/apache/phoenix/pull/1873/commits/78165aa4601ee49e572c3f75e99be7c7506737aa

Internal Investigation ID(s)

Internal Jira Case: TBD-16676

Environment

Talend Big Data 

How to get started with R-Script integration within Qlik Sense

The architecture of the integration at a High-level looks like this:



 

Qlik Sense Advanced Analytics integration is essentially an extension to Qlik Sense’s expression syntax, and as such it can be used in both Chart Expressions, and in Load Script Expressions.
 

With this new capability, we are now able to add syntax to a chart expression that tells Qlik Sense that particular expression should not be evaluated on the Qlik Sense server, but instead, all the information and data needed to calculate that expression should be sent via the server side extension on to the backend R system for calculation.

 After the advanced analytic calculations are completed, the data is sent back to the Qlik Sense Server and to the client for visualization.

Environment:

• Qlik Sense Enterprise on Windows , all versions

Resolution:

This video shows an example of how Qlik Sense connects to an R server for extending expression capabilities in Qlik Sense Apps while offloading the calculations to the R server engine.

Click here for Video Transcript

In order to start displaying a simple "Hello World" in Qlik Sense using a R-Script, we will do the following:

1. Have R & R-studio installed in your system. (RGui included with R for Windows can also be used) R can be downloaded at https://cloud.r-project.org/

2. We need a package in R to extend R functionality to applications via TCP/IP. The package name is "Rserve()"
Install the package using the below command in RStudio GUI:

install.packages('Rserve')

3. Now we need to invoke that library and start Rserve. In order to do so, execute the below scripts:

library(Rserve)
Rserve()

4.The communication method from Sense to R is taken care using gRPC. R is not a supported language in gRPC by default.

So a possible solution for this is to develop a connector in any of the supported languages of gRPC. Qlik provides an open-source connector developed in C# which in turn access Rserve to be able to run R scripts.
qlik-oss/sse-r-plugin
Once you built the connector,  start the SSEtoRserve.exe (ideally on the Rserve server itself)

Note: Qlik Support does not support this plugin directly. Inquiries should be submitted via GitHub under sse-r-plugin - Issues

5. Now we will have to configure the plugin:

For Qlik Sense Desktop June 2019 and up:

Add the following line in the settings.ini file:

SSEPlugin=R,localhost:50051

The settings.ini is located in this location: 

For previous Qlik Sense Desktop:

Add the following line in the settings.ini file:

SSEPlugin=R,localhost:50051

The settings.ini file is located in this location:

For Qlik Sense Enterprise/Server:

a. In the QMC, add a new Analytic Connection.
b. Restart the Qlik Sense Engine service.

Please refer to the screenshot below for creating a new connection.

Note: If the R-Plugin (SSEtoRserve.exe) was installed on the R-Server (where Rserve runs) or another machine, point to that machine name instead of 'localhost'. Also, in multi-node environments with multiple Qlik Sense Engines, even if the plugin was installed on the Central node, make sure to add the Central node's hostname instead of 'localhost' as the other Rim node Engine services need the correct DNS/Netbios name to reach the plugin.



6. Now Open a Qlik Sense App and add a KPI object in the sheet. This can be one of the Apps included with the  plugin itself under <storage path>\sse-r-plugin-master\sense_apps

Note that the example apps also need data connections to be created to the data files included with these apps files in the above location.

7. Otherwise, a new app can be created and any data may be loaded for the SSE example below.

8. For the measure, add the following expression which contains an R-script:

R.ScriptEvalStr('paste(q$firstWord, q$secondWord);', 'Hello' as firstWord, 'World' as secondWord)

9. If everything is configured properly, the R-script shown in bold above should be executed fine and it should display a "Hello World" message.

Understanding the R-script & Function:

R.ScriptEvalStr('paste(q$firstWord, q$secondWord);', Only([First Word]) as firstWord, Only([Second Word]) as secondWord)

Eight script functions are automatically added to the functionality of the plugin. What is needed to be covered on the plugin side to fulfill the functionality is to implement the EvaluateScript rpc function.

The syntax of these functions is: 

<EngineSSEName>.<FunctionName>(Script [,Parameter...])

Where the Script is an R-Script to be evaluated & Parameter is the data sent from Qlik's end.

Here, we use the ScriptEvalStr function which accepts argument of type String & returns a String. The 'paste' function in R concatenates vectors after converting to character. We pass two data fields of type string from Qlik (First Word & Second Word). The R-script then references these data fields through the q dataframe (structure already taken care in R) (q$firstWord and q$secondWord). The script/function finally returns a String back to Qlik Sense.

Related Content:

• Analytic Connections - Qlik Sense for Administrators 
• Script Regular Statements - Load - Qlik Sense on Windows 
• Creating an Advanced Analytics Server in 15 minutes using AWS 
• Qlik Server-Side Extension (SSE) with Analytic Connections 
• Getting Started with Advanced Analytics in Qlik Sense using Python 
• How to call an external / custom function in Qlik Sense? 
• Qlik Sense Analytic Connection (SSE) Error when reloading App 
  
  
   

When a user is deleted, any spaces, apps, scripts, and data connections they own will remain in the tenant without an owner. To prevent orphaned records, reassign ownership of these assets before deleting the user. Source: Reassigning ownership of spaces and resources (Qlik Cloud Documentation)

But even if the app is considered an Orphaned App, the owner can be changed in the Qlik Cloud Analytics Administration Console:

1. Open Qlik Cloud and open the menu
2. Access the Administration menu
3. Go to Content
   
   
   
   
4. Select the Apps tab
   
   
5. Filter by Deleted User in the Owner column
   
   
   
   Apps owned by Deleted Users will be listed.
   
   
6. Click the ... (ellipses) menu
   
   
   
   
7. Select Change Owner and change the ownership of the app

Environment

• Qlik Cloud Analytics

The Qlik Sense Engine allows for a Hard Max Limit to be set on memory consumption. 

To be able to enforce "Hard max limit" the engine requires access to a specific endpoint in the Windows operating system API.

If the operating system blocks calls to this endpoint, then an attempt to use the configuration "Hard max limit" will fail, and the engine will instead operate according to the "Soft max limit" configuration.

Refer to the documentation provided by Microsoft fur forther information: "SetProcessWorkingSetSizeEx"

How to review your memory settings in Qlik Sense or configure the Hard Max Limit:

1. Open the Qlik Sense Management Console in a supported browser
2. Navigate to Engines in the Management Console and select your engine
   
   
   
   
3. Expand the Advanced settings from the menu to the right
   
   
   
   
4. Review your memory settings and verify that Max Max Limit is selected
   
   

See Editing an engine - Qlik Sense for administrators for details.

To note:

Even with the hard limit set, it may still be possible for the host operating system to report memory spikes above the Max memory usage (%).

This is down to how the Qlik Sense Engine memory limit will be defined based on the total memory available.

Example:

• A server has 10 GB of memory in total, and the Max memory usage (%) is set to 90%.
• This will allow the process engine.exe to use 9 GB of memory. 
• Another application or process may at that point already be consuming 5 GB memory, and this will cause an overload of the system if the engine is set to use 9 GB. 
• The engine.exe will not be able to respect other services

The memory working setting limit is not a hard limit to set on the engine. This is a setting which determines how much we allocate and how far we are allowed to go before we start alarming on the working set beyond parameters. 

Internal Investigation IDs:

QLIK-96872, HLP-17517

When using SAML or ticket authentication which started in Qlik Sense June 2019, some users belonging to a big number of groups see the error "Qlik Sense G3 Broker API" on the hub and cannot proceed further.

You may receive the following error when setting up the SAML virtual proxy: cachebust pending 

Environments:

• Qlik Sense Enterprise on Windows 
  All Version
  
  

Resolution/Workaround

The only known workaround in the above versions is to reduce the number of groups sent in the SAML response or ticket request.

The fix for this defect is included in the following versions, but additional steps may be necessary:

All Versions

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"
   MigrationPort=4545
   (...)
   MaxHttpHeaderSize=65534

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

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

Other Related Articles:
https://community.qlik.com/t5/Official-Support-Articles/Error-431-when-trying-to-access-the-Qlik-Sense-Management/ta-p/1789124 

Internal Investigation ID(s):

QB-234.

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 Qlik Sense Repository Database (QSR) can be moved to a dedicated standalone PostgreSQL instance not hosted on the same machine as other Qlik Sense Services. It is also possible to move an already existing QSR from a local Sense install, to a dedicated PostgresSQL database.

Content:

• Set up a postgresSQL database
• Simplified checklist of steps:
• Moving the Qlik Sense Share Folders as well?
• Backup
• Restore
• Changing the Connection String to QSR and QSMQ Database
• Changing the Connection Stringto SenseServices Databases.
• Changing the Connection String to Licenses Database ( April 2019 and up )
• Remove Database Service dependency and Postgres Server
• Finalize

Set up a postgresSQL database

Instructions for this might vary slightly. Please refer to the Qlik Online Help for details.  We recommend watching this video.

Qlik Sense Enterprise server has a set of five databases. For more details visit Installing and configuring PostgreSQL on help.qlik.com.

1. The Qlik Sense repository database (QSR):

The QSR is the primary database in your Qlik Sense deployment.

2. The Qlik Sense services database (SenseServices):

The SenseServices database contains schemas for each of the Qlik Sense services and allows growth independently of the Qlik Sense Repository Database, while still sharing the same PostgreSQL instance and login role.

3. The Qlik Sense message queue database (QSMQ):

The QSMQ database provides a light-weight method of passing messages internally between services in Qlik Sense Enterprise. The NOTIFY and LISTEN functionality in PostgreSQL allows services to be notified about new messages that have been written to the messaging table.

4. The Qlik Sense logging database (QLogs): No longer supported after May 2021

The QLogs database centralizes logging by collecting log messages from all Qlik Sense nodes in your deployment and stores them in a PostgreSQL database.

5. The Qlik Sense license service database (Licenses):

The Licenses database is used to sync the assignments between the Qlik license backend and the local installation.

Simplified checklist of steps:

1. Download a valid version of postgresSQL.  For Sense June 2017 and up, 9.6.x is required, from November 2019 version 11.5.x as well. From May 2021 version 12.5 can be used. Review the system requirements of your version before proceeding.
2. Install based on instructions found on the Qlik Online Help for Qlik Sense; select the version you are running on then select from Menu , Deploy - Qlik Sense installation - Installing and configuring PostgreSQL.

Moving the Qlik Sense Share Folders as well?

Follow How to change the shared path in Qlik Sense 

Backup 

Depending on the version, you need to backup different databases, on the current Qlik Sense central node hosting the Qlik Sense Repository Database service, follow the backup instructions to obtain a database copy of each Qlik Sense Database Present . 
   Example for February 2021  you need to backup the databases reported in section "Installing and configuring PostgreSQL"; referring to the Help site these are : 
    QSR , QSMQ , SenseServices , Licenses , if configured QLogs    

Restore

On the dedicated remote postgresSQL host, perform a restore   of the backed up Databases of previous point. 

Changing the Connection String to QSR and QSMQ Database 

1. On the Qlik Sense central node, all services but the Qlik Sense Repository Service are shut down.
2. Open QlikSenseUtil. By default, this will be installed in: C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
3. Open the Connection String Editor and Read the current configuration, decrypting the current data.
   
   
4. Replace all mentions of the current database hostname.  In our example, the new database resides on 172.16.16.103. Instead of an IP you can also use the FQDN of the db server.
5. You need to repeat this step for the   sections <add name="QSMQ" and <add name="postgres"
6. Hit Save Value in config file encrypted, committing any changes. 

Changing the Connection String to SenseServices Databases. 

       Execute steps in Moved Postgress database to new host, but some qliksense is still accessing the SenseServices old database; check if different version of article are present for different Qlik Sense version .

Changing the Connection String to Licenses Database ( April 2019 and up ) 

Starting from April 2019 new License Service implementation is using this database.

1.   Open an elevated Powershell and change directory to C:\Program Files\Qlik\Sense\Licenses
2.    Run the script .\Configure-Service.ps1 and provide:
   • new Hostname or IP  
   • database port default is 4432
   • database user qliksenserepository
   • databasepassword is the qliksenserepository password  used during configuration of  the new database.
3. example: 
4. cd  'C:\Program Files\Qlik\Sense\Licenses'
5. .\Configure-Service.ps1 172.16.16.102 4432 qliksenserepository Password123!

It will look like this:

repeat this for:

Remove Database Service dependency and Postgres Server

After successfully verifying your new setup, remove the Qlik Sense Repository service dependencies and the old Postgres database. This is done to avoid issues with future Upgrade of Environment. 

1. In an elevated command prompt, execute the following on prompt:
   
   c:\sc config "QlikSenseRepositoryService" depend= ""
   c:\sc config "QlikLoggingService" depend= ""
   
   This will return: 
   
   [SC] ChangeServiceConfig SUCCESS
   
   
2. Restart the Qlik Sense Repository Service.
   
   Check that Qlik Sense Repository Database doesn't start (confirms [SC] ChangeServiceConfig SUCCESS ).
   
   
3. Remove the (local) Qlik Sense Repository Database
   
   Find the most recent PostgreSQL.msi in C:\ProgramData\Package Cache\  and remove it. This removes the service but no old local database data. This is needed to prevent issues on future upgrades of Environment.
   
   You can find the precise folder with this command depending on the Postgresql Version you used installing the inital release.
   
   9.6:
   
   c:\cd ProgramData\Package Cache
   c:\ProgramData\Package Cache\dir /s PostgreSQL.msi
   
   The folder containing PostgreSQL.msi will be revealed. Right click on the PostgreSQL.msi file and select uninstall from the menu.
   
   12.5:
   
   c:\cd ProgramData\Package Cache
   c:\ProgramData\Package Cache\dir /s PostgreSQL125.msi
   
   The folder containing PostgreSQL.msi will be revealed. Right click on the PostgreSQL.msi file and select uninstall from the menu.
   

Finalize

1. Restart the Qlik Sense Repository Service and verify that Qlik Sense Repository Database Service doesn't exist when followed the previous steps.
2. Start all remaining Sense Services 
3. Progress on the startup sequence (including the connection to the new database) can be tracked in the _System_Repository log files located in C:\ProgramData\Qlik\Sense\Log\Repository\Trace
4. Verify functionality.

5. In Multi-node scenario you need to repeat steps "Changing the Connection Strings to Databases" on all Rim nodes (QlikSenseUtil for Repository.exe.config and Configure-Service.ps1 for the micro services), and if required configure "Update the Qlik Logging Service Connection String" (note that is EOL with Qlik Sense Enterprise on Windows February 2022) .   

Environment

Qlik Sense Enterprise on Windows 

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

Logging out from Qlik Cloud Analytics leads to the error:

502 Bad Gateway

Resolution

QB-29858 will be fixed in an upcoming Qlik Cloud Analytics update. Until then, refresh the page to resolve the 502 Bad Gateway error.

The information provided on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID QB-29858 for reference.

Internal Investigation ID(s):

QB-29858

Environment

• Qlik Cloud

To retrieve the list of projects in TAC, use the following MetaServlet API command:

Command: { 'actionName': 'listProjects', 'authPass': 'admin', 'authUser': 'admin@company.com', 'onlyActive': true, 'onlyGit': false, 'withReference': false }

However, the above command will return multiple entries for the same project depending on the number of branches associated with it.

Resolution

To obtain a unique count of project names, regardless of the number of branches the project has, set the parameter 'loadAllBranchAndTag' to false in the command, as shown below:

Command : { 'actionName': 'listProjects', 'authPass': 'admin', 'authUser': 'admin@company.com', 'onlyActive': true, 'onlyGit': false, 'withReference': false, ‘loadAllBranchAndTag’ : false }

Note: please make sure to apply the patch TPS-5611 before executing this metaservlet command.

Environment

• Talend Data Integration 8.0.1

A talend job did run fine in the past two years, however, recently it was running slowly for several hours and freezes occasionally.

The job does not have much complicated sunjobs and it reads a file row by row, and for each row, checks the record type and sends the row to one of two possible output files. 

When trying to process a file with less than 30.000 lines, It loads about 1000 lines and then seems to freeze for several minutes, then loads another batch of lines, and so on. This issue doesn't reproduce on a newly created job (Duplicated one)

Resolution

After made an investigation on thread dump, the real time statistics was blocking the job and the problem seems to be appearing from the Statistics Monitor. It is suggested disable stats and logs both from Studio and Talend Administration Center sides using the below steps and re-run the job.

Studio Side

Disable Stats and Logs for Job level

Studio--> Designer -->Job-->Stats&Logs--> Disable the below check boxes.

• Use Statistics 
• Use Logs
• Use Volumetrics

We already have a global option in Studio >Preference>Talend>Run/Debug for Project Level

Talend Administration Center side

Job Conductor page--> Statistics-->disabled

Job won't open Socket and send message to Studio/Job Server when Statistics is disable and no matter disable it on job or project level, need to re-deploy jobs to Job server.

Cause

Checked the Thread dump and identified the below blocked threads:

org.talend.administrator.statistics.business.RealtimeTaskLoader->ExecStatisticsMonitor

The blocked threads indicate the problem occurs while retrieving the statistics and logs and the space and performance for this job is getting less and slower after it has been working for a while. 

Environment

• Talend Studio 
• Talend Administration Center 

Executive Summary 

Security issues in Qlik Sense Enterprise for Windows have been identified, and patches have been made available. If the vulnerabilities are successfully exploited, these issues could lead to a compromise of the server running the Qlik Sense software, including remote code execution (RCE).

This issue was discovered by Qlik during internal security testing and no reports of it being maliciously exploited have been received.

Affected Software 

All versions of Qlik Sense Enterprise for Windows prior to and including these releases are impacted: 

• May 2024 Patch 9
• February 2024 Patch 13
• November 2023 Patch 15
• August 2023 Patch 15
• May 2023 Patch 17
• February 2023 Patch 14

Severity Rating 

Using the CVSS V3.1 scoring system (https://nvd.nist.gov/vuln-metrics/cvss), these issues are rated HIGH.

Vulnerability Details

(CVE-pending) QB-29918, QB-29750 Remote Code Execution (RCE) via Connectors

Severity: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H 8.8 (High)

Unprivileged users with network access may be able to create connection objects that trigger the execution of arbitrary EXE files on Qlik Sense Enterprise for Windows.

(CVE-pending) QB-29586, QB-29864, QB-29482, QB-29802 - Broken Access Control (BAC)

Severity: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H 7.5 (High)

Unprivileged users with network access to Qlik Sense for Windows installation may be able to execute remote commands that could cause high availability damages, including high integrity and confidentiality risks.

Resolution 

Recommendation 

Customers should upgrade Qlik Sense Enterprise for Windows to a version containing fixes for these issues. Fixes are available for the following versions:

• November 2024 Initial Release
• May 2024 Patch 10
• February 2024 Patch 14
• November 2023 Patch 16
• August 2023 Patch 16
• May 2023 Patch 18
• February 2023 Patch 15

All Qlik software can be downloaded from our official Qlik Download page (customer login required).

Mitigating the Extension and Visualization Issue 

A workaround is available to address the complications affecting extension and invalid visualization errors. This workaround can be applied before or after the upgrade. It has been tested successfully on all patches released on December 4th. The November 2024 release is not affected by the issue. 

1. Stop the Qlik Sense Repository service
   
   
2. Open the file C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
   
   
3. Go to the section <appSettings>
   
   
4. Add the key VisualizationExtensionsExtractFilter as the last key in the <appSettings> section:
   
   <add key="VisualizationExtensionsExtractFilter" value="md|css|js|json|pdf|png|qext|txt|html|htm|gif|jpg|jpeg|wbl|otf|ttf|woff|woff2|eot|svg|bmp|mp3|jp2"/>
   
   
5. Save the file
   
   
6. Restart the following services:
   
   
   1. Qlik Sense Repository Service
   2. Qlik Sense Printing Service
   3. Qlik Sense Scheduler Service
   4. Qlik Sense Engine Service
   5. Qlik Sense Proxy Service

Question

What changes are made to the seat allocation after a license renewal?

If the number of seats or users will decrease after a license renewal, the admin user will receive an email that asks to de-allocate the exceeding seats within 14 days, and a reminder 7 days after. 
At the end of the 14 days, the seats will be de-allocated automatically starting from the least recent accesses. 
All of this info is included in the email received by the admin user.

Related Content

You can find further details on these seats allocation in tmc-account-license-info

Including details on what's considered admin seat within Talend Management Console.

Environment

Talend Cloud 

With the new inclusion of the Get Chart Image block in the Qlik Reporting connector in Qlik Application Automation, you now have more options to notify a group of users with more in-depth data and charts using Slack, Microsoft Teams, and email.

This article will guide you in sending your first chart image to Slack with Qlik Application Automation.

It explains a basic example of a template configured in Qlik Application Automation for this scenario.

You can make use of the template which is available in the template picker. You can find it by navigating to Add new -> New automation -> Search templates and searching for 'Send a Chart Image to Slack' or 'Embed a chart image in an email' in the search bar, and clicking the Use template option.

For guidance on sending charts via Microsoft Teams and mail, go to the "Next Steps" section at the end of this article.

You can download examples of the automations from this article: Send-chart-image-to-slack.json, Send-chart-image-to-outlook.json, Send-chart-image-to-mail.json, Send-chart-image-to-microsoft-teams.json

Full Automation

Configure the Automation

1. Open the automation editor and search for the Qlik Cloud Services connector on the left-hand menu.
   
   
2. Drag the blocks “Select Field Value” and “Create Bookmark” to the canvas and fill in the required inputs. You can add multiple Select Field Value blocks to apply selections to various fields. The Create Bookmark block is then used to create a temporary bookmark that can pass the selections to the Get Chart Image block.
   
   
   
   
   
   
   

   Warning: Whenever the “Get Chart Image” block is to be used, we advise you to only use it with temporary bookmarks or pre-existing persistent bookmarks.

2. Search for the Qlik Reporting connector on the left-side menu, then drag the "Get Chart Image" block to the editor and attach it below the previous block.
   
   Choose the same app you chose when creating the temporary bookmark and use the ID value received from the “Create Bookmark” block. 
   
   
   
   The height and width inputs are not required and default to 1000 if the fields are empty.
   
   Manually insert the Object ID input; it can not yet be retrieved through an API call.
   
   To find the chart ID from the app, open the app, then click Edit Sheet, right-click the chart, and open the Share/Embed menu from the menu dropdown that appears. You will see the object ID of the chart under the chart preview section as shown below:
   
   
   

    

3. Add the 'Condition' block to check whether the "Get Chart Image" block has returned a successful response.
   
   
   
   
   1. If the condition block outcome evaluates to true:
      
      
      • Search for Slack connector from the left-side menu, add the "Upload File To Channel" block, and fill in all the required inputs.
        
        
        
        
      • The chart image gets posted on the Slack channel as shown below:
        
        
         

   2.  If the condition block outcome evaluates to false:

      • Add the "Update Run Title" block to specify that the "Get Chart Image" block failed due to an error.
        
        
        
        
      • Add an "Error" block to throw an error message from the "Get Chart Image" block and set the current automation run to be in a failed state.
        
        
        

Configure and send the Output

Embed the chart in the email

Gmail does not support embedding base64 encoded images due to security constraints. To work around this, we advise sending the chart image as an attachment through the Send Mail block in the Mail connector if you use a Gmail account.

See Gmail blocking small embedded inline images in email template for details on the restriction. 

1. To embed the image in an email, you'll need to replace the Slack block with Send Mail block from the Microsoft Outlook 365 connector or the Send Mail block from the Mail connector and configure the block's Type parameter to HTML.
2. In the body of the HTML, start adding a <img> tag and set the src parameter of the img tag to "data&colon;image/png;base64,".
   

   
   

3. Add the Get Chart Image block output at the end of the src parameter.
   

   
   

4. Click the Get Chart Image label in the input parameter, and pick the Add formula option; then search for the "base64 encode" formula to apply it to the output from the Get Chart Image block.
   
   
   
   
   

   
   

5. Finalize the img tag with an optional width and height to style the image.
   
   

Send the chart to a channel in Microsoft Teams

1. To send the image to Microsoft Teams, replace the Slack block with the Send Html Message With Base 64 Image block from the Microsoft Teams connector.
2. Configure the "Base 64" parameter of the block by mapping it to the output of the Get Chart Image block.
   

   
   

3. Click the field mapping for the Get Chart Image again and open the formula picker. Search for the base64 encode formula and apply it.
   
   
   
   
    
4. Set the Image Content Type parameter to image/png and (optionally) provide additional HTML content that will be inserted before or after the image.
   

   
   

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 

Related Content

• Distributing Chart Images through Automation

This article explains how to simply set up JWT authentication using Qlik Sense default certificates and test it.

Steps:

1. Create a new virtual proxy
   
   This section only explains settings specific to JWT and supposes that you have set up Name, Prefix, Session cookie header name, load balancing nodes and linked a Proxy to the new virtual proxy.
   These are the minimum settings required for a virtual proxy to work correctly. Please refer to the Qlik Sense Online Help "Creating a virtual proxy" as well as Qlik Sense For Administrators - JWT authentication for details.
   
   
   1. In the authentication section, select JWT for authentication
   2. Paste the certificate used to sign/decrypt JWT in "JWT certificate
      
      In this article, we will use the default Qlik Sense certificate located:
      
      Important note: We use Qlik Default certificates for simplicity in this article, in a Production scenario, the customer should create the key material (generate a private/public key pair for JWT signing and verification) that is managed by customer internal security policies.
      
      
   3. Go to C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates
   4. Open server.pem in a text editor
   5. Copy the content including -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- then paste it in the JWT Certificate field in the QMC > Virtual Proxy configuration.
   6. Choose a value for JWT attribute for user ID and JWT attribute for user directory. That can be anything (except reserved key words for JWT claims) but it must match the values used in the JWT payload section when the JWT is generated.
   7. Apply changes and close.
      
       

      

      
      
      
2. Generate the JWT
   
   In this article, we will directly use the JWT debugger available on https://jwt.io to generate the token. In a real use case, the JWT library corresponding to the programming language used should be used to generate the JWT.
   
   
   1. Open https://jwt.io and go to the debugger
   2. Select RS256 for the algorithm
   3. In the PAYLOAD box, set up your attributes previously set via QMA in Qlik Sense's virtual proxy configuration for the user ID and the user directory. (Note: Swap 'DOMAIN' with the user's directory) 
   4. In the Verify signature, paste server.pem (Certificate) and server_key.pem (Private key) content in the appropriate fields. Those files are both located in C:\ProgramData\Qlik\Sense\Repository\Exported Certificates\.Local Certificates
   5. You can now copy the JWT generated in the left field and test it. This should look like:
      
      
      
      
3. Test the generated JWT
   
   In order to log in with JWT, you need to inject the JWT as a header. There are various extensions available depending on your browser in order to test this.
   
   In this example, we are using Chrome with Modheader.
   
   
   1. Install ModHeader from the Chrome Web Store
   2. Try to go to the hub:
      
                https://{your server name}/{prefix for JWT virtual proxy}/hub/
      
      
   3. You should get a 401 error: "Could not authenticate the request: Expected an authentication header." as no header has been provided.
   4. Go to ModHeader and set the following header:
      
             Header name: Authorization
             Header value: Bearer yourjwt
      
      
      
      
   5.    Reload the page, you should now be logged into the hub correctly.

In order to integrate your solution with Qlik Sense using JWT authentication, you will need to pass in your code the JWT token in the authorization token for the first request to Qlik Sense so that a session is created.

Related Content:

• Using Qlik Sense on Windows Repository API (QRS) with qlik-cli 
• Examples of integration for different purposes are available on the internet:
  https://github.com/qlik-oss/enigma.js/tree/master/examples/authentication/sense-using-jwt

It is not possible to set up a Microsoft Office 365 email provider with OAuth 2.0 authentication.
The HAR file shows this message in Network:

{connectionFailed: true, message: "Error during email request", success: false}
connectionFailed: true
message: "Error during email request"
success: false

Resolution

Configure the Mail.Send permission as it is described in Configuring a Microsoft 365 email provider using OAuth2.

Cause

This problem occurs when the Mail.Send permission has not been configured in the app registration.

Related Content

More information about the  Mail.Send permission can be found in Application permission to Microsoft Graph (learn.microsoft.com).

Environment

• Qlik Tabular reporting
• Qlik Cloud

The Replicate Connect Service does not start, leading to the Qlik Replicate IMS source endpoint failing to pull data from IMS.

Resolution

Verify what program is blocking irpcd.exe executable from launching, such as an anti-virus or threat protection program and enable an exception for irpcd.exe.

Cause

The irpcd.exe executable is quarantined by an anti-virus or similar threat protection program and cannot be started. 

Environment

• Qlik Replicate