Featured Content
-
How to contact Qlik Support
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical e... Show MoreQlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
- Support and Professional Services; who to contact when.
- Qlik Support: How to access the support you need
- 1. Qlik Community, Forums & Knowledge Base
- The Knowledge Base
- Blogs
- Our Support programs:
- The Qlik Forums
- Ideation
- How to create a Qlik ID
- 2. Chat
- 3. Qlik Support Case Portal
- Escalate a Support Case
- Phone Numbers
- Resources
Support and Professional Services; who to contact when.
We're happy to help! Here's a breakdown of resources for each type of need.
Support Professional Services (*) Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. - Error messages
- Task crashes
- Latency issues (due to errors or 1-1 mode)
- Performance degradation without config changes
- Specific questions
- Licensing requests
- Bug Report / Hotfixes
- Not functioning as designed or documented
- Software regression
- Deployment Implementation
- Setting up new endpoints
- Performance Tuning
- Architecture design or optimization
- Automation
- Customization
- Environment Migration
- Health Check
- New functionality walkthrough
- Realtime upgrade assistance
(*) reach out to your Account Manager or Customer Success Manager
Qlik Support: How to access the support you need
1. Qlik Community, Forums & Knowledge Base
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
The Knowledge Base
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
- Go to the Official Support Articles Knowledge base
- Type your question into our Search Engine
- Need more filters?
- Filter by Product
- Or switch tabs to browse content in the global community, on our Help Site, or even on our Youtube channel
Blogs
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)Our Support programs:
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.The Qlik Forums
- Quick, convenient, 24/7 availability
- Monitored by Qlik Experts
- New releases publicly announced within Qlik Community forums (click)
- Local language groups available (click)
Ideation
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation GuidelinesHow to create a Qlik ID
Get the full value of the community.
Register a Qlik ID:
- Go to register.myqlik.qlik.com
If you already have an account, please see How To Reset The Password of a Qlik Account for help using your existing account. - You must enter your company name exactly as it appears on your license or there will be significant delays in getting access.
- You will receive a system-generated email with an activation link for your new account. NOTE, this link will expire after 24 hours.
If you need additional details, see: Additional guidance on registering for a Qlik account
If you encounter problems with your Qlik ID, contact us through Live Chat!
2. Chat
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
- Answer common questions instantly through our chatbot
- Have a live agent troubleshoot in real time
- With items that will take further investigating, we will create a case on your behalf with step-by-step intake questions.
3. Qlik Support Case Portal
Log in to manage and track your active cases in the Case Portal. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
Your advantages:
- Self-service access to all incidents so that you can track progress
- Option to upload documentation and troubleshooting files
- Option to include additional stakeholders and watchers to view active cases
- Follow-up conversations
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Problem Type
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
Priority
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
Severity
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
Escalate a Support Case
If you require a support case escalation, you have two options:
- Request to escalate within the case, mentioning the business reasons.
To escalate a support incident successfully, mention your intention to escalate in the open support case. This will begin the escalation process. - Contact your Regional Support Manager
If more attention is required, contact your regional support manager. You can find a full list of regional support managers in the How to escalate a support case article.
Phone Numbers
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
- Qlik Data Analytics: 1-877-754-5843
- Qlik Data Integration: 1-781-730-4060
- Talend AMER Region: 1-800-810-3065
- Talend UK Region: 44-800-098-8473
- Talend APAC Region: 65-800-492-2269
Resources
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
Recent Documents
-
Binary load fails with General Script Error when using app binary instead of .qv...
A binary load command that refers to the app ID (example Binary[idapp];) does not work and fails with: General Script Error or Binary load fails with ... Show MoreA binary load command that refers to the app ID (example Binary[idapp];) does not work and fails with:
General Script Error
or
Binary load fails with error Cannot open file
This is observed after upgrading to Qlik Sense Enterprise on Windows November 2024 Patch 8, and any later releases.
It was previously possible to do binary loads from app binaries without the .qvf file extension (GUID number file name). With recent releases, Qlik is enforcing an already existing restriction, meaning the QVF file extension is now required. See Binary Load and Limitations for details.
This is working as designed and is intended as a security measure.
Example of a valid binary load:
LIB CONNECT TO 'DataFiles';
LOAD * FROM [YourFile.qvd];Example of an invalid binary load:
"Binary [lib://Apps/777a0a66-555x-8888-xx7e-64442fa4xxx44];"
Environment
- Qlik Sense Enterprise on Windows November 2024 Patch 8 and any later releases
-
Qlik Replicate and Microsoft SQL Server (MS-CDC) source Endpoint: How to Startup...
In certain scenarios, you may need to restart a Qlik Replicate task from a previously saved stream position, specifically a known LSN or SCN, rather t... Show MoreIn certain scenarios, you may need to restart a Qlik Replicate task from a previously saved stream position, specifically a known LSN or SCN, rather than reload the entire task. This guide provides step-by-step instructions on how to resume a Microsoft SQL Server (MS-CDC) task from a stored stream position.
Steps to Start a Task from a Stored Stream Position
- Locate the Previous Stored Stream Position
Open the task log file and search for the final saved stream position. You should see an entry like the following:
[SORTER ]I: Final saved task state. Stream position 000000D8000062D00003:0:2147483647, Source id 12, next Target id 37, confirmed Target id 33, last source timestamp 1748932926987000 (sorter.c:777)
In this example, the relevant stream position is: 000000D8000062D00003 - Start the Task from This Position
- In the Qlik Replicate Console, open the relevant task
- Navigate to Task Settings --> Advanced Run Options
- Choose Tables are already loaded. Start processing changes from
- Choose Source change position (e.g. SCN or LSN) and enter the previously located Stream Position (000000D8000062D00003)
- Validate in the Task Log
After starting the task, check the log file to confirm that the task is starting from the specified stream position:
[TASK_MANAGER ]I: Task 'SQL-to-SQL__MS-CDC' running CDC only in fresh start mode, starting from log position: 'position:000000D8000062D00003'. (replicationtask.c:1847)
This confirms that Qlik Replicate is correctly picking up from the desired point in the transaction log.
Notes
- This method applies specifically to tasks using Microsoft SQL Server (MS-CDC) as the source.
- It is useful in scenarios such as resuming a failed task, reprocessing a limited set of changes, or disaster recovery testing.
- Always validate the stream position against the source database's current log retention to ensure the LSN is still available.
Environment
- Qlik Replicate, all versions
- SQL Server, all supported versions
- Locate the Previous Stored Stream Position
-
How to disable the App Distribution Service (ADS) on a machine in a multinode en...
In a Windows multi-node deployment, the App Distribution Service (ADS) distributes apps from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise... Show MoreIn 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:
- Log on to Qlik Sense node on which you wish to disable App Distribution.
- Stop the Qlik Sense Dispatcher Service.
- Open the "C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf" file with Notepad or any text editors.
- Find the [appdistributionservice] section and the[hybriddeploymentservice] section.
- 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
- Save the file.
- Restart the Qlik Sense Dispatcher Service.
Environment
- Qlik Sense multi-cloud environments. Any versions.
-
Qlik Talend Product: How to Request Migration Token for Talend
As of Talend 7.0, each project item saved in Talend Studio receives a unique digital signature. This signature is crucial for ensuring the integrity o... Show MoreAs of Talend 7.0, each project item saved in Talend Studio receives a unique digital signature. This signature is crucial for ensuring the integrity of the items, as it is validated when importing them into Talend Studio. Any item with an invalid signature will be rejected, serving as a safeguard against unauthorized modifications.
Following these steps will help you effectively request assistance with migration token and migration queries. If you have any further questions, feel free to reach out to the respective teams.
Steps to Request Assistance
- Gather Necessary Information
Before requesting a migration token, you need to gather necessary Information and provide details of the existing license, such as the name of the account associated with the migration token request, License Name and provide a brief description of your query regarding migration tokens and migration.
Ensure all details are accurate and complete before sending your request.
- Create a support case to request Migration Token
If you need a migration token for your Talend products, please open a case over the Qlik Customer Support Portal. As our support agent need to generate the token via Migration Token Approver, you have to request this over a case submitted through the Qlik Customer Support Portal.
Related Content
setting-migration-token-in-talend-studio
Environment
- Gather Necessary Information
-
Qlik Talend Product: A ESB Route fails to deploy with Error "xxx is likely to be...
A ESB route is failing to deploy with error message" xxx is likely to be incompatible with this Talend Runtime version, try recompiling the route with... Show MoreA ESB route is failing to deploy with error message" xxx is likely to be incompatible with this Talend Runtime version, try recompiling the route with a newer Talend Studio version".
ERROR | Blueprint Event Dispatcher: 1 | b.CompatibilityBlueprintListener 73 | 332 - deployer-interceptor - 8.0.1.<Monthly Patch>-RT | Bundle cifmessagequeue.<Route Name> id : <Karaf> is likely to be incompatible with this Talend Runtime version, try recompiling the route with a newer Talend Studio version
Resolution
Ensure Runtime and Studio are at the same version and patch level.
As this issue may be occurring due to Camel 3 is out of support, please try to move up to Camel 4 to see if it get resolved.
In order to do so, please upgrade to the following versions:
- Talend Studio - R2025-02 or later
- Talend Runtime - R2025-02 or later
- Jobserver - R2025-01 or later
If you have built ESB route jobs using Talend Studio R2025-01 or previous versions which use Camel 3, please rebuild them in Talend Studio R2025-02 or later versions which use Camel 4.
Cause
This error indicates the Runtime Server and Talend Studio version are incompatible. The recent Camel upgrade for 2025-02 and beyond may be the issue.
Talend Runtime 8.0.1-R2025-02 (Camel 4) is available as a complete installation package, this version supports only Routes and Data Services artifacts built with Talend Studio R2025-02 or later. Artifacts built with previous Studio versions are incompatible. This is due to the Camel 4 and Java 17 compiler changes that have been updated to both Runtime and Studio.
Please check if both Studio and Runtime server are patched to the same version.
Related Content
For more information about upgrade, please refer to below Qlik Talend Release Notes
https://help.qlik.com/talend/en-US/release-notes/8.0/r2025-02-studio
https://help.qlik.com/talend/en-US/release-notes/8.0/r2025-02-talend-runtime
Environment
-
Qlik Sense Migration Tools: Error operation unsupported for server-type "cloud" ...
Executing the Qlik Migration Tools leads to the following error on line 185 of 7_migrateapps.ps1: Error: operation unsupported for server-type "cloud"... Show MoreExecuting 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
-
Qlik Replicate: Query timeout expired
A Qlik Replicate task fails with error Query timeout expired Resolution The error occurs when Qlik Replicate is working on a query to the source or ta... Show MoreA Qlik Replicate task fails with error
Query timeout expired
Resolution
The error occurs when Qlik Replicate is working on a query to the source or target and the query takes longer than anticipated, leading to the timeout.
Edit the source or target endpoint and within the Advanced properties and add a new Internal Parameter named cdcTimeout.
- Stop the task.
- Open source or target endpoint depending on the error from the query source or target and add the following Internal Parameter:
cdcTimeout (default 600); (some endpoints do not have this value)
executeTimeout (default 60)
loadTimeout (default 1200).
Try 10x the default value. Values are in seconds.
See Qlik Replicate: How to set Internal Parameters and what are they for? for more information. - Save the endpoint
- Try to resume task and see if we still have a timeout issue.
Environment
-
Qlik Replicate SAP Hana Source Oracle Target CDC its replicated as empty string
During the initial load, if a field is empty in SAP, it correctly replicates as a space in Oracle. However, during CDC, it is being replicated as an ... Show MoreDuring the initial load, if a field is empty in SAP, it correctly replicates as a space in Oracle. However, during CDC, it is being replicated as an empty string, which is incorrect.
Resolution
Correcting this behavior requires the Internal Parameter alwaysReplaceEmptyStrings to be disabled on the Oracle Target. alwaysReplaceEmptyStrings is enabled by default.
- Go to the Oracle Target Endpoint connection
- Switch to the Advanced tab
- Click Internal Parameters
- Search alwaysReplaceEmptyStrings and untick the checkbox
For more information on Internal Parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?
Environment
- Qlik Replicate
-
Qlik Replicate and Microsoft SQL Server (MS-CDC): SELECT failed because the foll...
When using Microsoft SQL Server (MS-CDC) as a source in Qlik Replicate, and the "Capture DDL events" option is enabled in the endpoint’s Advanced sett... Show MoreWhen using Microsoft SQL Server (MS-CDC) as a source in Qlik Replicate, and the "Capture DDL events" option is enabled in the endpoint’s Advanced settings, an error may occur when attempting to create a new table in the source database after the task has run once.
The following error is typically returned in SQL Server Management Studio (SSMS):
Msg 1934, Level 16, State 1, Procedure attrep_mscdc_ddl_catcher, Line 23 [Batch Start Line 17] SELECT failed because the following SET options have incorrect settings: 'ANSI_PADDING'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations.
Resolution
SET ANSI_PADDING OFF in T-SQL and the ANSI_PADDING OFF database option are deprecated. In SQL Server 2017 (14.x) and later versions, and Azure SQL Database and Azure SQL Managed Instance, ANSI_PADDING is always set to ON. Deprecated features shouldn't be used in new applications.
For more details, refer to the official documentation: SET ANSI_PADDING (Transact-SQL)
Qlik Replicate does not support the use of SET ANSI_PADDING OFF. It is recommended to avoid using deprecated features in user scripts.
Recommended Workarounds
Disable "Capture DDL events"
Before running the task for the first time, disable the "Capture DDL events" option in the endpoint's Advanced settings.
Temporarily Disable the DDL Trigger (Not recommended for production environments)
You can temporarily disable the trigger before running user scripts, and then re-enable it afterward. However, this approach is risky and not recommended for production systems.
A sample:
DISABLE TRIGGER attrep_mscdc_ddl_catcher ON DATABASE;
GO
SET ANSI_PADDING OFF
GO
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[Test](
[Column1] [int] NULL,
[Column2] [int] NULL
)
GO
ENABLE TRIGGER attrep_mscdc_ddl_catcher ON DATABASE;
GOCause
The DDL trigger attrep_mscdc_ddl_catcher, which is created when "Capture DDL events" is enabled, enforces certain SET options such as:
SET ANSI_NULLS ON;
SET QUOTED_IDENTIFIER ON;However, if a user attempts to run scripts with SET ANSI_PADDING OFF, it results in a conflict.
Internal Investigation ID(s)
00346063
Environment
- Qlik Replicate
-
Qlik Replicate on Linux: High System Memory Usage
When Qlik Replicate runs on a newly provisioned Linux server, the system memory usage is abnormally high and reaches critical thresholds. Resolution... Show MoreWhen Qlik Replicate runs on a newly provisioned Linux server, the system memory usage is abnormally high and reaches critical thresholds.
Resolution
To resolve the issue, reduce or disable huge page allocation by updating the kernel parameter:
vm.nr_hugepages = 0To make it persistent across reboots, update /etc/sysctl.conf. Then apply the change by "sudo sysctl -p"
Cause
The issue is related to the Linux kernel parameter vm.nr_hugepages, which defines the number of huge pages (typically 2 MB each) that are pre-allocated in memory.
In this case, the system was configured with:
vm.nr_hugepages = 24629
This reserves approximately 48 GB of memory (2M * 24629) for huge pages, significantly reducing the amount of available memory for other processes. If too many huge pages are reserved, the system may run low on regular memory pages, leading to performance degradation or instability.
Internal Investigation ID(s)
00352619
Environment
- Qlik Replicate, all versions
- Linux Server, all supported versions
-
Qlik Sense Enterprise on Windows: SAP Connector using Standard mode generates th...
When installing the Qlik SAP Connector in Qlik Sense, the following connectors typically will not be installed: Report connector, Query connector, OLA... Show MoreWhen installing the Qlik SAP Connector in Qlik Sense, the following connectors typically will not be installed: Report connector, Query connector, OLAP connector, and DSO connector.
They are present when installing the Qlik SAP Connector for QlikView.
Comparison with QlikView on the right and Qlik Sense on the left:
In previous versions of Qlik Sense, it was recommended to manually set up these connectors in Qlik Sense Standard mode. However, security fixes implemented in December 2024 (read more in High Security fixes for Qlik Sense Enterprise for Windows (CVE-2024-55579 and CVE-2024-55580)) lead to custom connectors in Qlik Sense Standard mode to fail.
Example error:
Error: Connector QvSAPxxxConnector.dll not found
Resolution
Contact Qlik Support to discuss possible workarounds.
Internal Investigation ID(s)
QCB-31029 (SUPPORT-566)
Environment
- Qlik SAP Connectors
- Qlik Sense Enterprise on Windows
-
Qlik Talend: Permission denied when executing a job that was built as a Docker i...
The following error is found when executing a task that was built as a Docker image and accessing the directory using System.getProperty("user.dir"). ... Show MoreThe following error is found when executing a task that was built as a Docker image and accessing the directory using System.getProperty("user.dir").
Caused by: java.io.FileNotFoundException: /file/directory (Permission denied)
The error was not found in Talend 7.3, but after migrating to Talend 8.0, the issue exists.
Regarding building a job as a Docker image, further details can be found here: Building a Job as a Docker image.Resolution
Use a directory that has public permission, such as: System.getProperty("java.io.tmpdir")
Cause
Directory permission changes between Talend 7.3 and Talend 8.0 for the maven directory.
Environment
- Qlik Talend Studio
-
Error exporting task from Qlik Enterprise Manager: loadTimeout cannot be greater...
Exporting a task from Qlik Enterprise Manager fails with: SYS-E-DESERIALERR, Failed to deserialize JSON to type ReplicationDefinitionExport: SYS-E-GT,... Show MoreExporting a task from Qlik Enterprise Manager fails with:
SYS-E-DESERIALERR, Failed to deserialize JSON to type ReplicationDefinitionExport: SYS-E-GT, LoadTimeout cannot be greater than 86400.
The task can be successfully exported from Qlik Replicate.
Resolution
To resolve this issue, follow these steps to remove the invalid loadTimeout parameter and re-import the task:
- Export the Task from Qlik Replicate
- Open Qlik Replicate
- Locate the failing task
- Export the task to a JSON file using the UI
- Edit the Exported JSON File
- Open the exported .json file in a text editor (such as Notepad++, VS Code)
- Locate the following line under the target endpoint section:
"loadTimeout": 144000, - Delete the entire loadTimeout line
- Delete the original task from the Qlik Replicate UI to prevent conflicts
- Import the modified task
- Import the task to Qlik Replicate using the Import Task functionality (see Importing Tasks for more information)
- Select the modified JSON file
- Confirm that the task imports successfully without errors
Cause
The error is caused by an internal parameter, loadTimeout, which is set on the task’s target endpoint. This value exceeds the maximum allowed limit of 86400 seconds (24 hours).
This parameter is not set in the Qlik Replicate UI, but is added by manually editing the task’s JSON file.
Environment
- Qlik Enterprise Manager
- Export the Task from Qlik Replicate
-
Qlik ODBC Connector Package log analyzer app
The Qlik ODBC Connector Package log analyzer app is an easy-to-set-up app meant to assist in troubleshooting ODBC Connector issues for Qlik Sense Ente... Show MoreThe Qlik ODBC Connector Package log analyzer app is an easy-to-set-up app meant to assist in troubleshooting ODBC Connector issues for Qlik Sense Enterprise on Windows (on-prem).
This short guide documents how to configure and use the app in your own environment for both analysis and learning purposes.
Content
Requirements
To get as much information as possible and leverage the app at its fullest, set the following two log settings in the QvOdbcConnectorPackage.exe.config file. The file is typically found in C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage.
- LoggingLevel set to ALL
- LogSQLStatements set to true
Setup
- Download the Qlik ODBC Connector Package log analyzer app, either from the article directly or from our file share.
- Import the Qlik ODBC Connector Package log analyzer app to your Qlik Sense environment
- Open the app from the hub
- Go to the Data Load Editor
- Open the config tab
- Define a lib connection for your ODBC connector package log file
- Reload the Qlik ODBC Connector Package log analyzer app
App Content
The first sheet opens with aggregated information and KPIs.
What you will find here:
- Connector Package version
- ApplicationId: The applications using the ODBC Connector Package connectors
- Logging Level: The applied ODBC Connector Package logging level
- HostName
- Start time: The start timestamp of the logging
- End time: The end timestamp of the logging
- Date: The logged dates
- UserId: The logged user IDs
- Count of errors and Count of warnings: The number of logged errors and warnings
- Connector activity during the day: A chart showing during what time ODBC connectors have been used
- Connector activity by days: A chart showing during which days ODBC connectors have been used
- Max query data size reloaded: KPI showing the maximum data size reloaded by an executed query within a logged reloadID
- Max query reload time: KPI showing the maximum time of all the logged and executed queries
- Data source usage: A table showing the count of connections, count of used apps, count of errors, and the sum of the data size of all reloaded data by data source
- Command pipe: A list of all command pipes. Command pipes are the basis for an ODBC Connector Package activity. A command pipe is created every time the Data Load Editor is opened and the ODBC connections are loaded, as well as when a new ODBC connection is created, if a connection test is performed, and when data is previewed or reloaded.
- RequestId: A command pipe can have different kinds of request IDs. For more details, see the Connector process details section.
- Num command pipes: The number of command pipes
- Number of apps: The total number of apps using some form of ODBC connection
The first sheet also shows additional details supplementing the initial charts and KPIs.
What you will find here:
- Connector process details: Filtering by a specific Command pipe allows for an overview of all messages and requests for that specific command pipe sorted by timestamp
- Database and connection string details: A table showing the type of data source, database version (if available), and the used connection string
- Overview of reload executions: A table showing which SQL statements have been executed in which request and command pipe. Also contains other details, such as timestamps, query time, reloaded data size, data source, rows fetched, etc...
The second sheet begins with a summary of errors and warnings.
What you will find here:
- A list of errors, warnings, and exceptions by command pipe and sorted by timestamp.
- The exact message and which app has been impacted
Following the error analysis, the app lists information about Advanced parameters and connection details.
What you will find here:
- The connection details are broken down by connection string parameters and can be filtered by command pipe. This allows you to review which reload used which connection string parameters and advanced parameters.
The last section of the second sheet displays table field details.
What you will find here:
- Data type information by executed SQL query, command pipe, application ID, and data source.
The Qlik ODBC Connector Package log analyzer app is provided as-is. No ongoing support will be provided by Qlik Support. For questions and to engage with your active Qlik peers on the subject, head over to Management & Governance.
Environment
- Qlik ODBC Connector Package
- Qlik Sense Enterprise on Windows
-
Qlik Sense Enterprise on Windows: How to change Logging level for QvWebStoragePr...
This article explains how to change the log level for the QvWebStorageProviderConnector in Qlik Sense Enterprise on Windows. Always back up .config fi... Show MoreThis article explains how to change the log level for the QvWebStorageProviderConnector in Qlik Sense Enterprise on Windows.
Always back up .config files before making changes.
To change the log level of your QvWebStorageProviderConnectorPackage to debug mode:
- Browse to %Program Files%Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage
- Locate deploy.config
- Open deploy.config file in a text editor with elevated permissions (Administrator)
- Locate the <LoggingLevel> section:
<!-- Valid values: Off, Error, Warn, Info, Trace - We would recommend you have at least Error set.
-->
<LoggingLevel>Info</LoggingLevel> - Change the field Info to Trace
Example:<LoggingLevel>Trace</LoggingLevel>
- Save the file
- Restart all Qlik Sense services
Environment
- Qlik Sense Enterprise on Windows
-
Introducing Automation Sharing and Collaboration
This capability is being rolled out across regions over time: May 5: India, Japan, Middle East, Sweden TBD: Asia Pacific, Germany, United Kingdom, Si... Show MoreThis capability is being rolled out across regions over time:
- May 5: India, Japan, Middle East, Sweden
- TBD: Asia Pacific, Germany, United Kingdom, Singapore
- TBD: United States
- TBD: Europe
- TBD: Qlik Cloud Government
[Update: May 7] The previously-scheduled rollouts of Automation Sharing and Collaboration for some regions have been temporarily postponed. We are working on an updated release plan and updated release dates are soon to be determined (TBD). Thank you for your understanding.
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:
- Run an automation from the Hub and Catalog
- Run an automation from the Automations activity center
- 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. - Programmatic executions of an automation
- Automations API: Members of a shared space will be able to run the automations over the /runs endpoint if they have sufficient permissions.
- Run Automation and Call Automation blocks
- 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
With this new delivery, we have also added new options in the automation context menu:- 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.
-
Qlik Replicate: Seeing too many "[SOURCE_CAPTURE ]T: TXN operation 'ROLLBACK' se...
This article addresses a common concern where users observe frequent ROLLBACK operations in the logs when using IBM DB2 LUW as a source in data replic... Show MoreThis article addresses a common concern where users observe frequent ROLLBACK operations in the logs when using IBM DB2 LUW as a source in data replication or change data capture (CDC) environments. These messages may appear alarming at first, but they are typically part of the database's normal transaction handling process.
Understanding why these rollbacks occur and how they impact system performance can help reduce confusion and improve monitoring strategies.
Content
- Prerequisites
- Step-by-Step Instructions
- Step 1: Understand the Nature of ROLLBACK Operations
- Step 2: Why You See Frequent ROLLBACK Messages
- Step 3: Impact on Performance and Latency
- Step 4: Best Practices for Monitoring and Optimization
- Common Issues and Solutions
- Conclusion
- Related Content
Prerequisites
Before proceeding, ensure the following:
- Basic understanding of database transactions and replication concepts.
- Access to:
- DB2 LUW logs
- Replication
- Administrative privileges on the source database (for log access and configuration)
Step-by-Step Instructions
Step 1: Understand the Nature of ROLLBACK Operations
- A ROLLBACK is a standard database operation used to undo uncommitted changes.
- In systems like Order Entry, a transaction may be initiated (e.g., adding an order) but not committed.
- If the transaction is later canceled, DB2 issues a rollback to revert the changes.
Step 2: Why You See Frequent ROLLBACK Messages
- These messages are generated when Qlik Replicate captures rollback events from the DB2 transaction logs.
- Rollbacks are especially common in high-transaction environments where temporary or test entries are frequently created and discarded.
Step 3: Impact on Performance and Latency
- Rollbacks can increase the volume of log data that needs to be processed.
- This may introduce latency in replication tasks, especially if:
- Many transactions are rolled back in a short time.
- The rollback spans multiple tables or large datasets.
- Additional transaction logs generated during rollback can also slow down log reading and processing.
Step 4: Best Practices for Monitoring and Optimization
- Monitor the frequency of rollbacks using DB2 monitoring tools or SQL queries on the transaction log.
- Review application logic to ensure transactions are committed or rolled back efficiently.
- If rollbacks are excessive and unexpected, investigate application behavior or consider tuning transaction handling.
Common Issues and Solutions
Issue: High latency in replication tasks
Solution: Check for excessive rollback activity and optimize transaction handling in the source application.Issue: Concern over data integrity due to rollbacks
Solution: Rollbacks are part of the normal process and ensure consistency. No action is needed unless they are unusually frequent.Issue: Large volume of logs generated
Solution: Consider adjusting log retention policies or archiving strategies to manage disk usage.Conclusion
Frequent ROLLBACK messages in DB2 LUW are typically a normal part of transaction management, especially in dynamic systems with frequent data changes. While they can contribute to replication latency, they are essential for maintaining data integrity. Monitoring and understanding these operations can help you better manage system performance.
Related Content
- IBM DB2 LUW Documentation
- IBM CDC (Change Data Capture) Overview
- Best Practices for DB2 Transaction Logging
Environment
- Qlik Replicate
-
Qlik Talend Product: ERROR ExecutionTaskHandler -/Talend/Administrator/generated...
You might be encountering the following issue on the Talend Administration Center UI (Job Conductor page) when deploying a task after upgrading or app... Show MoreYou might be encountering the following issue on the Talend Administration Center UI (Job Conductor page) when deploying a task after upgrading or applying a Talend Administration Center patch
Error: ERROR ExecutionTaskHandler - /Talend/Administrator/generatedJobs/task****.zip (No such file or directory)
Resolution
Please verify the 'Generated Jobs' folder on the Talend Administration Center Application
- If the folder is missing, create the appropriate path and configure it in the Job Conductor configuration page.
- If the folder exists but lacks the necessary permissions, ensure that write permissions are granted.
Cause
This error occurs when the path to the 'Generated Jobs' folder configured in the Job Conductor is missing or has insufficient permissions.
Environment
-
Qlik Stitch: How to Request SOC 2 Audit Report from Stitch?
This article briefly introduces how to request SOC 2 audit report from Stitch As Stitch has been certified compliant with the SOC 2 (System and Organi... Show MoreThis article briefly introduces how to request SOC 2 audit report from Stitch
As Stitch has been certified compliant with the SOC 2 (System and Organization Controls 2) security, availability, and confidentiality principles by an independent auditor, the audit report can be requested by contacting the Sales team.
You will need to fill out the form below, and our Sales Team will connect with you to obtain the SOC 2 report.
https://www.stitchdata.com/contact/
If you are not getting a response on time, please feel free to contact Qlik Support to get your account representative's details How to contact Qlik Support
Related Content
For more information about security issues, please refer to below link
https://www.stitchdata.com/docs/security/overview#security-issuesEnvironment
-
Qlik Sense Enterprise on Windows: PostgresSQL consuming 100% of CPU in two-hourl...
The PostgreSQL instance used by Qlik Sense (on-premise) uses 100% of CPU capacity. This behavior can be seen in an interval of 2 hours. Cause The Reso... Show MoreThe PostgreSQL instance used by Qlik Sense (on-premise) uses 100% of CPU capacity. This behavior can be seen in an interval of 2 hours.
Cause
The Resource Distribution Service is set to run a 2-hourly scan on all extensions and themes as part of a sync to Qlik Sense Cloud. This has proven to have a dramatic effect in very large environments where postgres.exe is causing the CPU to spike to 100% for an extended duration, making the environment unusable.
Resolution
Switch off Resource Distribution or set it to run every 24 hours.
Switch off Resource Distribution
- Open the services.conf file (default: C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf) in a text editor elevated to Administrator permissions
- Locate the [resource-distribution] section.
- Set Disabled to true:
[resource-distribution] Disabled=true Identity=Qlik.resource-distribution DisplayName=Resource Distribution ExePath=Node\node.exe Script=..\ResourceDistributionService\server.js
- Save the file
- Restart the Service Dispatcher
Schedule it to run every 24 hours
- Open the services.conf file (default: C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf) in a text editor elevated to Administrator permissions
- Locate the [resource-distribution] section.
- Set Disabled to false as //Disabled=true:
[resource-distribution] //Disabled=true Identity=Qlik.resource-distribution DisplayName=Resource Distribution ExePath=Node\node.exe Script=..\ResourceDistributionService\server.js [resource-distribution.parameters] --secure --wes-port=${WESPort} --mode=server --log-path=${LogPath} --log-level=info --interval-time=86400000
- Save the file
- Restart the Service Dispatcher
Internal Investigation ID(s)
QB-18723
Environment
Qlik Sense Enterprise on Windows (November 2022 and later)