Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch. 

All Qlik Replicate versions older than the 2024.5 SP03 release are affected.

Environment

• Qlik Replicate 2024.5 SP02 and below
• Oracle Source Endpoint with Oracle 2024 July patch (version 19.24)

Resolution

Upgrade to Qlik Replicate 2024.5 SP03 or later once available. 

Download the early builds for 2023.11 and 2024.5 here:

Link: https://files.qlik.com/url/ptbgkdzrixz2arpr
Password: ey9wfcf8

If you have Qlik Enterprise Manager deployed, upgrade this as well. See Qlik Enterprise Manager fails adding a table to a task with SYS-E-HTTPFAIL, no rest handler for url for download links.

Cause

The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly. 

Internal Investigation ID(s)

RECOB-8698

Reference:

Oracle Database 19c Release Update July 2024 Known Issues

As a general reminder, all changes to the environment such as operating system patches, endpoint and driver patches, etc. should be tested in lower environments before promoting to production.

Question I

How long does it take for Talend Management Console Logs to clear?

It takes 31 days. Any data older than 31 days will be cleared automatically as per our log retention policy. 

Question II

Can you manually change the time it takes for Talend Management Console Logs to be cleared?

The taken time for clearing TMC logs can not be manually changed. As mentioned in the answer for Question I, the 31 days is based on Talend log retention policy and cannot be manually changed.

Related Content

Talend-Cloud-Management-Console-Log-rotention-policy

Environment

Talend Cloud 

You can select a sheet to the landing page of the app by setting a default bookmark.

When you open the app, the expected landing page may not be displayed.

As well, when you open a sheet with a sheet action, the action might not get triggered.

Environment

• Qlik Sense Enterprise SaaS
• Qlik Sense Business

Resolution

The session needs to be terminated.

1. Close the browser or all opened tabs.
2. Wait for 30 minutes.
3. Log in to the tenant and open the app.

Cause 

The default bookmark with selection and landing sheet as well as sheet actions are applied once per session.

Qlik Sense SaaS keeps the session up to 30 minutes after closing the tab or tabs.

Related Content 

Setting a default bookmark to create an app landing page

The hybrid local deployment of Talend Data Stewardship (TDS) R2023-03 shows the newly created/updated Semantic Type (Regex pattern) for customized TIN_RULE as below, which is not functioning per Campaign task data filtering

^(\b\d{7}\b|\b\d{9}\b|\b\d{12}\b)$
^(\d{7}|\d{9}|\d{12})$

Resolution

Update private key and certificates from both Talend Dictionary Service Server and Talend Data Stewardship
 

Cause

After tried to update the Semantic Type by changing the Regex pattern and Naming/Label, and even creating a Semantic Type to publish, the newly created/updated Semantic Type is still not list from the Talend Data Stewardship Data Models side and it is not propagated to Model/Campaigns/Tasks for re-usage. Talend Data Stewardship could not fetch the Semantic Type successfully.

In Talend Data Stewardship catalina.out log, there are lots of network SSL disconnection error messages sent to dictionary service, and it could be the root cause.

Log Analysis 

Searched "UPDATE_CATEGORY" or "TsdEventListener" as a keyword in catalina.out log, you can find that:

The last time of dictionary service received dictionary service API feedback is at 2024-09-16 23:32:49,902. After that, TsdEventListener does not show the rules is propagated and updated successfully until you fix certificate_unknown issue at 2024-10-28 09:38:15,807

SCHM 2024-09-16 23:32:49,902 INFO [container-0-C-1] o.t.schema.datatypes.TsdEventListener : UPDATE_CATEGORY on [TIN_rule,

Till the certificate is fixed,  TIN_RULE shows ST updated

SCHM 2024-10-28 09:38:15,807 INFO [container-0-C-1] o.t.schema.datatypes.TsdEventListener : UPDATE_CATEGORY on [FirstName_Regex, tin_rule_v3,....

It indicates between 2024-10-01 and 2024-10-28 09:38 , the dictionary service could not be accessible due to certificate_unknown issue

starting date of Received fatal alert: certificate_unknown2024-10-01 06:05:32.743 UTC|TransportContext.java:361|Fatal (CERTIFICATE_UNKNOWN): Received fatal alert: certificate_unknown (
"throwable" : {
javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_unknown

Environment

Talend Data Stewardship

Talend Cloud 

Accessing the QlikView Server in the Management Console, or making changes in its settings, throws a "Failed to load because item with ID does not exist. Make sure that the QVS is available with the correct credentials." error.

Environment:

• QlikView 

QVPR is corrupted or includes a faulty Distribution Service / Reload Engine references.

Resolution:

This error message indicates that QlikView QVPR is corrupted.

I. If you have only started experiencing this recently, reverting to a backup of a previous QVPR version is advisable. 

Follow those steps to fix the issue, or see How To: Restore QVPR From Backup for details. 

1. Stop all the services
2. Open folder C:\ProgramData\QlikTech\ManagementService\QVPR\
3. Make a manual backup of all XML files, then delete them
4. Open sub-folder Backups
5. Select the zip file from the day before you faced the issue and unzip it in the QVPR folder.
6. Restart the services.

II. If this issue has been existent for a long while, it may be necessary to look into removing faulty Distribution Service / ReloadEngine references.

For QlikView 11.20 SR15 and up, as well as QlikView 12.x see ReloadEngine@SERVERNAME is down displayed in the QlikView Management Console after an upgrade

III. If the issue presents itself during a new installation, the best approach may be to rename the ProgramData\QlikTech\ManagementService folder, restart the Qlik Management Service which should recreate the directory and all the default settings and QVPR data. Note: all the save settings are restored to default and tasks are flushed)
 

This article gives an overview of the available blocks in the Github connector in Qlik Application Automation. It will also go over some basic examples of retrieving file/blob contents from your repos as well as other functionalities within a GitHub account.

As with most connectors provided for automations the authentication for this connector is based on the oAuth2 Protocol, so when connecting to it you provide the user name and password of the account directly to the Github platform to request access so it is done in the most secure manner there is.

Let's now go over a few basic examples of how to use the Github connector:

How to list owned repositories and check their contents from your Github account:

1. Create an automation;
2. From the left menu, select the Github connector;
3. drag and drop the "List my repositories" block
4. drag and drop the "List repositories contents" block inside the loop created by the first block:

Now the "list my repositories" block offers a couple of filtering options depending what result you want (all repos or just the private or public ones and if you want the result to come in sorted by some rule) but they are mostly optional. Not filling them in will return by default all repositories.

As for the "List repository contents" block you will need to fill in the username you use for your github account as well as the repository name which can be filled in with the results gotten from the first block. You can leave the path parameter empty to get the contents from the root folder or you can specify a path and the contents of that path will be returned.

As stated, if you expect to retrieve only one record, the use of "get repository content" block is more better suited. Also, you might want to switch this "List repository contents" block On Error status to either warning or ignore since Github API platform returns a 404 error if one of the queried repositories is empty.

Now if you are planning to use the "Get repository content" block another warning should be mentioned and that this block only works for files or blobs up to a maximum of 1 MB in size, as per Githubs platform limitations. The response of this block should look like:

As you can see we have a couple of information stubs of that file, but most importantly from here is the SHA property, which is needed if you are planning to later on use the "Create or update file contents" block, required input parameter for the update of a file/blob.

Now if you're planning on updating files that are bigger than 1MB and you require the SHA of that file, we suggest using the list repository contents block and search for the required file and SHA in that result.

As for other functionalities of the Github connector we support also getting and listing commits or issues present in a repository, listing of users and many other requests but, if you are in need of a request that isn't present, we also offer the functionality to create your own requests to the Github API by making use of the RAW API blocks. These API blocks and their uses are explained in a separate article.

You can find attached to this article a simple JSON example which you can upload to your workspace, if you want to see a quick example of how to use version control to back up your QCS apps I suggest visiting the related article.

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

Related Content

How to: Qlik Application Automation for backing up and versioning Qlik Cloud apps on Github

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

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

QlikView and Qlik Sense files are like ZIP file, as in they are highly compressed. So obtaining an estimate of how much RAM is needed for loading Apps into memory (footprint) is difficult to provide across the board. The expected memory usage associated with the app can also depend on how many users access the app and how much they are used.

Environment: 

• QlikView, all versions
• Qlik Sense Enterprise on Windows,  all versions
• Qlik Cloud

An estimate of the RAM needed per app can be built on the below, but for accuracy always test by loading the app into memory and using the Qlik Scalability Tools to obtain a baseline of memory usage for each app as it is accessed by the foreseeable number of users. 

Telemetry logging which allows for using the Telemetry Dashboard, is also an available suitable tool.

Since the release of the February 2019 version, Sense System Performance Analyzer monitoring App can be used to determine app footprint as well. Since the release of the June 2018 version, App Metadata Analyzer monitoring App can also be used. However, these last three may not provide the same data as the Scalability Tools.

An alternative is to use a test environment and simply observe RAM usage increases as apps are first opened (footprint), and as number of users accessing the app increase, then as number of operations are performed within the app. The test environment results for observed memory and CPU usage can be recorded as a baseline for the particular app in production, which assists in determining future sizing/scaling needs.

Need direct assistance in evaluating your Qlik Sense and QlikView apps? Qlik's Professional Services are available to assist you.

RAMInitial = SizeOnDisk × FileSizeMultiplier ; this is the initial RAM footprint for any application 

FileSizeMultiplier: range between 2-10 (this is a compression* ratio depending on the data contained in the app) 

*Compression is based upon the data, and how much we can compress depends upon the homogeneity of the data. The more homogeneous, the more compression Qlik can achieve. 
More information on one way of optimizing a document can be found on the Qlik Design Blog: Symbol Tables and Bit-Stuffed Pointers

RAMperUser = RAMinitial ×  userRAMratio ; this is the RAM per each incremental user 

userRAMratio: range between 1% -10%
 

Total RAM used per app :

TotalRAM = (RAMperUser × Number of users) + RAMinitial 

Example:

SizeOnDisk = 1 GB

File Size Multiplier 6 (range is from 2 to 10) This is an example value. A value can be obtained by reviewing telemetry (how far does the app expand?) or opening the app in a QlikView or Qlik Sense desktop and measuring the expansion based on how large it grows in memory.

RAMinitial = 1 * 6 = 6 GB

If we take a RAM Ratio per User of 6% then it is 0.06 (range is from 1 to 10)

RAMperUser = 6 x 0.06 = 0.36GB

Then RAM Required for 30 Users

TotalRAM = (RAMperUser × No. users) + RAMinitial 
TotalRAM =  (0.36 * 30) + 6
TotalRAM = 16.8 GB

Related Content:

• App Metadata Analyzer
• Sense System Performance Analyzer 
• Qlik Sense Scalability Tools - Community
• How to enable Qlik Sense QIX performance logging and use the Telemetry Dashboard
• Single/Multi-threading in QlikView
• Qlik Sense Performance Benchmark
• Qlik Sense Scalability Tools

After a successful installation of Qlik Alerting following Qlik Alerting installation steps, Installing the Qlik Sense Extension, and then adding the extension object to an Qlik Sense app with the proper Qlik Alerting server information, the extension shows up blank in Internet Explorer (IE) or with the message "Could not retrieve user info. Check your extension settings or contact your administrator" when using Google Chrome:



Chrome will output the following or similar in the Developer tools Console logs: (also under Network tab the extension failure is registered)

POST https://<Qlik Alerting server>:4552/api/users/extension net::ERR_CERT_AUTHORITY_INVALID
error

IE in the other hand will output the following or similar in the Developer tools Console logs and not much under the Network tab (halts after loading the Qlik Alerting js file):

SCRIPT1002: Syntax error
File: qlik-alerting.js, Line:9, Column: 42
SCRIPT5007: Unable to get property '__esModule'of Underfined or null reference

Environment:

• Qlik Alerting 
• Qlik Sense Enterprise on Windows 

In order to use a HTTPS connection with the Qlik Alerting extension a proper certificate needs to be installed on the Qlik Sense clients' computers. Otherwise HTTP needs to be used as indicated in the Workaround(s) section.

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.

Replace the Qlik Alerting self-signed certificate with the certificate issued for the deployment in order to allow HTTPS connections. Otherwise, a certificate error is observed when connecting to the Qlik Alerting web console and API connections from the extension fails as described above. See Workaround section below for an alternative.

There are at least the two methods for resolving the error above:

I. Using the server.pem and server_key.pem files that were originally exported from Qlik Sense:

The easiest way to resolve the error above is to use the server certificate and private key that was originally exported from Qlik Sense.

Note: This may not be suitable for all production environments. It will not allow the extension to function from outside the Qlik Sense / Qlik Alerting local network. E.g: When an external FQDN / Alias / CNAME is used to access the Qlik Sense app that uses the Qlik Alerting extension.

1. Follow the steps documented under Using trusted SSL certificates with Qlik Alerting and replace the mentioned server certificate files (server.pem and server_key.pem) with the server certificates (not the client certs) that were originally exported from Qlik Sense when going through the steps to configure the connection between Qlik Alerting and Qlik Sense.

2. When configuring the extension, make sure to use the machine name that was used when exporting the certificate via the Qlik Management Console (QMC). This will be the "Issued To" field found in the certificates.

3. Make sure the Qlik Sense self-signed root CA certificate (root.pem / root.cer) is installed on client computers (including the Qlik Alerting server) that require access to the web console and use of the Qlik Alerting extension in Qlik Sense apps. The certificate should be installed in the Trusted Root Certification Authorities store.

II. Another method is to replace the Qlik Alerting self-signed certificate with a certificate issued by a private or public CA for the deployment in order to allow HTTPS connections.

Note: The following is an example of issuing an SSL certificate using TinyCert. Please note that certificates issued by TinyCert.org are not considered to be "production ready" and should only be used for evaluation or testing. More information in TinyCert FAQ

1. Sign up for a free TinyCert account.

2. Create a Certificate Authority (CA) certificate. Using the defaults works fine.

3. Create a server certificate. Make sure to include all the host names used when accessing the Qlik Alerting server over https.

For example: The server machine name (hostname) may be sufficient in environments where clients are always on the same local network (LAN). However, an external FQDN (Alias, or CNAME records) for Qlik Alerting may be needed in the certificate's Subject Alternative Names in order to allow the extension to work when Qlik Sense app are accessed from outside the LAN. Keep in mind the client using the Qlik Alerting extension in the Qlik Sense app makes the connection request directly to the Qlik Alerting server.



4. Download the CA Certificate (cacert.pem). This certificate will need to be installed on client computers that use the Qlik Alerting extension as well as accessing the web console (to eliminate the cert error).

5. Download the server Certificate (cert.pem), and the Private key (clear) (key.dec.pem).
Note: Qlik Alerting does not support the option Private key (encrypted) as it does not support passphrases.

6. Move the three files to the Qlik Alerting server and follow the steps documented under Using trusted SSL certificates with Qlik Alerting.
Note:

• The cert.pem file above is the one that gets renamed to server.pem
• The key.dec.pem above is the one that gets renamed to server_key.pem

7. Import the CA Certificate (cacert.pem) on the Qlik Alerting server and on any needed client computer using the Certificates snap-in.

Workaround(s):

In use-cases where encryption of the traffic between the Qlik Sense client and Qlik Alerting is not a priority, communication via plain HTTP (unsecured) can also be used by unchecking the HTTPS option in the Extension configuration:


However, please note that in order for the above workaround to work the Qlik Sense app also needs to be accessed via plain HTTP (unsecured). Otherwise, the error reported above "Could not retrieve user info. Check your extension settings or contact your administrator" will be displayed along with the other errors for the two browsers. In Google Chrome the following will be registered in Developer tools Console logs:

Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint '<URL>'. This request has been blocked; the content must be served over HTTPS.

 

Related Content:

• General: what does the certificate error(red cross) in browser mean and how to fix it

When attempting to upgrade/reinstall a Dynamic Engine (DE), you may encounter an issue where you cannot deploy a new set of manifest files to the cluster. When applying the manifest files, even though it may apply all the namespaces and pods were created, a check of the DE using the "kubectl wait --for=condition=Available=true -n qlik-dynamic-engine deployment/engine-operator-dp --timeout 60s" command may fail with the following message:

Error from server (NotFound): deployment.apps "engine-operation-dp" not found

Cause

In many cases, the issue arises when some or all pods and namespaces may have been deleted, but the previous setups and definitions remain on the cluster. If these remain, they may hinder the successful application of manifest files, as these files will only generate new setups and definitions, rather than replacing the existing ones on the cluster.

Resolution

To remove any previous setups and definitions, please follow these steps:

1. The environment setup may still be deployed on the cluster if it hasn't been removed already. To verify this, please execute the following command:

   kubectl get qlikruntimes.qlik.com

2. If a custom resource still exists, it should return the name similar to this, "qlik-processing-env-<id>". Copy the value down and delete the environment-related resources and associated namespaces with the following commands:

   kubectl delete qlikruntimes.qlik.com remote-engine-<id>

   kubectl delete namespace qlik-processing-env-<id>

   

3. After removing the environment setup, the next setup to go is the infrastructure environment. Users can run the "kubectl get qlikruntimeinfras.qlik.com" command to show the resources with that name.

   Once the name that returns has been copied, delete the infrastructure setup and associated namespace with the following commands:

   kubectl delete qlikruntimeinfras.qlik.com qlik-dynamic-engine-<id>

   kubectl delete namespace talend-infra

   kubectl delete namespace qlik-dynamic-engine

4. The final step is to delete the custom resource definitions created by the initial DE manifest file. These definitions can be removed with the following commands:

   kubectl delete crd qlikruntimes.qlik.com

   kubectl delete crd qlikruntimeinfras.qlik.com

   

Once removed, download a new set of Manifest files from the TMC of the Dynamic Engine object and follow the steps in the Documentation to apply them.

Requesting Assistance from Support

If these steps are followed and the DE is unable to connect to TMC or establish a link with the assigned environment, kindly contact Support to investigate and verify the current issue.

When reaching out, the following items should be provided:

• Screenshots of the following items:
  • The output generated by the "kubectl wait --for=condition=Available=true -n qlik-dynamic-engine deployment/engine-operator-dp --timeout 60s" command, to validate the error output shown.
  •  All deployed (and failed) pods and namespaces on the cluster, via the "kubectl get pods --all-namespaces" command.
  • The DE Object and assigned workspaces in TMC, to confirm the status of the connection and pairing.
  • The subscription page in TMC allows Support can confirm the Domain Name and ID.
• A zipped copy of the manifest files that were being applied, for Support to review and validate.

Environment

• Talend Data Integration 8.0.1

Environment

• Qlik Sense Enterprise on Windows 

Resolution

Use different Proxies.

The underlying issue is that when the “Copy” of the App is being made, the copy would be unpublished, ergo the node that is making the Copy cannot see it, so the process fails.

It is suggested to use different virtual proxies instead of only one to load balance nodes for Published and Non published apps.

Internal Investigation ID(s) :

JIRA ID SHEND-631

While accessing Microsoft Azure SQL (MS-CDC) as the source database, the task reports an error message during the task startup.

The messages in the task log file:

[SOURCE_CAPTURE  ]V:  Execute: 'select is_cdc_enabled from sys.databases d where d.database_id=db_id()'  (ar_odbc_stmt.c:2768)
[SOURCE_CAPTURE  ]E:  MS-CDC Fitness Check: Database is not enabled for MS-CDC [1020101]  (sqlserver_mscdc.c:727)
[SOURCE_CAPTURE  ]E:  Failed in MS-CDC fitness check [1020101]  (sqlserver_endpoint_capture.c:274)

The error occurs even if the DBA has correctly set up the database for MS-CDC by executing the following:

exec source_db_name.dbo.sp_cdc_enable_db

Environment

• Qlik Replicate, all versions
• Microsoft Azure SQL source, all versions

Resolution

Add an internal parameter to adjust task behavior:

1. Open the Microsoft Azure SQL (MS-CDC) source endpoint
2. Go to the Advanced tab
3. Open Internal Parameters
4. Add a new parameter named UseDBNameInsteadOfDBID, and enable it by ticking the checkbox: 
   
   

Reading an XLS file which includes a specific character leads to Qlik Sense failing with the following error:

An Error occurred
Connection lost. Make sure Qlik Sense is running properly. If your session has timed out due to inactivity, refresh to continue working.
Error code: 16

Example:

1. Create a new app
2. Open the Data load editor
3. Select Attached files and import an xls file which includes 2363B code characters.
4. ??? is shown as the date after the character
5. Click Insert script, followed by Load data and confirm the result by clicking Close
6. Go to Edit Sheet
7. Add a table and add the previously loaded data as dimensions
8. The error is displayed

The error is avoided when using XLSX or CSV files with identical data. 

Qlik Cloud is not affected.

Resolution

Workaround:

Use xlsx or csv as source files.

Fix Version:

No fix is yet available for Qlik Sense Enterprise on Windows. Qlik anticipates a fix for its May 2025 release. 

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, or contact support with the ID QB-29693 for reference.

Cause

The error is triggered when reading .xls files containing strings with UTF-16 surrogate pair characters, such as emojis or rare Asian characters. The specific characters leading to the problem are uncommon. 

Environment

• Qlik Sense Enterprise on Windows, all versions

Loop and Reduce will remove an app's section access that was defined through the load script. Offline usage needs to be enabled in your tenant's management console in order to use the Loop And Reduce block on an app outside a personal space. More information on offline usage.

See How to Loop and Reduce with always one selected value fields if your app contains always one selected value fields.

This article explains how a loop and reduce operation can be performed on a Qlik Sense app by using Qlik Application Automation. It covers two examples, in the first one, the reloaded apps will be (re)published to one space. In the second example, each reduced app will be (re)published to a separate space.

This article covers two advanced examples, a more basic example can be found here .

Covered in this article:

• 1. Loop and reduce to one space
• 2. Loop and reduce to multiple spaces

The source app used in this article can be downloaded here.

Attached to this article are 2 files of the exported automations used in this article. More information on importing automations can be found here.

1. Loop and reduce to one space

In this example, all reduced apps will be (re)published to the same space.

Create a new automation and follow these steps to perform a loop and reduce action on a Qlik Cloud app:

1. Go to the Qlik Cloud Services connector and search for the block "Loop And Reduce". Drag this block inside the automation editor.
   
   
2. Specify the id for the app that should be used as a source app. The reduction will be performed on this app. Next, specify the field name over which the loop should run, for each unique value of the specified field name, a reduced app will be created. In this example, CountryName will be used as the reduction value.
   
   

    

3. The reduced apps are stored on the Temporary File services. The Loop And Reduce block will return a list of file ids together with the unique value of the reduction field and a list of sheet ids for the sheets that were public on the source app.
   
   
4. The next step is to import the apps from the Temporary File services. To do this search for the block "Import App From Export Id" and drag this block in the loop that's created by the Loop And Reduce block. This block will import one app from the temporary file services into your personal space.
   Tip: specify the reduced value that's outputted by the Loop and Reduce block in the Name parameter of the Import block. See the below image for an example:
   
   

    

5. When an app is imported, all sheets will be made private, this is the default behavior of the import app block. The next step is to publish the sheets that were public in the source app.
   
   
6. Because each reduced app will have a list of sheets that were public, a Loop block is necessary to loop over the list. Search for a "Loop" block in the block menu or find it under Basic and connect it right below the "Import App From Export Id" block. Specify the "Public Sheets" list returned by the Loop And Reduce block as the value for the "Loop over items of list" input parameter of the Loop block.
   
   

    

7. Now to publish each sheet of the imported app, search for the block "Publish Sheet" in the Qlik Cloud Services connector and drag that block in the loop generated by the "Loop" block. In this block, specify the id that's returned by the Import App block as App Id and use the current item in the loop as Sheet Id.
   
   

    

8. Nex step is to publish or republish the imported app to a managed space. This can be done with the block "Publish App To Managed Space". Search for this block in the Qlik Cloud Services connector and connect it below the loop block. Set the Run Mode to "(Re)publish by name", if the managed space already contains an app with the same name as the imported app, the imported app will be republished, or else it will be published.
   
   
9. In the configuration of the Publish App To Managed Space block, set the App Id equal to the id returned by the Import App From Export Id block. For the Space Id, perform a lookup or manually enter an id, make sure you're specifying a managed space. The Data parameter should be set to "source".
   
   

    

10. Finally, when your app is published to a managed space, the imported app will still exist in your personal space. To remove this app, search for the block "Delete App" in the Qlik Cloud Services connector and connect it to the Publish App To Managed Space block. Specify the id returned by Import App From Export Id as the App Id in the block's settings.
    
    

An example of a completed automation:

Attached example file: loop_and_reduce_to_same_space.json

2. Loop and reduce to multiple spaces

In this example, each reduced app will be published to a different space. We'll use the Insurance Claims app and the automation for the first example again. Since this app reduces on the field CountryName, we'll start by creating a managed space for each unique value that's found for CountryName. This results in the following list of spaces:

Next is to create a mapping for each unique reduction value and the corresponding space's id. There are multiple ways to achieve this. In this example, this mapping is stored in a JSON list of objects with the keys reduction_value and space_id. Feel free to use an automation to create the managed spaces and build this list.

Example:

[
	{
		"reduction_value": "Scotland",
		"space_id": "6138a3062c1054d8158c189a"
	},
	{
		"reduction_value": "Northern Ireland",
		"space_id": "6138a318faed485d36ae911f"
	},
	{
		"reduction_value": "England",
		"space_id": "6138a337faed485d36ae9126"
	},
	{
		"reduction_value": "Wales",
		"space_id": "6138a33f98b0d0bf7e719dfb"
	},
	{
		"reduction_value": "Guernsey",
		"space_id": "6138a349faed485d36ae912b"
	},
	{
		"reduction_value": "Isle of Man",
		"space_id": "6138a35aba392246d331e611"
	},
	{
		"reduction_value": "Jersey",
		"space_id": "6138a3653ec592fe53a8d55b"
	}
]

The next step is to store the mapping in the automation. Execute the following steps to do this:

1. Search for the Variable block and add this to the automation.
   
   
2. Go to the block's settings, click Manage variables and add a new variable of type list.
   
   
3. Go to the operations section of the variable and set the first operation to empty the variable.
   
   
4. Add a second operation Merge other list into... and click the List input field of that operation, in the dropdown that appears, select Add Formula.
   
   
5. From the formula picker, search for the formula Object and select it. Copy the JSON mapping to the json input field of the Object formula and click Save.
   
   
6. Add the block to the beginning of the automation from the first part of this article:
   
   

    

7. The next step is to find the right space id for each reduced app. To do that, add the block Lookup Item In List in the automation right before the block Publish App To Managed Space.
   
   
8. Go to the settings of the Lookup Item In List block and specify the variable that contains space_id/reduction_value mapping as input list. The condition inside the lookup should compare the mapping's reduction_value to the Reduced Value of the current item in the loop of Loop And Reduce. See the below image for an example:
   
   
   

    

9. Finally, specify the space_id from the output of the lookup block as Space Id in the settings of the Publish App To Managed Space.
   
   

    

Attached example file: loop_and_reduce_to_mulitple_spaces.json

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.

For information about Qlik Sense failover candidates, see Qlik Sense Failover Central node: Requirements and Considerations.

Out of the box, you need to toggle the option to enable a rim node as a failover node during first time setup. In this article, we will outline how to accomplish elevating an existing node to being a failover candidate primarily using the QRS APIs.

Steps:

1. Perform a GET /qrs/ServerNodeConfiguration/full API call
   
   
2. Copy the JSON response
   
   
3. Edit the JSON to include only the node that you want to elevate
           Remember to remove the []'s which bracket the JSON response
   
   
4. Change the failoverCandidate to be true and slightly modify the modifiedDate
   
   
5. Perform a PUT /qrs/ServerNodeConfiguration/{GUID_of_note_to_elevate} with the edited JSON in the body
   
   
6. Export full trusted root from existing Central candidate
   
   
7. Stop services on the newly elevated rim
   
   
8. Deleted the existing trusted root certificate on the newly elevated rim
   
   
9. Import the copy of the certificate that was previously exported from an existing Central candidate
   
   
10. Start all services on the rim

Environment

Qlik Sense Enterprise on Windows 

Related Content 

https://community.qlik.com/t5/Official-Support-Articles/Removing-a-Rim-Node-not-to-be-a-Failover-candidate-in-the/ta-p/1711472 

Qlik Replicate task fails during run time:

RetCode: SQL_ERROR SqlState: S1000 NativeError: 4 Message: [SAP AG][LIBODBCHDB DLL][HDBODBC] General error;4 cannot allocate enough memory: OOM. please check traces for further information [1022502] (ar_odbc_stmt.c:2789)

Resolution

To address the memory error:

1. If not already stopped, manually stop the current task
2. Edit the source SAP HANA endpoint / from Advanced tab
3. Add the following three Internal Parameters:
   
   
   • fetchQueryHints 
     value:  NO_CS_EXPR_JOIN
   • hextobinLocation
   • value: excludingJoin
   • maxFetchIntervalSize (note that this internal parameter is depreciated in 2023.5 and 2023.11 as the parameter now appears as an endpoint setting)
     value: 10000
     
     
     

For more information on how to set Internal Parameters, see: Qlik Replicate: How to set Internal Parameters and what are they for? 

Environment

Qlik Replicate 
SAP Hana Endpoint

It is not possible to Include and Must_include variables with native Qlik Cloud scripts. Doing so leads to the error:

Unable to fetch file

Resolution

The possibility to include native Qlik Cloud scripts in other apps is on the roadmap for 2025.

In the meantime, there are two possible workarounds:

• Manually copy and paste the script to a txt file, then save it as a qvs file and reimport it
• In the native script: 
  1. Enter the script editor
  2. Access the script's history
  3. Export the script from there
  4. You will receive a qvs in text format
  5. Import the qvs to the tenant and use that in the “include” variable

Cause

There are two sorts of script files in Qlik Cloud:

Native scripts: they are qvf files. They can be reloaded on their own, but currently cannot be included.

Qvs scripts: they are imported as datasets, and they are txt files. They cannot be reloaded on their own, but they can be included.

Environment

• Qlik Cloud

Question

Does NPrinting have the ability to send NPrinting reports to a Microsoft Sharepoint or other worldwide web url address destination?

Environment

• Qlik NPrinting: All Versions

Resolution

• It is not possible to automatically distribute Qlik NPrinting reports from an Qlik  NPrinting publish task to any type of HTTP, FTP or any other worldwide web url addresspath.
• Therefore, it is not possible to send NPrinting Reports to an MS SharePoint worldwide web address.
• To workaround, it is possible to use a local or network path as defined in Distributing reports to folders
• Create a network share on the Sharepoint server and use that network folder as a destination for the distribution of your Qlik NPrinting reports.

Local and Network path examples:

• Local: c:\nprinting\output
• network: \\myfileserver\files\nprintingoutput
  
  NOTE: Keep in mind that the NPrinting Scheduler service user account must have NTFS file and folder security permission to access local or network share folder destinations. It must also be in the same domain as the share point or destination server host address path or the NP service account will fail to open the network path.
  

*This feature is not planned nor on the NPrinting road map at this time. You can check our 'ideas' page to determine if this has been requested. You can add your request at the link below if it has not: Ideation 

Related Content

• NPrinting Engine System Requirements
  • Storage: Only Windows, local or shared, storage is supported.

A user has been given permissions to a section of the Management Console with a new security rule (example: Apps or Streams), but when they access the console, all sections remain grayed out.
 

To give a user access to the different sections in the QlikSense Management Console, seperate rules need to be added to allow access to QMC Section Resources. 

The following filters are used to grant access to the different sections. A user with access to a QMC section can open that section, but will only see objects according to the user's access rights.

QMC section resources

Resource filter Filter will target

Related Content

• Security Rule Example: License Management only access in the Qlik Sense Management Console (QMC) 
• Qlik Sense Management Console sections grayed out and cannot be accessed 
• Available resource filters