To help Qlik customers manage costs more effectively, Qlik has developed the Qlik Snowflake Monitoring application, designed to provide invaluable insights about your Snowflake costs, usage, inventory, security, performance and contract utilization. This app utilizes Qlik's Associative Engine to connect directly to your Snowflake instance and reveal insights from Snowflake's detailed metadata, offering valuable information that traditional query-based tools and Snowflake's own reports are unable to provide.

Leveraging Qlik Application Automation, and Data Alerts, you can:

• Install* & update the app with a fully guided, click-through installer, using an out-of-the-box Qlik Application Automation template.
• Get alerted when new versions of the Snowflake Monitor are available using Data Alerts.

*Minor configuration is required on first run to create the required data connections.

Content:

• Part One: 'Qlik Snowflake Monitoring App Installer' templateoverview
• Features
• Note on manual install
• Part Two: Creating and setting up analytics data connections
• Snowflake connection
• Note on Snowflake authentication
• REST connection to repository
• Note on update compatibility
• Part Three: Set up a Data Alert to notify when a new version of the app is available
• Summary

Part One: 'Qlik Snowflake Monitoring App Installer' template overview

This automation template is a fully guided installer/updater for the Qlik Snowflake Monitor. Leverage this automation template to easily install and update this application. The application itself is community-supported; and it is provided through Qlik’s Open-Source Software GitHub and thus is subject to Qlik’s open-source guidelines & policies.

For more information, refer to the GitHub Repository.

Features

• Easy app installation and updates
• Create new spaces or use existing spaces
• Automatic setup of settings, roles, and permissions
• Always installs the newest version from Qlik's OSS GitHub
• Tags apps to easily track installations and versions
• Works with both user and capacity-based subscriptions
• Compatible with all Snowflake tenant levels

Note on manual install

If the monitoring app was installed manually (i.e. not through the application automation installer), then the app will not be detected as existing. The automation will install new copies side-by-side. Any subsequent executions of the automation will detect the newly installed monitoring application and check their versions. This is because the application is tagged with ‘QCS - QSM - {App Name}’ and ‘QCS – QSM - {Version}’ during the installation process through the automation. Manually installed applications will not have these tags and therefore will not be detected.

Part Two: Creating and setting up analytics data connections

The Qlik Snowflake Monitor requires two connections, one to your Snowflake instance to feed the data for your analytics, and one REST connection to the qlik-oss repository to run a version check on the monitor.

Snowflake connection

You will need to create a custom User, Role and Warehouse on your snowflake tenant. This is to ensure this user and role can see the monitoring details and can be monitored.

1. Update the credentials in the SQL script from GitHub 
2. Run the SQL as ‘ACCOUNTADMIN’ from your Snowflake tenant to create a warehouse to retrieve the relevant data. Make sure you change the password and store this securely.
3. Create a snowflake data connection in the Qlik analytics space into which the application was deployed, using the following details:
   
   
   • Server: The full hostname for the Snowflake account, not prefixed with http:// or https://
   • Port: Leave as default unless it needs changing.
   • Database: SNOWFLAKE
   • Schema: ACCOUNT_USAGE
   • Warehouse: QLIK_MONITORING_WH
   • Role: QLIK_MONITORING_ROLE
     
     

   For Authentication, this setup is defaulted to username & password.

   • Username: QLIK_MONITORING
   • Password: As specified in your configuration above
     
     

   Finally, you need to name the connection as follows:

   • Connection Name: SNOWFLAKE_MONITORING_DATA
     
     
   
   

    

Note on Snowflake authentication

If you wish to use an alternative authentication method, please follow the documentation accordingly on both Snowflake & Qlik.

REST connection to repository

The REST connection is used to fetch version details from the GitHub repository. On reload it will look for the the latest released version in github and check this against the version you have installed. You can later use this in ‘Part Three’ to create an alert when updates to the application are available. To create a REST connection the following information is required:

• URL: https://github.com/qlik-oss/qlik-snowflake-monitor/raw/main/manifest.json
• METHOD: GET
• Allow “WITH CONNECTION”: Enabled
• Connection Name: REST Monitoring Versioning API
  
  
  
  

Once these two connections have been set up, you can reload the application. The application has been created to accommodate Snowflake tenants of all sizes. If you have a small tenant, you will find the initial run of the load script can take around 30 minutes, and for larger tenants this can be over an hour or two. Subsequent runs will utilize cached QVDs that update daily to reduce reload times each subsequent day.

Note on update compatibility

If a new release of the application is made, occasionally a full reload of data is required, but generally, if the data schema is unchanged the existing QVDs will be maintained. This is through the use of versions in the names of the QVDs used to store the data.

Part Three: Set up a Data Alert to notify when a new version of the app is available

The application has the following two variables:

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

To create a new Data Alert for updates to the monitoring app, follow these steps:

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

   

6. Navigate to the Distribution tab and confirm that the alert is evaluated When data is refreshed.

Summary

The Qlik Snowflake Monitor can be easily installed by following these steps above. If you wish to find out more, check out this Ometis blog post and this Ometis Webinar to get a run through of the analytics this application can offer.

If you face any issues, please use the GitHub and raise an issue through the repository.

Unable to generate personal access token in TMC and shows error "Token creation has failed" in TMC

PersonalAccessToken

Cause 

Talend Cloud users can generate up to five access tokens. So as an administrator, you can view the name, owner, creation date and last date used for each token generated on the account. You can delete tokens individually or by group.
It is recommended to delete unused and old tokens to increase the system security.

Resolution

1. Go to Users & Security > Access tokens.
2. Find tokens using the search or by sorting columns.
3. Select the tokens you want to delete.
4. Click Delete and confirm the operation.
   You cannot recover deleted tokens. If you delete a token by mistake, the user will have to create a new one.

Related Content

cloud-admin-tokens

Environment

Talend Cloud 

Qlik Sense offers a range of Monitoring Applications that come pre-installed with the product.  This article aims to provide information on where to find information about them or where to download them.

Content:

• Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Access Evaluator for Qlik Cloud
• How to automate your Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• Qlik Application Automation Monitoring App
• 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

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.

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 and to download the app and usage instructions, see The Entitlement Analyzer for Qlik Cloud.

App Analyzer for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud App Analyzer.

Reload Analyzer for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud Reload Analyzer.

Access Evaluator for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud Access Evaluator.

How to automate your 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

Qlik Application Automation Monitoring App

For more information and to download the app and usage instructions, see Qlik Application Automation monitoring app.

OEM Dashboard for Qlik Cloud

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

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

Logs not showing up in TMC when a task is running on Remote Engine.

Cause

The payload of the generated metrics was exceeding the file size limit.

Most common error log:

com.fasterxml.jackson.databind.JsonMappingException: Invalid UTF-8 middle byte 0x70
at [Source: (ByteArrayInputStream); line: 1, column: 24553] (through reference chain: org.talend.observability.common.model.CloudEvent["data"]->org.talend.observability.common.model.MetricSet["metrics"]->java.util.ArrayList[42])

Resolution[can be removed if not necessary]

To address the issue and eliminate the error logs effectively , please follow these steps:

1. Update Configuration:
   • Locate the configuration file: org.apache.karaf.decanter.collector.rest.servlet.cfg.
   • Modify the property max.request.size to 200000000. This change increases the maximum request size limit.
2. Understanding the Change:
   • The default value for max.request.size is 100000000, which corresponds to 100 MB of memory usage on Remote Engine. By increasing this value to 200000000, you are allowing for larger requests, which can help prevent errors related to request size limitations.
3. Restart Remote Engine:
   • After making the configuration change, restart Remote Engine to apply the new settings.

Environment

• Talend Cloud 8.0.1
• Java version: 1.8
• Remote Engine Version: 2.12.13

An existing User Directory Connector (UDC) stopped working.

The following error is displayed:

The User Directory Connector (UDC) is not configured because the following error occurred. Setting up connection to LDAP root node failed. Check log file

Configuring an identical connector with the same parameters on another server is working fine.

When starting a sync, the following exception is thrown in the User Repository logs:

Repository.UserDirectoryConnectors.LDAP.GenericLDAP.GenerateUserQuery(String[] toFilterOn)?? at Repository.UserDirectoryConnectors.LDAP.GenericLDAP.SyncUsers(String[] usersToFilterOn)?? at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)?? at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)????Exception rethrown at [0]: ?? at System.Runtime.Remoting.Proxies.RealProxy.EndInvokeHelper(Message reqMsg, Boolean bProxyCase)?? at System.Runtime.Remoting.Proxies.RemotingProxy.Invoke(Object NotUsed,
 

Environments:

• Qlik Sense Enterprise on Windows 

LDAP filter strings are stored for UDC. If the LDAP filter is removed from the database (by using pgadmin, for example), leaving the string as a null value rather than an empty string, the Qlik Sense Services will not be able to correctly interact with the UDC anymore. 
 

Resolution:

1. Open the Qlik Sense Management Console
2. Navigate to User Directory Connectors
3. Open the UDC showing the symtomps
4. In the empty LDAP filter field, enter any values 
5. Confirm the changes

Adding alternative measures or dimensions to a chart is expected to immediately update the chart. However, Qlik Sense May 2024 requires a page refresh before any changes are reflected correctly.

Earlier versions of Qlik Sense are not affected.

Resolution

This is caused by QB-26786. 

Workaround:

Refresh the page.

Fix Version:

Upgrade to Qlik Sense Enterprise on Windows November 2024 or any later versions.

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-26786 for reference.

Environment

• Qlik Sense Enterprise on Windows May 2024, all patches

A third-party security scan detects HSTS as not being enabled in Qlik Replicate or Qlik Enterprise Manager, even if it has been correctly set up.

Example software used which returned a false fail: VAM Vulnerability Assessment/CUB

Resolution

Manually verify if HSTS is set up:

1. Open your browser's debug menu (For example in Google Chrome: press F12, or right-click and select Inspect)
2. Open the Network tab
3. Reload the page to capture network requests
4. Open the Headers tab
5. With a valid page selected, locate the Response Headers section
6. Find the Strict-Transport-Security header
   Example: 

   application-message:OK
   application-status:200
   cache-control:no-cache, no-store
   content-length:12
   content-type:application/json; charset=utf-8
   date:Tue, 13 Aug 2024 01:33:36 GMT
   server:Microsoft-HTTPAPI/2.0
   strict-transport-security:max-age=31536000; includeSubDomains
   x-content-type-options:nosniff
   x-xss-protection:1; mode=block

Cause

As Qlik Replicate and Qlik Enterprise Manager do not use IIS, some third-party tools cannot successfully verify HSTS.

Related Content

• Setting up HSTS on Qlik Replicate
• Setting up HSTS on Qlik Enterprise Manager

Internal Investigation ID(s)

00298442

Environment

• Qlik Replicate
• Qlik Enterprise Manager

"RestConnectorMasterTable" General Script Error in statement handling

RestConnectorMasterTable:
20200826T102106.344+0000 0088 SQL SELECT
20200826T102106.344+0000 0089 "name",
20200826T102106.344+0000 0090 "value"
20200826T102106.344+0000 0091 FROM JSON (wrap off) "contactCustomData"
20200826T102106.344+0000 0092 WITH CONNECTION (
20200826T102106.344+0000 0093 URL "      ",
20200826T102106.344+0000 0094 HTTPHEADER "Authorization" "**Token removed for security purpose**"
20200826T102106.344+0000 0095 )
20200826T102106.967+0000 General Script Error in statement handling
20200826T102106.982+0000 Execution Failed
20200826T102106.986+0000 Execution finished.

Environment

• Qlik Sense Enterprise on Windows February 2021

Resolution

To be able to catch the exact error and mitigate the issue they need to apply our recommended best practices for error handling in Qlik scripting using the Error variables
Error variables 
Script control statements 

Set to ErrorMode=0 it will ignore any errors and continue with the script. You can use the IF statement to retry the connection or move to another connection for a few attempts and then it will change it to ErrorMode=1 and fail or just disconnect on its own.

A sample script is located here, but further options can be added from the Help links already provided.
Qlik-Sense-fail-and-retry-connection-sample-script 

Note: QlikView scripting is the same in these functions for Qlik Sense unless otherwise stated, but there are some very helpful items in the links.
Best-Practice-Error-Handling-in-Script 

Cause 

Error with the fetch of the token with the rest call. If the number of rows in a table doesn't match or is less than expected, trigger the script to throw an error and have it try to load the table again for more records, or if the count is off, do a Loop until returns the correct number.

Internal Investigation ID(s) 

QB-3164

Talend Studio does not start and displays an error message:

An error has occurred. see the log file /studio/configuration/xxxxxxxx.log

The log files read:

!MESSAGE Application error !STACK 1 java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:81)     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)     at java.lang.reflect.Method.invoke(Method.java:498)     at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:659)     at org.eclipse.equinox.launcher.Main.basicRun(Main.java:595)     at org.eclipse.equinox.launcher.Main.run(Main.java:1501)

Cause

Cached values.

Resolution

To clear cached values and recreate certain configurations:

1. Close Studio and go to the Studio installation directory.
2. Open the configurations folder and delete the folders that begin with org. -- except org.talend.configurator.
3. Restart Studio.

If the issue persists, create a backup of your workspace, then switch to a new empty workspace and try to pull your projects again.

The documentation of Talend Data Catalog v8.1 states that：

In fact, HA deployment is only available on the MM most advanced edition as the license stored in the shared database must be enabled to support both the Active and Passive servers (obviously on different host ids).

To be more precise, only the "Advanced Plus" version (the Data Governance version in v8.1) supports HA mode.

Environment

• #Talend Data Catalog 8.1

Related  Content

Talend Data Catalog High Availability Considerations

By default, Qlik Replicate control tables like attrep_apply_exceptions or attrep_status are created in lower case. If you would like for those tables to be created in UPPERCASE on Snowflake as a target, please see below.

Starting in version 2021.5 service pack 02, there is an internal parameter called setIgnoreCaseFlag which if checked or set to true, will set the QUOTED_IDENTIFIERS_IGNORE_CASE to true.

Thus, letters in double-quoted identifiers are stored and resolved as uppercase letters.

For reference: https://docs.snowflake.com/en/sql-reference/parameters.html#quoted-identifiers-ignore-case

You can search for setIgnoreCaseFlag in the Advanced tab -> Internal Parameters for the Snowflake Target endpoint.

Environment

• Qlik Replicate 

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

Preparing a storage task fails with the following error:

Failed to prepare Data Task
Job finished with error. SQL compilation error: Object already exists as TABLE

The error will only occur if a task name includes Japanese Katakana characters. It does not fail when using English as the preferred language; only when using Japanese.

Environment

• Qlik Data Gateway version 2023.11.11

Resolution

This issue was caused by RECOB-8643 and has been resolved in the Qlik Data Gateway version 2024.5.7, along with any later releases. 

See the Release Notes for details.

Internal Investigation ID(s)

RECOB-8643

Upgrading Qlik Sense Enterprise on Windows (on-prem) fails. Reviewing the installer log files (see How To Collect Qlik Sense Installation Log File ) shows:

Error! Validation of: C:\Program Files\Qlik\Sense\\Client\1130.68f106588cb51d5970a9.js.LICENSE.txt failed: Could not find file 'C:\Program Files\Qlik\Sense\Client\1130.68f106588cb51d5970a9.js.LICENSE.txt'.

The environment previously used the Qlik PostgreSQL Installer to upgrade its bundled PostgreSQL database. 

Resolution

Verify if old Qlik Sense patches remained installed:

1. Open the Windows Control Panel 
2. Open Programs & Features 
3. Open View Installed Updates (menu on the left)
4. Locate an old Qlik Sense patch and click Uninstall 
   
   

If the Uninstall option does not work, manually uninstall it instead:

1. Open a Windows Explorer and navigate to C:\ProgramData\Package Cache
2. Open a command prompt (as an administrator) and move to the same path using the command: "cd C:\ProgramData\Package Cache"
3. Run the command "dir /s Qlik_Sense_update.exe"
4. A folder will be revealed. Open the folder in Windows Explorer. 
   
   Example:
   
   
   
   
5. Verify the folder includes Qlik_Sense_update.exe
6. Rename the folder. e.g. "9b21fde3-1245-4536-891f-e1d3965f3d0f_aaa"
7. Go back to the list of Installed Upgrades and click Uninstall on the Patch
   
   
   
   
8. Confirm the message with Yes
9. Upgrade Qlik Sense.

Cause 

A defect was observed if the Qlik PostgreSQL installer was previously used and old patches were not correctly removed by the installer. See the May 2023 Release Notes for QPI.

The error message appears when the installer is looking for the file which is no longer exists in the new version of the Qlik Sense.

Related Content 

Upgrading Qlik Sense Repository Database using the Qlik PostgreSQL Installer 

Environment

Qlik Sense Enterprise on Windows with Qlik PostgreSQL Installer used to upgrade PostgreSQL
Example: QPI was used to upgrade PostgreSQL on November 2022. November 2022 was then upgraded to February 2023. 

Internal Investigation ID(s) 

QB-17862

When the runtime network environment is strictly restricted and the network firewall exception cannot be opened for repo1.maven.org, it leads to unresolved jar dependencies, causing service deployment failure and generating "Unable to resolve xxx.jar" errors in <Talend Runtime Home>/log/tesb.log.

Resolution

Quick workaround

Download the jar locally and upload it to correct folder following maven2 structure, as Talend Runtime will use local maven cache to copy needed jars into <Talend Runtime Home>/system folder.

1. mkdir -p /home/talenduser/.m2/respository
2. Download the missing jar from https://repo1.maven.org to local and upload it to Talend Runtime.
3. Create the maven2 folder structure and copy the jar to the newly created folder.
4. Use bundle:install <group-id>/<artifact-id>/<version>
5. Redeploy the failed service.

Long-term Solution

For each jar download, use a centralized network control.

1. Setup a Nexus repository, such as "maven-central", which can mirror https://repo1.maven.org. This Nexus server must allowlist per https://repo1.maven.orgaccess
2. Add "http://admin:Talend123@nexusHost:8081/repository/maven-central, \" in org.ops4j.pax.url.mvn.cfg.
   vi Runtime/etc/org.ops4j.pax.url.mvn.cfg
   org.ops4j.pax.url.mvn.repositories= \ http://admin:Talend123@nexusHost:8081/repository/releases@id=tesb.release,\ http://admin:Talend123@nexusHost:8081/repository/snapshots@snapshots@id=tesb.snapshot, \ http://admin:Talend123@nexusHost:8081/repository/maven-central, \ https://repo1.maven.org/maven2@id=central

Then, Talend Runtime can use this mirror repo to access dependency jars.

Cause 

Strict network control from Talend Runtime server.

Environment

• Talend Data Integration 7.3.1, 8.0.1

The task was published from Talend Studio using Java 17. The project properties within Talend Studio is currently set to Java 17 compatibility mode, and the Remote Engine is also utilizing Java 17. Nevertheless, the execution summary of the task indicates that Java 8 is being used.

Cause

The environmental setting JAVA_HOME of the Remote Engine from which it run is set for Java 8 home path. Some servers require multiple Java environments and have the Remote Engine's JDK set in the <Remote Engine Installation Home>/bin/setenv or the <Remote Engine Installation Home>/etc/wrapper file. The Job launcher will take it's lead from JAVA_HOME, thereby causing the Job to execute with Java 8.

Resolution

1. Backup and edit the <Remote Engine Installation Home>/etc/org.talend.remote.jobserver.server.cfg file.
2. Set the java executable path org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH, for example:

   org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=/<JDK HOME>/bin/java

Environment

• Talend Data Integration 8.0.1

The internal parameter skipMscdcJobFitnessCheck implies that, if enabled, it will prevent or (skip) the Fitness Check from running. This is incorrect.

skipMscdcJobFitnessCheck controls the cdcJob portion of the Fitness Check. The Fitness Check itself will always run and cannot be stopped. Only the cdcJob check is skipped. 

This means that task log entries such as "Failed in MS-CDC fitness check" will not be addressed by enabling skipMscdcJobFitnessCheck. 

Environment

Qlik Replicate  
SQL Server MS-CDC

Related Content:

Qlik Replicate: MSSQL-CDC source endpoint to Snowflake. We are encountering the following error: Failed in MS-CDC fitness check 
Qlik Replicate: How to set Internal Parameters and what are they for?

Executing the Qlik Migration Tools leads to the following error on line 185 of 7_migrateapps.ps1:

Error: operation unsupported for server-type "cloud" (Qlik Cloud). Supported server-types are: ["windows"]

Example:

qlik context use $QlikWindowsContext | out-null

qlik qrs app export create $appid --skipdata $SS --exportScope all --output-file $exportAppFile

Resolution

Verify you have followed the required step-by-step configuration documented in Using qlik-cli with Qlik Sense Enterprise client-managed Repository API (QRS).

Specifically, do not forget to execute this cmd to add the Qlik Sense Enterprise on Windows server to qlik-cli. See Configure a context in qlik-cli for details.

Example:

##qlik context create QSEoW --server <server name> --server-type windows --api-key <JWT Token>

Cause

Possible causes:

• failed to specify --server-type windows
• executed the cmd against Qlik Cloud, not Qlik Sense Enterprise on Windows

Lines 184 and 185 test the connection as documented in Qlik-CLI: Test the connection and point to a misconfiguration of the context. 

Environment

• Qlik Cloud
• Qlik Sense Enterprise on Windows

By accessing the tenant of the Qlik Sense SaaS editions,  you may get the following error after trying to open an app.

"Unable to connect to the Qlik Sense engine. Possible causes: too many connections, the service is offline, or networking issues."

Environment

• Qlik Sense Enterprise SaaS
• Qlik Sense Business

Resolution

In the most common scenario, the error is related to an idle session timeout. If the error occurs after 20 min idle time, the only required action is to click "Refresh" in order to reconnect the client to Qlik Sense. 
For this scenario, a more user-friendly message is planned for future Qlik Cloud releases. 

It is recommended to try and establish if a network device between the browser and the Internet is causing the connection error if it occurs immediately or sooner than idle session timeout.

• Contact your local IT helpdesk for troubleshooting and advice.
  • Confirm that network components support Websocket connections to your tenant  <tenantname>.<region>.qlikcloud.com
  • Check if the device utilizes an Internet proxy for Internet access
  • Disable VPN if feasible

• Connect to Qlik Cloud tenant from a different device or network

  • Connect with a non-corporate device, to quickly identify if corporate policy is causing the issue
  • Access Qlik Download page as a test, if the tenant is not allowed from another device

• Check browser dev tools for more specific error messages

  • Search Qlik Support Knowledge for related articles and known issues 
  • Open Qlik Support ticket if the error can not be resolved and local IT can not find a root cause

Cause 

Qlik Sense uses WebSockets that enable communication between the web browser and Qlik Sense server. A Qlik Sense application gets generated with visualization objects and data via this communication.
The same technology is applied for web integration where Qlik Sense objects are embedded in other pages. 

The root cause of this error is that the browser's WebSocket connection has been terminated for various reasons;

• The most common scenario is that the session has been idle for 20 minutes, and session timeout has been reached in Qlik Sense engine. In such a case, the session will be restored by pressing "Refresh" in the error dialog. 
• The WebSocket connection may be terminated prematurely or blocked by a network device.
  • If the error occurs immediately when an app is accessed, it may indicate that WebSocket traffic is not allowed to pass through from the browser to the Internet.
    It may also indicate that multiple concurrent WebSocket connections are not allowed in all network devices between the browser and the Internet. 
  • If the error occurs a few seconds after the app has been successfully opened, it may indicate that the WebSocket connection is not allowed to be persistent in the network devices between the browser and the Internet.
    Qlik Sense requires persistent WebSocket connections, and also sends TCP keep-alive packages every ~30 secs to keep the connection open even when a user is not actively interacting with a Qlik Sense app. This keep-alive mechanism will not work if a network device has a lower connection timeout than 30 seconds. 
  • WebSocket connections use a different (WSS) protocol and port than normal (HTTPS) web traffic. Network devices between the browser and the Internet must support the use of the WebSocket protocol. 

Related Content 

• Qlik Sense Enterprise SaaS requirements / Qlik Sense Business requirements 
• How are WebSockets used in Qlik Sense? 
• How to troubleshoot web socket issue for Qlik Sense