Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Qlik 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:
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. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
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)
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.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
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:
Log in to manage and track your active cases in Manage Cases. (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.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
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.
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.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
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.
Talend, the leader in data integration and integrity, proudly announces our Talend badging program that gives you the ability to securely share your verified technical skills on social media as you progress on the path to a recognized Talend expert.
If you are brand new to Talend, and want to learn more about how Talend products can help you get more value from your data, register for Talend Academy and start learning with the Talend Data Fabric Foundations learning plan. If you complete all the modules and quizzes, you will gain an understanding of the benefits delivered by Talend products, and you will earn the Talend Data Fabric Explorer badge.
With a Talend Academy subscription, new badge tracks become available to help you expand your knowledge of Talend products. You earn badges as you complete specific training in Talend Academy and pass certification exams.
On your path to expertise, Talend awards you badges that recognize your level of technical proficiency, from Explorer to Certified.
On completion of the Introduction to Talend Studio course on Talend Academy, you will receive the Talend Studio Explorer badge. It proves that you have a basic understanding of Talend Studio and how to perform basic tasks, such as creating and running a Job, parsing a delimited file, and connecting to a database. This is your first step on the journey to becoming a Talend expert.
Next, you will decide which track makes the most sense for you and your career development, depending on your role and area of interest. For more information, click the links to see the page for each track:
This list will increase over time to address more roles and areas of the Talend Data Fabric. Stay tuned!
To be awarded a Practitioner badge, you need to complete learning plans on Talend Academy based on the track you selected. For example, to get a Data Integration developer Practitioner badge, you need to complete the Data Integration Basics and Data Integration Advanced learning plans.
To guide you from the Explorer level to the Practitioner level, you can collect Talend Academy trophies along the way. In learning plans, you will find quizzes to assess your knowledge and understanding of the training material. If you achieve a score of 80% or more, then you will be awarded a trophy.
Each trophy demonstrates progress along the path towards the Practitioner badge. When you successfully complete your training and have collected the necessary trophies, you will earn a Practitioner badge to show that you are ready to contribute to projects. Now it’s time to celebrate and share your success with your peers!
Talend offers certification exams that assess your knowledge of product usage and the underlying methodology required to successfully implement quality projects. The exams are designed by Talend subject matter experts to ensure the quality and relevance of the technical topics covered in the exam. On completion of the certification exam, you will be awarded a Certified badge.
To be successful in the exam, participants are expected to have completed the recommended training on Talend Academy, earned the corresponding Practitioner badge, and have six months of hands-on experience on the product.
In addition to the formal training, Talend Academy offers certification preparation courses to help you get fully prepared for the exam. They include:
You’ll find all the details on our Certification Exams page.
Once you feel ready for the exam, register on the Kryterion Webassessor site.
Passed? Well done! Certified badge holders know how to implement quality projects, which may be an opportunity for you to expand your role. Make sure your peers know about this new achievement!
Claiming your Talend badge is simple. On completion of the earning criteria for each Talend badge, you will receive a notification email from Talend.
To claim your Talend badge, follow these simple steps:
If you don’t have an account, create one and validate it by clicking the link in the account creation email you will receive.
Note that you can have multiple email addresses attached to your badging account, such as professional and personal emails, or an email address from a previous employer. It means you have the ability to regroup all your badges into a single account so that peers and recruiters can view all your badges acquired over time.
This article contains steps on how to do backup and restore the Qlik Sense Enterprise on Windows (QSEoW) site.
For full instructions on how to backup and restore a Qlik Sense site, see the online help under Backup and restore Qlik Sense Enterprise on Windows.
For sole database backup information article can be found here: How to backup PostgreSQL database in Qlik Sense
Backup and Restore Targets:
Environment:
Note: These steps are provided as-is based on latest version available of Qlik Sense product at the time of writing and/or last update to the article. Please make sure to cross-reference these steps with the official documentation for your product version under Backup and restore Qlik Sense Enterprise on Windows.
Backing up Qlik Sense Repository Database:
! Downtime is required.
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\pg_dump.exe -h localhost -p 4432 -U postgres -b -F t -f "c:\backup\QSR_backup.tar" QSR
Restoring Database (PostgreSQL):
Option 1: Restoring on the same machine (PostgreSQL)
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\dropdb.exe -h localhost -p 4432 -U postgres QSR
.\createdb.exe -h localhost -p 4432 -U postgres -T template0 QSR
.\pg_restore.exe -h localhost -p 4432 -U postgres -d QSR "c:\backup\QSR_backup.tar"
For further reference, consult the Qlik Sense Help Site for your respective version.
Option 2: Restoring on a different machine (PostgreSQL)
cd "C:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.6\bin"
.\dropdb.exe -h localhost -p 4432 -U postgres QSR
.\createdb.exe -h localhost -p 4432 -U postgres -T template0 QSR
.\pg_restore.exe -h localhost -p 4432 -U postgres -d QSR "c:\Backup\QSR_backup.tar"
cd "C:\Program Files\Qlik\Sense\Repository"
.\repository.exe -standalone -restorehostname
Backing up The Certificate
Please refer to the Backing up Certificates Help site documentation for details and verify that the information matches your current version.
Restoring The Certificate
Please refer to the Restoring certificates Help site documentation for details and verify that the information matches your current version.
Backing up the Apps used by Qlik Sense
Restoring Apps used by Qlik Sense:
Backing up the Repository Content used by Apps:
Normally, It is similar to the section for apps, the path where these files live is in the StaticContent folder on the Share path.
Restoring the Repository Content used by Apps:
Restoring a Qlik Sense site to a machine with a different hostname
Security of Qlik Sense Enterprise on Windows can be approached in the below discrete areas. All these areas provide different options for increasing security in a deployment, and thereby mitigating vulnerabilities and protecting against attackers.
Content:
Be aware that a high level of server hardening can lead to failure in your deployment. Be mindful of always having a backup to restore to in case your configuration leads to irreversible failure.
Qlik Sense Enterprise on Windows supports multiple different Authentication Solutions;
Qlik can not specify which authentication method is appropriate for each deployment. It is advisable to review currently supported alternatives within your organization and/or Identity Provider (IdP) to implement the most suitable solution for your use case.
Qlik Sense Enterprise on Windows provides two levels of native authorization in the product.
Attribute based access control (ABAC), which is configured through Qlik Sense security rules. This article will not go in depth on how to best implement security rules for your requirements, but it is highly recommended to think of your users based on the capabilities that you intend to provide them. For example different roles and capabilities as shown in image below, allows for a security rule framework to be designed and implemented. This can be done either by yourself by referencing Qlik Sense Help for Administrators and available assets or by engaging with a Qlik Consultant or Qlik Partner.
Row level data reduction, which is configured through Section Access at Qlik Sense app level. This article will not go in depth on Section Access implementation, but with this reduction a single file can be used to hold the data for a number of users or user groups. Qlik Sense uses the information in the section access for authentication and authorization, and dynamically reduces the data, so that users only see their own data.
Qlik Sense Enterprise on Windows inherits the available protocols, cipher suites, key exchanges and other security hardening which are enabled on the Windows Server operating Qlik Sense.
Windows Server has a lot of protocols enabled by default; however protocols, ciphers, hashes and key exchanges that are considered deprecated or not secure enough should be disabled. There are many ways of doing this, and the Windows administrator and security experts should be consulted so that local policies are accurately applied. For simplicity, understanding and a good overview IIS Crypto 3.0 can be a good tool for evaluating current Windows configuration and applying changes.
Keep in mind that "Best Practice" today might not be recommended in the near future, what was considered "safe" a while ago is not necessarily considered so today. For this reason, it is also important to regularly scan servers for potential vulnerabilities and revisit configurations as required.
Windows Server needs to be restarted for these settings changes to take effect. It is also important to ensure that all components running on the server still operate as expected after hardening is applied, for example older non-Qlik software might not be compliant with the latest options and standards.
Firewalls typically should be closed, with required ports only opened for intended purposes.
See Qlik Sense Enterprise on Windows ports overview for details on required port based on the deployed architecture.
For most organizations, local administrator rights allow for an easier deployment, but Qlik Sense Enterprise on Windows does not require local administrator rights in order to function. This can be an attractive option inside some organizations. This will require additional configuration of boot strap mode as described in Qlik Sense Enterprise on Windows Services.
For a brief overview of the rights needed by a Qlik Sense Enterprise service account:
Qlik Sense Enterprise for Windows does not officially support Group Managed Service Accounts (gMSA), but it can operate using one. The initial barrier is that the installer requires a service account and password to be entered during installation. A domain or local account could be substituted for the install stages only to be swapped out in the Windows Services applet (services.msc) after installation. Some functionality may require workarounds (e.g. A User Directory Connection to Active Directory).
Qlik Sense Enterprise on Windows does require exceptions from anti-virus scan to avoid potential disk I/O conflicts. Refer to Qlik Sense Folder And Files To Exclude From AntiVirus Scanning for more details.
Qlik Sense Enterprise on Windows can run with Federal Information Processing Standards (FIPS) enabled on the Windows Server. This does require a few adjustments of configuration files due to Qlik using non-FIPS compliant algorithms for minor tasks like hash checks. See Running Qlik Sense on Windows systems with FIPS compliance enabled for more details on Qlik Sense and FIPS.
Qlik Sense Enterprise on Windows uses PostgreSQL to store meta-data relating to a Qlik Sense site. In multi-node sites or sites where PostgreSQL is isolated from Qlik Sense Enterprise for Windows additional security can be applied;
Qlik Sense Proxy service bundled with Qlik Sense Enterprise on Windows is simply a web-service. This means applying general practice guidance but in the context of Qlik Sense as described below.
Qlik Sense Enterprise on Windows acts as a Certificate Authority (CA) during initial installation and signs a certificate that is applied on all encrypted traffic between Qlik Sense services. The same Qlik Sense signed certificate is applied as default certificate also for incoming connections from users accessing Qlik Sense Hub and QMC. This default certificate is not intended for production use, unless user access to Qlik Sense comes through a network load balancer or reverse proxy that trusts the Qlik Sense certificate. For direct user access to Qlik Sense Proxy, a fully trusted certificate can typically be acquired from your local IT and then applied on the Qlik Sense Proxy service.
As of July 2019, Qlik Sense Enterprise on Windows support SHA1 and SHA2 certificates. If SHA384 or SHA512 certificates are needed, then a network load balancer or reverse proxy can be configured in front of Qlik Sense which offloads to Qlik Sense.
There are numerous HTTP response headers that can be used in attempting to secure a server. Below are a couple of the most common ones, but as always it is recommended to consult local IT and web security expert on what the recommendations are.
Any additional HTTP response header values can be configured in Qlik Sense Virtual Proxy settings under Additional response headers as shown in the below image and described in Qlik Sense for Administrators: Virtual Proxies. It is recommended to trial any header changes in a new virtual proxy, as poor configuration may accidentally lock you out from Qlik Sense access.
Policy is a placeholder for your policy of choice and cannot be used as a value. See Writing a Policy (Mozilla) for examples.
This Techspert Talks session covers:
- What to plan for
- Migration Pathways
- Cloud Best Practices
Chapters:
Resources:
If you need to resend a license email along with license installer links and the license key to a customer/user, follow the steps outlined below.
This guide will help you understand the process and the necessary details you need to provide.
Gather Necessary Information:
Send an Email Request:
Use the following template to structure your email request:
Subject: Resend License Email Request
Dear Support Team,
I hope this email finds you well.
I am writing to request that a license email be resent. Below are the details:
I would greatly appreciate your assistance in resending the license email. Thank you for your support and consideration.
Best regards,
[Your Name]
Subject: Resend License Email Request for Talend Data Integration
Dear Support Team,
I hope this email finds you well.
I am writing to request that the license email for Talend Data Integration be resent. Below are the details:
I would greatly appreciate your assistance in resending the license email. Thank you for your support and consideration.
Best regards,
Sam
Following these steps will help you effectively resend a license email to your customer.
If you have any further questions, feel free to reach out to the respective teams.
What is the default user session timeout for Qlik Sense Business and Qlik Sense Enterprise SaaS? Can the session timeout for Qlik Cloud be changed?
The default (fixed) value is set to 30 minutes. This is controlled by SESSION_TTL.
It is not currently possible to adjust the session timeouts in the Qlik Cloud.
Qlik Sense offers a range of Monitoring Applications that come pre-installed with the product. This article aims to provide information on where to find information about them or where to download them.
The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant.
The app provides:
For more information and to download the app and usage instructions, see The Entitlement Analyzer for Qlik Cloud.
The App Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Sense applications in your tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud App Analyzer.
The Reload Analyzer is a Qlik Sense application built for Qlik Cloud, which provides an overview of data refreshes for your Qlik Cloud tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud Reload Analyzer.
The Access Evaluator is a Qlik Sense application built for Qlik Cloud, which helps you to analyze user roles, access, and permissions across a tenant.
The app provides:
For more information and to download the app and usage instructions, see Qlik Cloud Access Evaluator.
Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:
For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.
This article shows how to use the Qlik Application Automation Monitoring App. It explains how to set up the load script and how to use the app for monitoring Qlik Application Automation usage statistics for a cloud tenant.
For more information and to download the app and usage instructions, see Qlik Application Automation monitoring app.
The OEM Dashboard is a Qlik Sense application for Qlik Cloud designed for OEM partners to centrally monitor usage data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas.
Although this dashboard is designed for OEMs, it can also be used by partners and customers who manage more than one tenant in Qlik Cloud.
For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.
The Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.
If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.
The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.
Basic information can be found here:
The License Monitor
The Operations Monitor
Both apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.
The Qlik Sense Hub connection times out faster / sooner than configured in the Virtual Proxy.
When working with an app in the hub, the connection to the app times out faster than configured in virtual proxy (for example, after 5 minutes), and the error message below is displayed:
Connection lost. Make sure that Qlik Sense is running properly. If your session has timed out due to inactivity, refresh to continue working.
This issue occurs when accessing Qlik Sense through a reverse proxy or load balance, but does not occur when accessing Qlik Sense on the same server (https://localhost/hub).
The user is also being active on the sheet, i.e. they are making selections etc. to interact with sheet objects.
Here is an example log line that may be seen in the AuditActivity_Proxy logs:
76 12.20.4.0 20200115T101930.708-0500 QLIKSERVER 8cd6aa7c-fab5-4e82-a2cd-0681943e7d58 Command=Close connection;Result=0;ResultText=Success d62cfb0a-3355-44a5-9e34-5eaada84be67 1ba723cc-e754-4e24-a42b-0732b24ad924 0 DOMAINNAME user.name 5c5e98cf-3f1f-45ed-96f0-8e76d7c44473 Not available Proxy AppAccess /app/5c5e98cf-3f1f-45ed-96f0-8e76d7c44473?reloaduri=https%3a%2f%2domain.com%2fsense%2fapp%2f5c5e98cf-3f1f-45ed-96f0-8e76d7c44473%2foverview Close connection 0 Backend web socket connection Closed for session 'd62cfb0a-3355-44a5-9e34-5eaada84be67'.
Qlik Sense should not terminate a session earlier than configured in the Virtual Proxy (default is 30 minutes), and when it does the error message would be different:
Your session has timed out. Log back in to Qlik Sense to continue.
In this case, if the connection is being lost and it is occurring sooner than configured in the virtual proxy then this indicates that either:
Qlik Sense requires WebSockets. To verify WebSocket traffic, see Qlik Sense Websocket Connectivity Tester.
Check to see if this issue occurs when using Internet Explorer. Internet Explorer by default adds additional unnecessary traffic to the WebSocket which can help in these situations. If you do not receive early timeouts when using IE, you can try Enabling TCP Keep Alive Functionality In Qlik Sense.
The HTTP keep-alive timeout may be increased here which helps in environments exhibiting the behavior mentioned above. See the Keep-alive timeout under the Proxy configuration. See Editing Proxies - Advanced > Keep-alive timeout (seconds)
If the above does not work, then you will need to make changes to your network infrastructure. Sniffing the network traffic to confirm things further can be performed. As sniffer, Wireshark can be installed on both Qlik Sense Proxy server and Hub client PC to run captures on both ends simultaneously. This may assist confirming the following:
Qlik Support may assist in a best-effort basis with the above. Please check out the video below for additional guidance. If further assistance is required correcting the environmental behavior, unfortunately the the task falls outside the scope of Qlik Support as this often is specific to the network involved. If further assistance is needed please reach out to your Account Owner to arrange Consulting Services (or see How to Contact the Consulting Team?)
Click here for video transcript
Network appliances (e.g. Load balancers, reverse proxies, VPN solutions, firewalls, web accelerators, etc) may not see the websocket connection as an "alive" TCP connection, depending on the vendor, and therefore terminate the connection on behalf of the end-user.
The "Backend web socket connection Closed for session" string seen in the logs is registered when a WebSocket TCP layer connection is closed by the transmission of a TCP Packet containing the FIN flag set. This happens when either the browser window or tab is closed or when a network device in the environment drops the TCP connection sessions in a controlled fashion (sends the TCP FIN packet to the Sense server). This can also be sent by the client's computer if there is(are) any setting(s) preventing inactive TCP connections from staying open, as required by the Websocket protocol.
Windows Firewall blocking port 4747. Disable Firewall or apply all ports inbound and outbound
The max parallel session count cannot be configured.
Qlik Sense Enterprise on Windows allows for a maximum of five parallel sessions from one user. If the maximum is reached, the sixth connection will fail with:
You cannot access Qlik Sense because you have no access pass. Too many sessions active in parallel
For more information, see:
You cannot access Qlik Sense because you have no access pass
How to count sessions in Qlik Sense
Troubleshoot too many sessions active in parallel
When launching Talend Studio the following message appears
A Java Runtime Environment (JRE) or Java Development Kit (JDK) must be available in order to run Talend_Sign_On_Tool_win-x86_64. No Java virtual machine
was found after searching the following locations:
<Studio HOME>\configuration\studio_SS o_client\jre\bin\javaw.exe
javaw.exe in your current PATH
JAVA_HOME or Java dll path may be incorrectly set in environmental variables or ini file.
As a Talend Test Migration License is generated for a period of 60 days (2 months) at a time, how to extend your Talend Test Migration License when it is expiring or already expired in Talend Studio/Talend Administration Center?
Please create a new case in Customer Support Portal so that Talend Support can generate a new test migration license for you. As long as there is a current subscription of the account, a test migration license will be provided.
Please keep in mind that a Talend Test Migration License is valid for 60 days(2 months) a time.
If you are looking to obtain a Test Migration license, see How to Request and Utilize a Talend Test Migration License.
In the realm of software integration and data management, ensuring compatibility and functionality across different versions is crucial.
Talend, a leading provider of data integration and integrity solutions, offers a straightforward process for users to test migration from existing active licenses to newer versions.
This guide outlines how to request and effectively utilize a Talend Test Migration License, whether for cloud or on-premises deployments.
A Talend Test Migration License allows users to transition from their current active license to a newer version temporarily for testing purposes.
This enables organizations to assess the new features, functionalities, and compatibility with their existing systems before committing to a full migration.
Before requesting a Talend test migration license, ensure you have the following details ready:
Send your request to customercare@qlik.com with the following email template.
Subject: Request for Talend Test Migration License
Dear Support Team,
I hope this message finds you well.
I am writing to request a Talend test migration license for our cloud deployment. Below are the required details:
Your prompt assistance in providing this test migration license would be greatly appreciated. Thank you for your support and consideration.
Best regards, [Your Name]
Subject: Request for Talend Test Migration License (Cloud)
Dear Support Team,
I hope this message finds you well.
I am writing to request a Talend test migration license for our cloud deployment. Below are the required details:
Your prompt assistance in providing this test migration license would be greatly appreciated. Thank you for your support and consideration.
Best regards,
John Doe
For On-Premises Deployments:
Send your request to customercare@qlik.com with the following email template.
Subject: Request for Talend Test Migration License
Dear Support Team,
I hope this message finds you well.
I am writing to request a Talend test migration license for our on-premises deployment. Below are the required details:
Your prompt assistance in providing this test migration license would be greatly appreciated. Thank you for your support and consideration.
Best regards, [Your Name]
Subject: Request for Talend Test Migration License (On-Premises)
Dear Support Team,
I hope this message finds you well.
I am writing to request a Talend test migration license for our on-premises deployment. Below are the required details:
Your prompt assistance in providing this test migration license would be greatly appreciated. Thank you for your support and consideration.
Best regards, John Doe
Effectively utilizing a Talend test migration license is essential for organizations looking to evaluate new Talend software versions without disrupting existing operations.
By following the outlined steps and using the provided templates, users can streamline the process of requesting and deploying a test migration license tailored to their specific deployment needs.
If you are looking to extend a Test Migration License, see How to extend Talend Test Migration License
! Note: Do NOT modify the NPrinting Database for any reason using PG Admin postres query or any other execution tools as this will damage your NPrinting Deployment and prevent successful NPrinting Database backup and restore operations.
! Note: Do NOT restore an older version of an NPrinting Database to a New NPrinting server or restore a newer version of the NPrinting database to an older version of NPrinting Server.
Examples:
These rules apply to general releases and service releases: The point version of the NPrinting Database being restored must match the point version of NPrinting Server being restored to.
! Note: From NPrinting February 2020 and later versions, it is NOT necessary to enter a superuser database password
! Note: If you are making a backup for the Qlik Support team, please add the following NPrinting user information so that we can log onto the NPrinting Web Console following the local restore of the database (also ensure that NPrinting Authentication is enabled. Go to Admin > Settings > Authentication
This procedure is meant to backup and restore (partial backup and restore of these individual items is not possible*):
NP Web Console Items:
NP Backup zip File Contents (do NOT open and modify the contents of this file):
NOTE:
c:\nprintingbackups
Before Proceeding: Please log on as the NPrinting service account used to run the NPrinting Web Engine and Scheduler services before proceeding
Open the Windows Service Manager (services.msc), and stop the following services (by right-clicking them, and then clicking Stop). This will ensure any manual or scheduled NPrinting Publish Tasks are not executed during the backup or restore process:
C:\NPrintingBackups
Do NOT modify any syntax or add any additional unnecessary spaces
Open the command prompt making sure to run cmd.exe as Administrator and change directory as follows:
cd C:\Program Files\NPrintingServer\Tools\Manager
Qlik.Nprinting.Manager.exe backup -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin" --pg-password YourSuperuserDBpasswordHere
or with Current Supported versions of NPrinting (no password required)
Qlik.Nprinting.Manager.exe backup -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin"
Qlik.Nprinting.Manager.exe restore -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin" --pg-password YourSuperuserDBpasswordHere
Qlik.Nprinting.Manager.exe restore -f C:\NPrintingBackups\NP_Backup.zip -p "C:\Program Files\NPrintingServer\pgsql\bin"
File C:\Users\domainuser\AppData\Local\Temp\2\nprintingrestore_20201203082300\files\xxxxxxxxxxxxxxxxxxxxxxxxxxxx does not exist in the source backup package.
! Note: If re-installing on existing or restoring to a different NPrinting server environment, ensure that the destination NPrinting server license is enabled/activated before restoring the NP database.
NPrinting Engine:
NP Connections:
Qlik Sense Certificates (if using NPrinting Qlik Sense connections)
C:\Program Files\NPrintingServer\Settings\SenseCertificates
Other helpful information about the NP Backup and Restore tool and process:
C:\ProgramData\NPrinting
Note:The pre and post upgrade backup files are appended with the NP version number and backup dateC:\ProgramData\nprinting\logs\nprinting_manager.log
*NOTE:
The following release notes cover the Qlik PostgreSQL installer (QPI) version 1.2.0 to 1.4.0.
Content
Silent install/upgrade is supported beginning with Qlik PostgreSQL Installer 1.4.0 and later. QPI can now be used with silent commands to install or upgrade the PostgreSQL database. (SHEND-973)
Improvement / Defect | Details |
SHEND-1359, QB-15164: Add support for encoding special characters for Postgres password in QPI | If super user password is set to have certain special characters, QPI did not allow upgrading PostgreSQL using this password. The workaround was to set a different password, use QPI to upgrade the PostgreSQL database and then reset the password after the upgrade. This workaround is not required anymore with 1.4.0 QPI, as 1.4.0 supports encoded passwords. |
SHEND-1408: Qlik Sense services were not started again by QPI after the upgrade | QPI failed to restart Qlik services after upgrading the PostgreSQL database. This has been fixed now. |
SHEND-1511: Upgrade not working from 9.6 database | In QPI 1.3.0, upgrade from PostgreSQL 9.6 version to 14.8 was failing. This issue is fixed in QPI 1.4.0 version. |
QB-21082: Upgrade from May 23 Patch 3 to August 23 RC3 fails when QPI is used before attempting upgrade. QB-20581: May 2023 installer breaks QRS if QPI was used with a patch before. |
Using QPI on a patched Qlik Sense version caused issues in the earlier version. This is now supported. |
Qlik Replicate 2023.5.0.284 has been observed to contain a behavior where source and target latency are miscalculated leading to big differences of fluctuating latency estimates. This behavior is resolved in a new patch.
2024-06-11T09:04:24 [PERFORMANCE ]T: Source latency 184.42 seconds, Target latency 12256.62 seconds, Handling latency 12072.21 seconds (replicationtask.c:3789)
2024-06-11T09:04:54 [PERFORMANCE ]T: Source latency 214.42 seconds, Target latency 214.42 seconds, Handling latency 0.00 seconds (replicationtask.c:3789)
2024-06-11T09:09:24 [PERFORMANCE ]T: Source latency 484.43 seconds, Target latency 12480.20 seconds, Handling latency 11995.77 seconds (replicationtask.c:3789)
This bug has been resolved in Qlik Replicate 2023.11 Service Pack 04 and Qlik Replicate 2024.05 General Availability release
QB-27442
RECOB-7562
If applying the R2024-05v2 or R2024-06 monthly patch on your CICD instance, and using Jenkins, many or all builds may start to fail without warning. The P2 may be commenting that it was not able to locate some of the component jars in the local .m2 repository; with the folder location mentioned being the "${user.HOME}/.m2/repository", instead of the local repository defined in the settings file. Even if using "-s", "-gs", and/or attempting to force the plugin to use a specific local repository, it will always override the location with ${user.HOME}, and fail to run properly.
This issue may only appear with those environments that use OpenJDK Zulu 17 at this time; instances that use Oracle JDK 17 or other OpenJDK distros do not appear to be affected at this time.
If customers have not upgraded to the R2024-05 monthly patch, we would suggest to continue using the R2024-04 monthly patch and 8.0.15 "builder-maven-plugin". If the upgrade has already happened or in progress, customers should check if they can swap to a different Open JDK instance (such as AdoptOpenJDK), or use Oracle JDK for the time being; until the issue has been fixed.
Currently, Qlik is on track to remediate the issue with a change to the plugins themselves, with a targeted date (at this time) of the July 2024 Monthly Patch.
Due to some changes in the newer versions of Jenkins (both LTS and the nightly versions), the plugins that are used with Jenkins remove some variables that are necessary to be passed to Maven and the P2 itself. Additionally, Zulu JDK has a problem with how the variables are being passed from Jenkins to the Java instance itself.
For additional questions or concerns, please reach out to Talend Support on this issue, and reference this internal defect ID, TUP-43304.
Parallel Load is often used to accelerate the replication of large tables by splitting the table into segments. Primary Key (or index) columns are not mandatory for Parallel Load; any column(s) can be used as a segment column as long as it can divide the data into segments. However, ROWID can sometimes be more efficient if the table has no Primary Key, no other indexes, and no other columns that can easily split the table rows.
Currently, Oracle data types ROWID/UROWID are not supported in the major versions of Qlik Replicate. As a result, columns with these data types will not be visible in the Qlik Replicate GUI, making it impossible to utilize ROWID directly in the Parallel Load design window.
This article provides a guide on how to utilize ROWID in Parallel Load.
CREATE VIEW scott.kitv1000rowid AS SELECT rowid||'' AS row_id, id, name, notes FROM scott.kitnopk1000 ORDER BY row_id;
You may get the errors, "A call to SSPI failed, see inner exception" and "The certificate chain was issued by an authority that is not trusted". While they should have no impact on your end-users, you'd still like to clean them up from the logs.
Qlik Sense otherwise functions without issues.
Example error:
System.Proxy.Qlik.Sense.Communication.Communication.Tcp.StreamFactory 16 c2972806-6ae3-4559-8ebf-c7c2201335f3 xx\xxx Failed to authenticate stream as Server The client and server cannot communicate, because they do not possess a common algorithm↵↓A call to SSPI failed, see inner exception. NO-STACKTRACE↵↓ at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
These, unfortunately, are not Qlik Sense errors, but rather errors from Windows that Qlik Sense reports. You should also be able to see them in your Windows Application logs. For more information, please search out Windows Support.
See Security Support Provider Interface Architecture for additional details.
Possible root causes: