The distribution of QlikView apps from QlikView Distribution Service to Qlik Cloud fails with the error "TestCloudLicense: Failed - Unauthorized. Failed to retrieve qv_nodes tag."

Environment

• QlikView 
• Qlik Cloud 

Resolution

• The license used in Qlik Cloud is missing the QV_NODES tag, which allows the access to QlikView apps from Sense Deployments. For QlikView to distribute to a Qlik Cloud tenant,  the tag must be present in the tenant license.

Please, reach out to your account manager to have that fixed.

• This issue could also occur if there are missing configuration entries in he QVDistributionService.exe.config  file, refer to the following article QlikView Distribute to cloud fails: The type initializer for System.IdentityModel.Tokens.Jwt.JsonExtensions threw an exception.

After submitting a question in Qlik Answers, the real-time reasoning output is not displayed while the question is being processed. The reasoning stepper, which normally shows the model’s step-by-step thinking in real time, is either missing or fails to load. The issue may occur intermittently and does not consistently reproduce across sessions or browsers.

Example:

Environment

• Qlik Cloud Analytics
• Qlik Answers

Cause

This is a client-side issue, rather than a defect in Qlik Answers, and is commonly caused by a browser extension.

Qlik Answers delivers its real-time reasoning output via a streaming HTTP response (Server-Sent Events / chunked transfer encoding). Browser extensions can interfere with this mechanism by intercepting, buffering, or suppressing streaming network traffic at the browser level. When any such extension disrupts the stream, the reasoning stepper never receives the data it needs to render.

Extension types known to cause this class of conflict include, but are not limited to:

• DRM and Media Proxy Extensions: Intercept low-level browser network requests to proxy DRM-protected media streams; inadvertently buffers non-media streaming responses.
• VPN and Proxy Extensions: Route all browser traffic through a proxy layer, introducing buffering that breaks Server-Sent Event connections.
• Advanced Ad and Content Blockers: Their network-level request filtering can strip or delay streaming response headers.
• Privacy and Anti-Tracking Extensions: May block or throttle requests classified as tracking-like, including persistent HTTP connections.
• Script Injectors and Page Modifiers: User scripts that intercept fetch or XMLHttpRequest can interfere with streaming response handling.
• Corporate Security and Endpoint Protection: Perform SSL inspection or traffic analysis that can break SSE streams.

Resolution

This article documents a solution for Google Chrome.

1. Verify whether an extension is the cause:
   
   
   1. Open Chrome and press Ctrl+Shift+N (Windows) or Cmd+Shift+N (Mac) to open an Incognito window.
   2. Navigate to Qlik Cloud and submit a question in Qlik Answers. As extensions are disabled by default in Incognito, the reasoning view appears. This confirms a browser extension as the root cause. 
      
      
2. Identify the conflicting extension:
   
   
   1. Navigate to the Chrome extensions page: chrome://extensions/
   2. Disable all extensions.
   3. Re-enable them one at a time, testing Qlik Answers after each, until the conflict is reproduced. Pay particular attention to extensions listed in the Cause section.
      
      
3. Once the conflicting extension is identified, choose one of the following:
   
   
   • Disable or remove the conflicting extension entirely, or
   • Allowlist Qlik Cloud in the extension’s settings.
     
     Most VPN, ad blockers, and security extensions support per-site exceptions that will resolve the conflict without requiring the extension to be removed.

If the issue persists after disabling all extensions:

The same class of interference can also be caused by corporate network proxies, SSL inspection appliances, or endpoint security agents operating outside the browser. If Incognito also fails to display the reasoning view, engage your IT or network security team to verify whether outbound Server-Sent Event connections to Qlik Cloud are being intercepted or buffered at the network level.

This conflict is not unique to Qlik Answers. Any web application that relies on Server-Sent Events or streaming HTTP responses may be affected by extensions or network components that proxy or intercept traffic at the browser level.

If you continue to experience issues after following the steps above, please open a support case and include the following:

• Browser version and operating system
• A full list of installed browser extensions
• Whether the issue reproduces in Incognito mode
• A screen recording showing the behavior

Related Content

• Answering questions with Qlik Answers | help.qlik.com
• Supported browsers for Qlik Cloud Analytics | help.qlik.com
• How to contact Qlik Support | Qlik Community

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

Content:

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

Requirements

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

Installation method One

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

      get-command qlik​

   3. Closer PowerShell

Installation Method Two

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

   choco install qlik-cli

4. This completes the installation.

Enable the Completion Feature (optional, but useful)

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

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

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

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

3. Save it. 
4. Restart PowerShell

Use Qlik-CLI

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

If your Qlik Talend Studio has Internet access, patches can be directly applied from within Qlik Talend Studio.

For details, see Setting up the Update URL of Talend Studio.

If your Qlik Talend Studio environment is not connected to the Internet, contact support for a download link to the required patch zip file, then follow the instructions in Qlik Talend Studio: How to add features or update Talend Studio Manually in Offline Mode?

Environment

• Qlik Talend Studio

• A user subscribes to a sheet or chart that references a variable.
• When the variable changes, the report is still delivered with the old value.
• The Qlik Sense app, on the other hand, shows the correct value when opened.

Environment

• Qlik Cloud 

Resolution

This is a current limitation.
Variables are among the settings that are only saved (as value, not as formulas) when the subscription is saved.

The subscription report will continue to use first value.

We have an improvement planned to include variables as formulas planned, but currently no precise ETA.

After upgrading Qlik Talend Studio to patch R2025-08 or later, jobs using the tS3Connection or tS3List components fail with the error:

Exception in component tS3List_1
java.lang.IllegalStateException: Connection pool shut down

Resolution

An additional change with the new SDK version is how the AWS "region" is handled. In Qlik Talend Studio R2025-07 and earlier, the Region and Endpoint field is shown as a dropdown below.

Using the DEFAULT value works for most cases:

With the new SDK 2.x, the region field is less flexible. The region must explicitly be defined to work correctly. To resolve connectivity issues after upgrading, it is best to explicitly define the AWS region used under the new Region text field:

Additional Information

• For all AWS regions, see: AWS service endpoints 
• We recommend also reviewing all details for tS3Connection in our help documentation as per tS3Connection | help.qlik.com

Cause

With the release of R2025-08, Qlik Talend Studio migrated AWS component dependencies from Amazon Web Services SDK version 1.x to SDK version 2.x. This move was prompted by SDK 1.x having reached end of life as of December 31, 2025.

The Amazon DynamoDB, Amazon SQS, and Amazon S3 components were all updated. For the full release notes, see R2025-08 Talend Studio 8.0 - New Features.

Environment

• Qlik Talend Studio

When using IBM DB2 for iSeries as a source in Qlik Replicate, the task may report a warning if journal receiver numbers are not continuous.

A typical warning message looks like:

[SOURCE_CAPTURE  ]W:  Journal entry sequence '2026' was read from journal receiver 'APSUPDB.QSQJRN0118'. The previous entry was read from receiver 'APSUPDB.QSQJRN0116'. Check if a receiver has been detached.  (db2i_endpoint_capture.c:1836)

Resolution

Qlik Replicate reports this condition as a warning only. There is no impact on task execution or data integrity:

• The task continues to run normally
• No journal entries are lost
• No data inconsistency is introduced

This warning can be safely ignored unless accompanied by other errors or abnormal task behavior.

Cause

On the IBM DB2 for iSeries side, 'Check if a receiver has been detached' can occur if, for example, the process is holding or locking the journal. This temporarily prevents the system from creating or attaching the next journal receiver. In such cases, a receiver number may be allocated but never successfully created, resulting in a gap in the receiver numbering.

This behavior is normal on IBM i and does not indicate a defect. The system assigns journal receiver numbers, but sequential continuity is not guaranteed. IBM i only guarantees that receiver numbers increase monotonically, not that every number will exist.

Internal Investigation ID(s)

00420963, 00423959

Environment

• Qlik Replicate
• IBM DB2 for iSeries all versions

When attempting to add an app to Qlik Answers, the error invalid logical model or other indexing errors appear, followed by the process hanging without further processing or simply erroring out. 

The behavior is the same in both user-based tenants and capacity-based tenants.

The app reloads normally when scheduled or when reloaded manually. This indicates there is no issue with the app itself, which is not exhibiting any errors performing typical analytics activity.

Resolution

If your app has existing business logic, your custom business logic may interfere with the expected Qlik Answers indexing preparation.

To resolve this:

1. Navigate to the Logical Model in your application
2. In the Overview tab, click Reset to default
   
   
   
3. Enable the app for Qlik Answers, which re-indexes the app
4. Reload the app
5. Ask a question

If changes are made to the logical model after performing the above steps, those changes will be reindexed automatically. Keep in mind that this re-indexing may take up to 24 hours.

Cause

In some instances, business logic may need to be reset or may not be consistent with best practices, preventing Qlik Answers from indexing the Qlik app. 

See Best practices for preparing applications for Qlik Answers for details.

Internal Investigation ID(s)

SUPPORT-8526

Environment

• Qlik Answers
• Qlik Cloud Analytics

Related Content

• How to prepare your Qlik App for Qlik Answers - Qlik Community - 2542848
• Best practices for preparing applications for Qlik Answers

Using DB2 LUW (ODBC) as a target with a replication of a text column, the following error may be encountered:

[TARGET_APPLY ]T: RetCode: SQL_ERROR SqlState: 42846 NativeError: -461 Message: [IBM][CLI Driver][DB2/AIX64] SQL0461N A value with data type "SYSIBM.LONG VARGRAPHIC" cannot be CAST to type "SYSIBM.TIMESTAMP". SQLSTATE=42846 [1022502] (ar_odbc_stmt.c:2864)

Resolution

The May 2026 version of Qlik Replicate contains a native DB2 LUW endpoint capable of processing the datatype correctly to prevent the error. 

Workaround

Remove any tables that have multiple Text columns.

Internal Investigation ID(s)

SUPPORT-8188

Environment

• Qlik Replicate

A partial reload fails when Applymap() is used in a load statement that is not part of the partial reload itself.

This affects any partial reloads.

This limitation can block the distribution list import in In-application reporting. In fact, when a distribution list is added by uploading a source file, a new section (Distribution List) is automatically generated in the application’s load script, and a partial reload for this session starts automatically. 

If Applymap() is used anywhere in the application script, the partial reload fails, and the recipient list can't be imported.

Resolution

This is currently considered expected behavior in Qlik Sense Enterprise on Windows and Qlik Cloud Analytics. There are possible workarounds to address partial reload failures.

If the problem is limited to In-application reporting, it is possible to run a full reload of the application from the HUB once the Distribution List session is generated in the app script. Notice that this may cause a consumption of resources that can be charged to the tenant.

A more general workaround is to conditionally ensure that certain operations are limited to the partial reload only, using a schema like this in the script:

if IsPartialReload() then
*****
here the script involving mapping and Applymap()
*****
else
***
the rest of the script
***
endif;

A similar approach is to use the partial reload prefix on the mapping table like:
"Mapping add LOAD". 

It may be necessary to work with conditions for operations like "drop field" in this case, dependent on whether the referenced field exists or not in the given reload context.
Here are two example scripts showing two possible methods.
 

Method One:

if IsPartialReload() then
Replace Load 'IsPartial' as Status autogenerate 1;
else
Load 'IsNormal' as Status autogenerate 1;
// Load mapping table of country codes:
map1:
mapping LOAD *
Inline [
CCode, Country
Sw, Sweden
Dk, Denmark
No, Norway];

// Load list of salesmen, mapping country code to country
// If the country code is not in the mapping table, put Rest of the world
Salespersons:
LOAD *,
ApplyMap('map1', CCode,'Rest of the world') As Country
Inline [
CCode, Salesperson
Sw, John
Sw, Mary
Sw, Per
Dk, Preben
Dk, Olle
No, Ole
Sf, Risttu
] ;

// We don't need the CCode anymore
Drop Field 'CCode';
endif;

Partial_reload_Data:
Add only LOAD * inline [
Salesperson, CCode
Pierre, Sw
Viggo, Sw ];

if IsPartialReload() then
Replace Load 'IsPartial' as Status autogenerate 1;
else
Load 'IsNormal' as Status autogenerate 1;
end if;

// Load mapping table of country codes:
map1:
mapping add LOAD *
Inline [
CCode, Country
Sw, Sweden
Dk, Denmark
No, Norway
] ;

// Load list of salesmen, mapping country code to country
// If the country code is not in the mapping table, put Rest of the world
Salespersons:
LOAD *,
ApplyMap('map1', CCode,'Rest of the world') As Country
Inline [
CCode, Salesperson
Sw, John
Sw, Mary
Sw, Per
Dk, Preben
Dk, Olle
No, Ole
Sf, Risttu
] ;

// We don't need the CCode anymore
if not IsPartialReload() then
Drop Field 'CCode';
end if;

Partial_reload_Data:
Add only LOAD * inline [
Salesperson, CCode
Pierre, Sw
Viggo, Sw ];

Cause

This behavior is due to a known limitation in Qlik Sense Enterprise on Windows and Qlik Cloud Analytics.

Internal Investigation ID(s)

QB-5181

Environment

• Qlik Sense Enterprise on Windows
• Qlik Cloud Analytics

When connecting to the Google Drive Spreadsheet connector, some date values are fetched as text.

For example, there is a date table like the following:

In the Data Load editor:

However, in the fetched results, the first two columns are returned as text:

Resolution

This is working as designed when using the Google Drive and Spreadsheet connector.

Two possible workarounds exist.

Use the Qlik Google Drive connector

1. Upload the spreadsheet to the Google Drive as an XLSX file, and use the Qlik Google Drive connector instead.
   
   
   
   
2. Use Select Data to fetch the data
   
   

Change the DateFormat in the load script

1. In the default script, you can find the following parameter set.
   
   
   
   
2. Change the format "M/DD/YYYY" to what you want to load, which is the same format as the spreadsheet.
3. Reload the script, and you will see the data is fetched in the proper date format.

Internal Investigation ID(s)

SUPPORT-8842

Environment

• Qlik Cloud

At Qlik Connect 2026 I hosted a session called "Fast 15" with my top 10 visualization tips. Here's the app I used with all tips including test data.

Tip titles, more details in app:

• Product Catalogue
  How to make a product catalogue. Here's a variant with the new Pivot table using inline SVG images. The product images have been converted to Base64 and inlined within the inline SVG. The text is just positioned on top of the image.
• Table waterfall with subtotal and partial sum
  How to make table waterfall with add bars, and bars for subtotal and retro sum. Spreadsheet for layout, rangesum() and above() for offset and bar, master measures and SVG for waterfall.
• Switches revisited
  How to make a switch. Create a variable vSwitch set value to 0 Use the button, to toggle the variable, use action "set variable"
• Button examples
  How to style a button. Examples of button styles.
• Map with 3d bars
  How make 3d bar map point layer. Use a simple SVG with two rects: the bar and the shadow in Data URI with inline SVG. Added a top and base triangle for a little extra 3d effect.
• Rank box chart
  How to make a rank box chart. Use unicode boxes and repeat().
• Filter pane examples
  How to place a filter pane. Example of top panel, side panel and drawer style.
• Half Gauge
  How to make a multi half gauge. Use the map and two line layers.
• Pie chart value and percentage in the same label
  How to customize pie chart labels. Use dual() and number format measure expression.
• Line chart symbols
  How to add symbols in the line chart. Use dual and unicode symbols.
• Control chart with combo chart
  How to make a control chart with dynamic bounds. Use combo and measures for center, upper and lower bounds
• Formatting x-axis and keep field
  How to format the x-axis. Use dual and aggr.

I want to emphasize that many of the tips were discovered by others than me, I tried to credit the original author at all places when possible.

If you liked it, here's more in the same style:

• 24 days of visualization Season III, II, I
• Top 10 Tips Part X, IX, VIII, VII, VI, V, IV, III, II , I 
• Let's make new charts with Qlik Sense
• FT Visual Vocabulary Qlik Sense version
• Similar but for Qlik GeoAnalytics : Part III,  II, I

Thanks,
Patric

In a Windows multi-node deployment, the App Distribution Service (ADS) distributes apps from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise SaaS. The service is installed on every node. However, Qlik Sense does not have load balancing for ADS, meaning if not all nodes have access to the apps, distribution may fail. See App Distribution from Qlik Sense Enterprise to Qlik Cloud fails when distributed from RIM NODE.

If you wish to disable app distribution from certain nodes:

1. Log on to Qlik Sense node on which you wish to disable App Distribution.
2. Stop the Qlik Sense Dispatcher Service.
3. Open the "C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf" file with Notepad or any text editors.
4. Find the  [appdistributionservice] section and the[hybriddeploymentservice] section. 
5. Disable both by setting it to Disabled=true.
   

   [appdistributionservice]
   Disabled=true
   Identity=Qlik.app-distribution-service
   DisplayName=App Distribution Service
   ExePath=dotnet\dotnet.exe
   UseScript=false
   
   [hybriddeploymentservice]
   Disabled=true
   Identity=Qlik.hybrid-deployment-service
   DisplayName=Hybrid Deployment Service
   ExePath=dotnet\dotnet.exe
   UseScript=false​

6. Save the file.
7. Restart the Qlik Sense Dispatcher Service.

Environment

• Qlik Sense multi-cloud environments. Any versions.

This article explains how to extract changes from a Change Store and store them in a QVD by using a load script in Qlik Analytics. 

The article also includes

• An app example with an incremental load script that will store new changes in a QVD
• Configuration instructions for the examples

Scenario

This example will create an analytics app for Vendor Reviews. The idea is that you, as a company, are working with multiple vendors. Once a quarter, you want to review these vendors.

The example is simplified, but it can be extended with additional data for real-world examples or for other “review” use cases like employee reviews, budget reviews, and so on.

The data model

The app’s data model is a single table “Vendors” that contains a Vendor ID, Vendor Name, and City:

Vendors:
Load * inline [
"Vendor ID","Vendor Name","City"
1,Dunder Mifflin,Ghent
2,Nuka Cola,Leuven
3,Octan, Brussels
4,Kitchen Table International,Antwerp
];

The Write Table

The Write Table contains two data model fields: Vendor ID and Vendor Name. They are both configured as primary keys to demonstrate how this can work for composite keys.

The Write Table is then extended with three editable columns:

• Quarter (Single select)
• Action required? (Single select)
• Comment (Manual user input)

Prerequisites

• A shared space
• A managed space (optional but advised for the tutorial)
• A connection to the Change-stores API to the Analytics REST connector in the shared space. A step-by-step guide on creating this connection is available in Extracting write table changes with the REST connector in Qlik Cloud.

Steps

1. Upload the attached .QVF file to a shared space
2. Open the private sheet Vendor Reviews
3. Click the Reload App (A) button and make sure data appears (B) in the top table
   

   
   

4. Go to Edit sheet (A) mode
5. Drag a Write Table Chart (B) on the top table, and choose the option Convert to: Write Table (C).
   
   This transforms the table into a Write Table with two data model columns Vendor ID and Vendor Name.
   
   
   

    

6. Go to the Data section in the Write Table’s Properties menu and add an editable column
   
   
   

    

7. This prompts you to define a primary key inside the table. Click Define (A) in the table and use both Vendor ID and Vendor Name as primary keys (B).
   
   You can also just use Vendor ID, but we want to show that this also supports composite primary keys.
   
   
   
   
   
   
8. Configure the editable column:
   
   
   • Title: Quarter
   • Show content: Single selection
   • Add options for Q1Y26 through Q4Y26.
     
     Tip! Also add an empty option by clicking the Add button without specifying a value.
     
     
     

      

9. Add another Editable column with the below configuration
   
   
   • Title: Action required
   • Type: Single select
   • Options:  Yes and No
     
     

     

10. Add another Editable column with the below configuration
    
    
    • Title: Review
    • Type: Single select
    • Options:  Yes and No
      
      
      
      
11. The Write Table is now set up.
    
    Go to the Write Table’s properties and locate the Change store (A) section. Copy the Change store ID (B).
    
    
    

     

12. Leave the Edit sheet mode. Then add changes for at least two records. Save those changes.
    
    
    

     

13. Go to the app’s load script editor and uncomment the second script section by first selecting all lines in the script section (CTRL+A or CMD+A) (A) and then clicking the comment button (B) in the toolbar.
    
    
    

     

14. Configure the settings in the CONFIGURATION part at the end of the load script
    
    
    

     

15. Update the load script with the IDs of the editable columns.
    
    The easiest solution to get these IDs is to test your connection. Make sure the connection URL is configured to use the /changes/tabular-views endpoint and uses the correct change store ID.
    
    
    

     

16. Copy and paste the example load script (for the editable columns only) and paste it in the app’s load script SQL Select statement that starts on line 159:
    
    
    

     

17. Replace the corresponding * symbols in the LOAD statement that starts on line 176:
    
    
    

     

18. Choose which records you want to track in your table by configuring the Exists Key on line 216.
    
    This key will be used to filter the “granularity” on which we want to store changes in the QVD and data model, as the load script will only load unique existing keys (line 235).
    
    
    • $(vExistsKeyFormula) is a pipe-separated list of the primary keys.
    • In this example, Quarter is added as an additional part of the exists key to keep track of changes by Quarter.
    • Optionally, this can be extended with createdBy and updatedAt to extend the granularity to every change made:
      
      
      

       

19. Reload the app and verify that the correct change store table is created in your data model. The second table in the sheet should also successfully show vendors and their reviews.

Environment

• Qlik Cloud Analytics

There is no need to sign any additional NDA statements when dealing with Support. Please see below 3 relevant policies that can be referred to if and when customers ask for specific NDA's before engaging with support.

1. Employment contracts: All employees (including Support) have signed employment contracts with confidentiality clauses in them.  Confidentiality clauses are the same as NDAs for this purpose.
2. Contract with the customer: The customer contract will say that any information passed from Qlik to the customer (and vice-versa) if it is confidential data, will be treated by the other party as confidential.
3. Qlik Handling of 3rd Party Data Policy: This policy reminds employees that customer data is confidential and summarizes the procedures to keep it confidential and safe (e.g. data retention rules).
    

Modern large language models that power advanced AI capabilities, such as Qlik Answers, require processing infrastructure that may not be available in every Qlik region. To provide our AI capabilities in as many regions as possible, Qlik Cloud now offers cross-region inference as an opt-in feature. You determine if available inference locations meet your data residency and compliance requirements.

Latest Update
March 9th, 2026

To deliver the best possible AI capabilities to our customers in Brazil, we are upgrading to modern AI models that require data processing across AWS commercial regions globally.

Starting 9th of April, data processing for Pipelines, API Designer, and Data Governance will move from Brazil-only to all AWS commercial regions.

Key highlights

• Regional compliance: Inference locations are tailored based on the underlying availability of AWS infrastructure.
• Transparency: Qlik provides at least 30 days' notice before any processing location changes

For complete details about inference locations for your region and data protection measures, see the full documentation available in Enabling cross-region inference.

Please subscribe to this article to receive updates to any inference location.

Environment

• Qlik Cloud

Installing Qlik Replicate 2025.5 and 2025.11 GA versions on Linux 9.7, an error may occur during installation or when attempting to start the services.

This issue is typically observed when the installation is performed using a different account than the one intended to run the services.

For example, installing Qlik Replicate with the account apsup while specifying qlik as the service account:

sudo user=qlik group=qlik verbose=true rpm -ivh --prefix /opt areplicate-2025.11.0-164.x86_64.rpm

A typical error message is:

arep.sh: created /opt/attunity/replicate/bin/areplicate
arep.sh: created /etc/systemd/system/areplicate.service
systemctl daemon-reload failed
failed to install areplicate as a service, areplicate will not be run
warning: %posttrans(areplicate-2025.11.0-164.x86_64) scriptlet failed, exit status 9  

Resolution

Upgrade your Qlik Replicate installation. This issue has been resolved in Qlik Replicate 2025.11 SP3 (2025.11.0.437 and later).

Internal Investigation ID(s)

00443949

Environment

• Qlik Replicate 2025.5
• Qliklik Replicate 2025.11 GA/SP1/SP2
• Linux 9.7

When using SAP HANA as a source in Qlik Replicate, Qlik Replicate does not fully handle the DECIMAL CS_DECIMAL_FLOAT datatype by default. This can lead to a loss of precision during replication.

For example, the value 345.56 in Hana replicated as 345 in Google BigQuery, a generic File target, or other target endpoints.

Assume we have a table defined as below:

create column table JOHNW.TESTDEC (
      ID integer not null primary key,
      name varchar(20),
      dec1 DECIMAL(38,4) CS_FIXED,
      dec2 DECIMAL CS_DECIMAL_FLOAT);
      
INSERT INTO johnw.testdec VALUES (1,'test',234.45,345.56);

Resolution

There are two possible solutions.

1. Use a VIEW with explicit casting, then replicate the VIEW instead of the original table in Qlik Replicate task:
      

   CREATE OR REPLACE VIEW johnw.testdec_view2 AS 
   SELECT 
    id,
    name,
    dec1,
    CAST(dec2 AS DECIMAL(30,4)) AS dec2
   FROM johnw.testdec;

   
   This ensures a fixed scale is applied before replication.
   
   This workaround works for a Full Load ONLY task.
        
2. Use source_lookup()
   
   Adding a column with datatype NUMERIC(30,4), the expression is:
   

   source_lookup('NO_CACHING','JOHNW','TESTDEC','DEC2','ID=:1',$ID)

   You may combine this with a CAST to enforce the desired precision or any other formatting.
   
   This workaround is effective for both Full Load and Change Processing; however, it requires the source to have a primary key or a unique index.
   
   The advantage is that no changes are needed in the source HANA database.
    

Cause

The DEC2 column is not a standard fixed DECIMAL.

• CS_FIXED → fixed precision/scale (e.g., DECIMAL(38,4))
• CS_DECIMAL_FLOAT → floating decimal (variable scale)

Qlik Replicate cannot handle it correctly by default in the current versions.

Environment

• Qlik Replicate all versions
• SAP Hana all versions