Pressing a button that executes an Automation fails with:

Bad request

An additional error may be shown:

You are not authorized to run this automation

These errors are typically seen after changing the Automation's owner. 

Resolution

Bad request

When the owner of an Automation is changed, the system automatically disables that Automation. In this context, this error indicates that the automation is disabled or that its run mode is incorrectly configured.

To resolve this:

• Ensure the Automation has its status set to Enabled (A)
  
  If it is set to Disabled, click the Actions (...) menu (B) to enable it.
  
  
  
  
• Verify the Automation's Run mode is set to Triggered. If the Automation is set to a different mode (such as Manual or Scheduled), the button will not be able to initiate it.
  
  
  1. Open your Automation and select the Start node
  2. In Inputs, verify Run Mode to be set to Triggered
     
     
     
     
     

You are not authorized to run this automation

This error can occur after re-enabling an automation and the execution token having changed.

Follow these steps to re-establish the connection:

1. Navigate to the sheet where the button containing the automation execution action is located.
2. Edit the sheet and locate the Actions and navigation pane.
3. Find the specific action configured to trigger the automation.
4. In the Automation section, remove the currently selected automation name.
   
   
   
   
5. Click Edit sheet to save this change. This signals the system that the automation link has been cleared.
6. Click Edit sheet and navigate back to the same Automation action.
7. Use the dropdown arrow in the Automation field to select the desired automation you want to be triggered.
8. Click Edit sheet to save the re-selected automation.
9. Verify that the button now successfully executes the automation without errors.

Environment

• Qlik Cloud Analytics
• Qlik Automate

Question

Does Qlik Stitch Support for Databricks Unity Catalog as a destination option?

We are learning that Databricks is requiring all customers migrate from Databricks Delta Lake to unity catalog.

So far, Qlik Stitch does not support Unity Catalog with Databricks as a destination option yet, and using it could result in loading errors or other problems.

Please submit a feature request for this by following the process outlined here. 

New-Process-for-Submitting-a-Feature-Request-for-All-Talend

Related Content

Databricks Delta Lake on AWS (v1) Data Loading Reference

Environment

• Talend Cloud 
• #Qlik Stitch

Images included in an Excel worksheet may appear stretched or use the wrong aspect ratio when previewed in an Excel report or after being distributed in an on-demand reporting task.

This affects charts imported by Qlik Sense as well as static images and shapes. 

Resolution

To fix the affected Qlik Reporting template, change the body font currently used in the Excel template to a supported font family:

1. Create a new Excel workbook or open an existing Excel template using Office Web or Excel
   Desktop
2. For each Excel worksheet contained in the Workbook, click on the worksheet’s top left
   corned or press Ctrl-A to select all the cells.
3. In the Excel ribbon bar, under the Home menu, choose a supported body font
   
   Supported fonts:
   
   
   • Andale Mono
   • Arial (Bold, Italic, Bold Italic)
   • Arial Black
   • Calibri (Bold, Italic, Bold Italic)
   • Calibri Light (Italic)
   • Cambria (Bold, Italic, Bold Italic)
   • Candara (Bold, Italic, Bold Italic)
   • Comic Sans MS (Bold)
   • Consolas (Bold, Italic, Bold Italic)
   • Constantia (Bold, Italic, Bold Italic)
   • Corbel (Bold, Italic, Bold Italic)
   • Courier New (Bold, Italic, Bold Italic)
   • Georgia (Bold, Italic, Bold Italic)
   • Impact
   • Times New Roman (Bold, Italic, Bold Italic)
   • Trebuchet (Bold, Italic, Bold Italic)
   • Verdana (Bold, Italic, Bold Italic)
   • Webdings
   • WenQuanYi Zen Hei
     
     More fonts could be supported in the future.
     
     
4. After changing your font, double-check the size of images added to the template (both static
   images and dynamic Qlik Sense charts). Font modification may have altered the image; if necessary, resize or re-add the image.

To prevent other related symptoms, set the main display zoom level to 100% when creating and editing an Excel template on the Windows platform. Note that this is a Windows OS setting and not the Zoom set within the Excel App.

Cause

An unsupported font is used in the current Qlik Reporting template. 

Internal Investigation ID(s)

SUPPORT-3842, QCB-32146

Environment

• Qlik Cloud Analytics
• Qlik Reporting

You may be experiencing an error " No import token found for connection" or the error "CRITICAL Error saving list of discovered streams: {'message': 'Not Authorized'}" when running extractions on Stitch integrations.

Integration will run fine and extraction jobs will not error out, however there no data is loading and in the extraction logs you will see the above error.

Resolution

In order to resolve this, you will need to create a new integration as that establishes a new connection with a new import_token. 
If the version of this integration is deprecated, creating a new integration will automatically use the latest version.
Upgrading the integration using the upgrade button (if one is available) or creating a new integration is the only path forward at this point to get your integrations running again.

Creating a new integration with a different schema name is recommended because you will benefit from a free historical re-sync of your data.

Cause

What is happening here is that this integration was created some years ago, and internally there is a token that expired. Specifically, the import_token for connections created over 5 years ago will expire at that 5 year time period and Stitch do not automatically generate a new import token. As a result, you will see this message in extractions.

Related Content

If you prefer to re-use the same destination schema name when creating a new integration, please refer to this article:

Qlik-Stitch-How-to-Upgrade-the-Integration-to-Latest-Version

Environment

• Talend Cloud 
• #Qlik Stitch

Unique Index not found for SAP Hana version 2.0 SPS 7 in Qlik Replicate. This version of SAP Hana reports the index type as "INVERTED VALUE" instead of "INVERTED VALUE UNIQUE" in SAP Hana.

This change in SAP has no direct impact, but other indirect changes have caused Qlik Replicate to be unable to find the Unique Indexes of tables from the table metadata for the SAP Hana source endpoint.

The missing Unique Indexes for the tables cause disruptions to the CDC process, as updates can not be applied without the Unique Index.

Resolution

This defect (SUPPORT-372) has been resolved in the early Service Pack 3 for Qlik Replicate 2024.11.

Contact Qlik Support for access to the early Service Pack build.

Internal Investigation ID(s):

Product Defect ID: SUPPORT-372

Environment

• Qlik Replicate

Opening QlikView Documents from the AccessPoint directly in the QlikView Desktop leads to the document being launched with the wrong (AJAX) client.

Previously, documents would automatically launch with qvp:// and use the Desktop client as the default.

Clicking the View details link lists only three clients:

Ajax client, Internet Explorer plugin, Mobile client

Previous versions would list the QlikView desktop client:

Resolution

This behavior was changed between 12.70 and 12.80. To reenable the previous default:

1. Open QlikView Desktop
2. Go to Settings
3. Go to User Preferences
4. In the License section, click Clear License Information
5. Close the QlikView Desktop
6. Open a Windows File Explorer and go to %USERPROFILE%\AppData\Roaming\QlikTech\QlikView
7. Open settings.ini
8. Modify the settings.ini by adding the line SupportLeaseLicenseForDMSMode=1 below the [Settings 7] section
   
   Example:
   
   [Settings 7]
   SupportLeaseLicenseForDMSMode=1
   .... other settings ....
   
   
9. Save the changes to the settings.ini
10. Open QlikView Desktop and open the AccessPoint; any documents will now open directly with QVP://accesspoint/path/documents.qvw.

If the steps did not succeed:

• Verify that you cleared the license beforehand
• Verify if SupportLeaseLicenseForDMSMode=1 is still present in %USERPROFILE%\AppData\Roaming\QlikTech\QlikView\settings.ini
  The settings.ini file may have been overwritten by a different version of QV.exe that was active while the changes were made. If this is the case, close all QV.exe instances and repeat the steps.

Internal Investigation ID(s)

QCB-32143

Environment

• QlikView 12.80 and later

In Talend tDBInput component,  CLOB data types can not be handled properly when you are attempting to ingest data from source DB2 to Target one.

This article briefly introduces how to properly handle CLOB data types when ingesting from DB2 to Target using Talend.

How To

1. Write a Utils class ClobUtils with the method getClobAsString under Code-> Global Routines
   You can create your own routines according to your particular factorization needs.
   For more information, please check qlik Help Documentation about: Creating user routines
2. Use this Utils in tMap/tJavaRow component : ClobUtils.getClobAsString(row1.C1)
   You can call any function in any of the system and user routines from your Job components in order to run them at the same time as your Job. Please check Help Documentation about: Calling-routine-function-from-job

The code below is a scratch version that needs testing and rewriting.

Use this as an example to study:

==Example code: ===
package routines;
import java.sql.Clob;
import java.sql.SQLException;
import java.util.logging.Level;
import java.util.logging.Logger;
import org.apache.commons.io.IOUtils;
package routines;
import java.sql.Clob;
import java.sql.SQLException;
import java.util.logging.Level;
import java.util.logging.Logger;
import org.apache.commons.io.IOUtils;
import java.io.IOException;
import java.io.InputStream;
import java.io.StringWriter;
import java.lang.String;
public class ClobUtils {
    public static String getClobAsString(Object obj) {
        String out = null;
        if (obj != null && obj instanceof Clob) {
            out=getClobAsString((Clob) obj);
        } else {
            Logger.getLogger("ClobUtils").log(Level.FINE, "null value");
        }
        return out;
    }
    public static String getClobAsString(Clob clobObject) {
        String clobAsString = null;
        if (clobObject != null) {
            long clobLength;
            try {
                clobLength = clobObject.length();
                if (clobLength <= Integer.MAX_VALUE) {
                    clobAsString = clobObject.getSubString(1, (int) clobLength);
                } else {
                    InputStream in = clobObject.getAsciiStream();
                    StringWriter w = new StringWriter();
                    IOUtils.copy(in, w, "UTF-8");
                    clobAsString = w.toString();
                }
            } catch (SQLException e) {
                e.printStackTrace();
            } catch (IOException e) {
                e.printStackTrace();
            }
        }
        return clobAsString;
    }
}

Related Content

• https://stackoverflow.com/questions/2169732/most-efficient-solution-for-reading-clob-to-string-and-string-to-clob-in-java
  
  
• https://www.baeldung.com/java-string-character-large-object-conversion

Environment

• Talend Studio 
• Talend Data Integration 

When a user authenticates with SAML/JWT/Ticket, security rules based on the attributes from the SSO provider do not work and the attributes are not visible in the QMC under the User record.

Environments:

• Qlik Sense Enterprise, all versions

When a user authenticates with SAML, a list of attributes will be given to Qlik Sense based on what is set up in the virtual proxy.  The attributes depend on the implementation.

However, these User attribute(s) returned from the SSO provider are only kept for the user session and are not stored/persisted in the Qlik Sense Repository Database. Therefore, they do not appear in the QMC like attributes synchronized via a UDC connection (data which is persisted to the database).
 

Resolution:

1. Reference the attributes via user.environment.[attribute name] (not user.[attribute name])
2. View the exact attributes returned from the SSO provider by examining the logs:
   
   
   1. Set the Proxy Audit Logs to the DEBUG level
      
      
   2. After enabling debug logging, the (Trace/Audit) Proxy logs will reveal the extracted attribute(s). No restart is required. 
      
      The default location for this log is in C:\ProgramData\Qlik\Sense\Log\Proxy\Trace\servername_Proxy_audit.txt
      
      Example Headers that will be injected:
      
      [X-Qlik-Security, OS=Windows; Device=Default; Browser=Firefox 50.0; IP=fe80::f0bf:12cb:47cd:2086%14; ClientOsVersion=6.3; SecureRequest=true; Context=AppAccess; role=Domain+Users; role=group5; ] || [X-Qlik-User, UserDirectory=DOMAIN; UserId=user5] || [X-Qlik-ProxySession, b29118dd-4539-4742-ad65-fe307eb10b54] || [X-Qlik-ProxyId, ProxyId=38daa8e0-5330-4581-9f40-49d7418b858f; Prefix=adfs] || [X-Qlik-Trace, cf2e0117-ee82-4d26-bba8-b781fc4ef19e:::]

The central proxy virtual proxy cannot be deleted and virtual proxy prefix are unique per proxy.

Environments:

• Qlik Sense Enterprise on Windows 

Resolution:

In order to change to remove the prefix for a different virtual proxy to use another authentication method by default:

1. in the QMC, go to "Virtual proxies" > "Central proxy (default)"
2. Modify the virtual proxy prefix to the desired string
3. Click "Apply" in order to save
4. Go back to "Virtual proxies", double-click on the virtual proxy that you want to make default in order to edit it.
5. Remove the virtual proxy prefix
6. Click "Apply" in order to save

Note: If the virtual proxy made default is using SAML authentication, the SAML Assertion Consumer Service URL will also need to be updated in the Identity Provider configuration.

This article explains how the Qlik Reporting connector in Qlik Application Automation can be used to generate a bursted report that delivers recipient-specific data.

For more information on the Qlik Reporting connector, see this Reporting tutorial.

This article offers two examples where the recipient list and field for reduction are captured in an XLS file or a straight table in an app. Qlik Application Automation allows you to connect to a variety of data sources, including databases, cloud storage locations, and more. This allows you to store your recipient lists in the appropriate location and apply the concepts found in the examples below to create your reporting automation. By configuring the Start block's run mode, the reporting automations can be scheduled or driven from other business processes.

Contents

• Using a straight table as a distribution list
• Using an Excel File as a distribution list

Using a straight table as a distribution list

In this example, the email addresses of the recipients are stored in a straight table. Add a private sheet to your app and add a straight table to it. This table should contain the recipients' email address, name, and a value to reduce the app on. We won't go over the step-by-step creation of this automation since it's available as a template in the template picker under the name "Send a burst report to email recipients from a straight table".

Instead, a few key blocks of this template are discussed below.

1. List Values Of Field. This block will return a list of all values of the specified field. The selected field should directly map to the recipient scope of data to be delivered. For each value, a report will be generated and distributed to the recipients who have that value assigned in the distribution list. We'll call this value the scope of the report, an example field could be Region to build a report for each different region and delivery to regional employees.
   
   
2. The Create Report block and attached blocks will then be executed for each unique value of the field. Tip: you can dynamically name your reports by mapping the current field's value to the Report name parameter of the Create Report block:
   
   
   
   
3. Add any sheets to the report by using the Add Sheet to Report block. Use the block Add Selection To Sheet to add selections. Add at least a selection for the current scope of the report. Also, apply a selection to the app using the Select Field Value block. This will reduce the straight table that contains the distribution list to the current scope.
   
   
4. Now, use the block Get Straight Table Data and configure it to retrieve the distribution list. The important step here is to append each email address from the distribution list to a string variable. Also, add a semicolon ';' to the field to separate the email addresses. 
   
   
   
   
5. The scope from the distribution list should be used to add a sheet to the report and apply a selection for the current recipient. For example, if the recipients are sales reps, this could be used to provide an overview of each recipient's individual sales.
   
   
   
   
6. Use the Generate Report block to finalize the report. Map this block's output to the attachment parameter of the Send Mail block. Map the string of email addresses to the To input field of the Send Mail block.
   
   
   
   
7. Then make sure to execute the block Unlock Selections to allow the selections to be overwritten for the next report scope. Also, empty the email addresses from the string variable to make sure they aren't persisted for the next scope.
   
   

Helpful tips

1. The Output block can be used to keep track of the automation's progress by showing the current scope.
2. When building the report automation, you can test the email output by sending the report to yourself before using the distribution variable for operational execution.
3. It's also possible to use the Copy File block from the Cloud Storage connector to store a copy of the report on any file storage system like Dropbox or SFTP. 

Using an Excel File as a distribution list

In this example, the email addresses of the recipients are stored in an Excel file. This can be a simple file that contains one worksheet with headers on the first row (name, email & a value for reduction) and one record on each subsequent row. 

1. The first step is to gather the Excel file's item id. This can be retrieved from the URL when the file is open in a browser window or by executing the List Items In Root Folder Of Drive block. Execute this block in a test run to fetch these records.
   
   
   
   
2. The results from the test run can now be used in other blocks, click the Item Id input field of the List Rows WIth Headers block and select the id key from the right item in the output returned by the List Items In Root Folder Of Drive block. 
   
   
   
   
3.  Further configure the  List Rows With Header block by specifying the worksheet name and the dimensions of the data (header row included). Below is an example of the excel file shown at the beginning of this section.
   
   
   
   
4. The other steps of the automation are similar to the first part of this article so they won't be repeated here. Optionally, values from the Excel file can be used for reducing the report with the block Add Selection To Report. 
   
   

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.

Watch this space for when the feature has been successfully rolled out in your region.

This capability is being rolled out across regions over time:

1. May 5th: India, Japan, Middle East, Sweden (completed)
2. June 4th: Asia Pacific, Germany, United Kingdom, Singapore (completed)
3. June 9th: United States (completed)
4. June 12th: Europe (completed)
5. TBD: Qlik Cloud Government

With the introduction of shared automations, it will be possible to create, run, and manage automations in shared spaces. 

Content

• Allow other users to run an automation
• Collaborate on existing automations
• Collaborate through duplication
• Extended context menus
• Context menu for owners:
• Context menu for non-owners:
• Monitoring
• Administration Center
• Activity Center
• Run history details
• Metrics

Allow other users to run an automation

Limit the execution of an automation to specific users.

Every automation has an owner. When an automation runs, it will always run using the automation connections configured by the owner. Any Qlik connectors that are used will use the owner's Qlik account. This guarantees that the execution happens as the owner intended it to happen.

The user who created the run, along with the automation's owner at run time, are both logged in the automation run history.

These are five options on how to run an automation:

1. Run an automation from the Hub and Catalog
   
   
   
   
2. Run an automation from the Automations activity center
   
   

    

3. Run an automation through a button in an app
   
   You can now allow other users to run an automation through the Button object in an app without needing the automation to be configured in Triggered run mode. This allows you to limit the users who can execute the automation to members of the automation's space.
   
   More information about using the Button object in an app to trigger automation can be found in How to run an automation with custom parameters through the Qlik Sense button.
   
   
4. Programmatic executions of an automation
   
   
   1. Automations API: Members of a shared space will be able to run the automations over the /runs endpoint if they have sufficient permissions.
   2. Run Automation and Call Automation blocks
      
      
5. Note for triggered automations: the user who creates the run is not logged as no user specific information is used to start the run. The authentication to run a triggered automation depends on the Execution Token only.

Collaborate on existing automations

Collaborate on an automation through duplication.

Automations are used to orchestrate various tasks; from Qlik use cases like reload task chaining, app versioning, or tenant management, to action-oriented use cases like updating opportunities in your CRM, managing supply chain operations, or managing warehouse inventories.

Collaborate through duplication

To prevent users from editing these live automations, we're putting forward a collaborate through duplication approach. This makes it impossible for non-owners to change an automation that can negatively impact operations.

When a user duplicates an existing automation, they will become the owner of the duplicate. This means the new owner's Qlik account will be used for any Qlik connectors, so they must have sufficient permissions to access the resources used by the automation. They will also need permissions to use the automation connections required in any third-party blocks. 

Automations can be duplicated through the context menu:

As it is not possible to display a preview of the automation blocks before duplication, please use the automation's description to provide a clear summary of the purpose of the automation:

Extended context menus

• Start a run from the context menu in the hub
• Duplicate automation
• Move automation to shared space
• Edit details (owners only)
• Open in new tab (owners only)

Context menu for owners:

 

Context menu for non-owners:

 

 

Monitoring

The Automations Activity Centers have been expanded with information about the space in which an automation lives. The Run page now also tracks which user created a run.

Note: Triggered automation runs will be displayed as if the owner created them.

Administration Center

The Automations view in Administration Center now includes the Space field and filter.

The Runs view in Administration Center now includes the Executed by and Space at runtime fields and filters.

Activity Center

The Automations view in Automations Activity Center now includes Space field and filter.

Note: Users can configure which columns are displayed here.

The Runs view in the Automations Activity Center now includes the Space at runtime, Executed by, and Owner fields and filters.

In this view, you can see all runs from automations you own as well as runs executed by other users. You can also see runs of other users's automations where you are the executor.

Run history details

To see the full details of an automation run, go to Run History through the automation's context menu. This is also accessible to non-owners with sufficient permissions in the space.

The run history view will show the automation's runs across users, and the user who created the run is indicated by the Executed by field.

Metrics

The metrics tab in the automations activity center has been deprecated in favor of the automations usage app which gives a more detailed view of automation consumption.

You may be experiencing a pattern of the Binlog error like below when extracting data from MySQl Integrations in Stitch.

Fatal Error Occurred - Binlog has expired for tables

The problem always stems from how did you configured certain parameters in your AWS RDS instance due to a lack of explicit specification.

As MySQL Integrations can be configured with AWS RDS instances, for MySQL integrations that are configured in this way, it means the requirements for the Binary Log Retention Period differs from that of standalone MySQL instances and this can cause issues if the Binary Log Retention Period is incorrectly or insufficiently configured.

Resolution

The Binary Log Retention Period should be configured to a value of 168 hours or 7 days. 
Running call

call mysql.rds_set_configuration('binlog retention hours', 168)

or

call mysql.rds_set_configuration('binlog retention hours', 7) 

will fix the issue.

Cause

The Binary Log Retention Period is controlled by AWS RDS which functions differently and independently of a standalone MySQL instance.

If the Binary Log Retention Period is set to 0, this will cause issues.

Related Content

There is a RDS specific stored procedure that governs bing log retention beyond traditional MySQL parameters given in the case.

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/mysql-stored-proc-configuring.html

Environment

• Talend Cloud 
• Qlik Stitch

This article provides step-by-step instructions to ensure your Talend Studio environment no longer uses the flagged spring-core-5.3.33.jar file and instead uses the updated spring-core-6.1.14.jar. It also explains how to verify your job builds are free of the old JAR.

Steps to remove the flagged JAR and confirm the update 

These steps are only necessary in cases where Qlik Talend Studio did not remove the old jar when applying the relevant patch (2025-02 or newer).

1. Verify the Updated JAR in Qlik Talend Studio:
   
   
   1. Open Qlik Talend Studio
   2. Go to the Modules view
   3. Search for spring-core
   4. Confirm that spring-core-6.1.14.jar is installed and marked as active
      
      
2. Remove the Old JAR from Your Studio Environment
   
   Once you’ve confirmed the new version is active, you can remove the old JAR:
   
   
   1. Navigate to the following example path (adjust accordingly if your installation directory differs):
      
      C:\TalendStudio8_install\studio\configuration\.m2\repository\org\springframework\spring-core\5.3.33.jar
      
      
   2. Delete spring-core-5.3.33.jar from this location

      Create a backup copy of the JAR before deletion, in case you need to restore it later.

3. Check your Job Builds
   
   When you build a job in Qlik Talend Studio, all required JAR files are packaged into a ZIP archive.
   
   
   1. Locate the lib folder inside the archive
   2. Check if spring-core-5.3.33.jar is present
      • If not present: No further action is needed
      • If present: Rebuild the job using your patched (2025-02) version or newer of Qlik Talend Studio to ensure only the updated JAR is included
        
        
4. Restart Qlik Talend Studio to ensure all updates take effect

Additional Notes

• Qlik Talend Studio may re-download JARs from a shared repository (such as Nexus) if configured. If you use a shared repository, ensure the old JAR is also removed or blocked there to prevent re-import.
• For projects using version control or shared resources, coordinate with your team to avoid accidental reintroduction of the old JAR.

Troubleshooting

• If the old JAR reappears after deletion, check if your project is configured to pull dependencies from a shared repository. Remove or block the flagged JAR in that repository as well.
• If you encounter errors after removing the JAR, confirm that no jobs or custom code still reference the old version.

Environment

• Qlik Talend Studio

Cannot log in to Qlik Talend Administration Center. Login fails with:

Error: 500, The call failed on the server; see server log for details

The log file reports:

ERROR SqlExceptionHelper - The MySQL server is running with the LOCK_WRITE_GROWTH option so it cannot execute this statement

Resolution

Expand cloud storage for MySQL or perform a data cleanup to free up the space required.

Cause

Cloud MySQL has reached the cloud storage quota during data writes. 

Environment

• Qlik Talend Administration Center

Using a Signed License Key with its Signed License Definition in a long term offline environment past the 90 days provided by Delayed Sync requires (besides license modification) additional configuration steps!

• No license has long term offline capability enabled by default. 
• Long term offline capability needs to be specifically approved by Qlik and the conditions of offline use agreed to by the customer. See Request license off-line approval - April 2020 and onwards. Once approval has been obtained through the CSO, the license will be modified with an additional attribute OFFLINE;YES;;
• Additional configuration changes are necessary for long term offline mode to function
• (Delayed Sync requires a Signed License Definition, but does not require additional configuration steps)

Configuration changes needed:

These changes will need to be done on all nodes running the Service Dispatcher. Not only the Central node. 

1. Stop the ServiceDispatcher service
   
   
2. As Administrator, open the Service Dispatcher services.conf file.
   
   Default location Qlik Sense on-prem: C:\Program Files\Qlik\Sense\ServiceDispatcher
   Default location QlikView: C:\Program Files\QlikView\ServiceDispatcher
   
   
3. Locate [Licenses.parameters]and add the parameter -offline 
   
   Example:
   
   [licenses.parameters]
   -qsefw-mode
   -offline
   -app-settings="..\Licenses\appsettings.json"
   
   
   
   The displayed order is required in the February 2024 IR release. Previous and future versions (Patch 2 and later) do not have a fixed order requirement.
   
   
4. Save the file
   
   
5. Start the ServiceDispatcher service

Once the changes has been done you will need to retrieve the updated SLD key from https://license.qlikcloud.com/sld and then apply the same for successful offline activation.

Note on upgrading: If using a version of Qlik Sense prior to November 2022, this file may be overwritten during an upgrade.  Please be sure to re-apply this parameter and restart the Service Dispatcher on all nodes after an upgrade. With Qlik Sense November 2022 or later, custom service settings are by default kept during the upgrade. See Considerations about custom configurations. 

Internal Investigation ID(s):

QB-25231

The Permissions requirements for Google Pub/Sub as a target state:

pubsub.subscriptions.create on the containing Cloud project (only required if you want Replicate to create a default subscription per topic when no subscription exists).

See Prerequisites.

However, the Pub/Sub endpoint does not offer a parameter allowing the subscription name to be specified.

Resolution

The subscription must follow the same naming convention, which involves appending the "-sub" suffix to the topic name. For example, if the topic name is "mytopic," the subscription name must be "mytopic-sub."

Cause

Qlik Replicate checks for subscriptions that follow a specific naming convention. For example, if the topic name is "mytopic," the subscription name must be "mytopic-sub." Qlik Replicate only recognizes subscriptions that adhere to this naming format.

Environment

• Qlik Replicate

A Qlik Replicate task may fail or encounter a warning caused by Data Inconsistencies when using Oracle as a source.

Example Warning:

]W:  Invalid timestamp value '0000-00-00 00:00:00.000000000' in table 'TABLE NAME' column 'COLUMN NAME'. The value will be set to default '1753-01-01 00:00:00.000000000'  (ar_odbc_stmt.c:457)
]W:  Invalid timestamp value '0000-00-00 00:00:00.000000000' in table 'CTABLE NAME' column 'COLUMN NAME'. The value will be set to default '1753-01-01 00:00:00.000000000'  (ar_odbc_stmt.c:457)

Example Error:

]E: Failed (retcode -1) to execute statement: 'COPY INTO "********"."********" FROM @"SFAAP"."********"."ATTREP_IS_SFAAP_0bb05b1d_456c_44e3_8e29_c5b00018399a"/11/ files=('LOAD00000001.csv.gz')' [1022502] (ar_odbc_stmt.c:4888) 00023950: 2021-08-31T18:04:23 [TARGET_LOAD ]E: RetCode: SQL_ERROR SqlState: 22007 NativeError: 100035 Message: Timestamp '0000-00-00 00:00:00' is not recognized File '11/LOAD00000001.csv.gz', line 1, character 181 Row 1, column "********"["MAIL_DATE_DROP_DATE":15] If you would like to continue loading when an error is encountered, use other values such as 'SKIP_FILE' or 'CONTINUE' for the ON_ERROR option. For more information on loading options, please run 'info loading_data' in a SQL client. [1022502] (ar_odbc_stmt.c:4895)

Resolution

The bindDateAsBinary attribute must be removed or set on both endpoints. 

Cause

The parameter bindDateAsBinary means the date column is captured in binary format instead of date format.

If bindDateAsBinary is not configured on both tasks, the logstream staging and replication task may not parse the record in the same way.

Environment

• Qlik Replicate

After upgrading to Qlik Sense Enterprise on Windows May 2024 SR1, the Data Lineage information of <CreatorDoc></CreatorDoc> is empty for all QVDs created using the Store script function.

Example: 

STORE * FROM Transactions INTO C:\QlikDocuments\Dev\Transactions.qvd ;

Resolution

Workaround:

Specify the format (qvd) in the STORE command. 

Example:

STORE * FROM Transactions INTO C:\QlikDocuments\Dev\Transactions.qvd (qvd);

Read more about the syntax in Store.

Fix Version:

Qlik aims to release a fix in the next possible service 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 SUPPORT-4149 for reference.

Cause

Product Defect ID: SUPPORT-4149

Environment

• QlikView May 2024 SR1

When doing a false migration update, you want a new branch based on the good commit id to start again. 

This article briefly introduces how to create a New Branch from a Commit before the faulty Migration Update

How to

1. Install Git Bash (if not already installed)
   https://git-scm.com/downloads
2. Identify the correct commit to revert to
   • Open the commit history of the affected file, for example:
     http://abc.com/project/talend.project
   • Look for the commit where the productVersion was updated, and find the commit SHA-1 id right before the false commit from the commit history.
   • Find the SHA-1 hash of the last good commit before the incorrect migration.
3. Create a new branch from that commit and sync it to Git server
   Run the following commands in your terminal:

   git clone http://abc.com/project.git
   cd project
   git checkout -b newBranchName <sha1-of-good-commit>
   git push -u origin newBranchName

These above steps will create and push a new branch starting from the commit just before the incorrect migration was introduced.

Environment

• Talend Studio 
• Talend Data Integration 

The problem occurs when working with a generic ODBC connection (DSN) for Qlik Data Gateway Direct Access. While the connection to the database can be established, a table preview fails with:

Command fields returned non-success: The driver used does not comply with the general database column specification. Returned columns metadata does not contain COLUMN_SIZE, DECIMAL_DIGITS.

Resolution

The driver in use does not fulfill the requirements and must be updated.

Qlik support suggests contacting the driver provider and asking to update it in order to make it compatible with the Qlik Data Gateway requirements.

If possible, try a different, supported driver to connect to the data source.

Cause

The error message indicates the drive in use is based on ODBC 2.x. This is not compatible with Qlik Data Gateway, which only supports ODBC 3.x. See ODBC (via Direct Access gateway).

For additional information on the difference in metadata column names between ODBC 2.x and ODBC 3.x, see SQLProcedureColumns Function, specifically the table documenting the SQLProcedureColumns changes. 

Internal Investigation ID(s)

SUPPORT-3489

Environment

• Qlik Cloud Analytics
• Qlik Data Gateway Direct Access