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.
Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.
The behaviour began after an upgrade of Qlik Sense Enterprise on Windows.
This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.
Enable QmcTaskTableCacheDisabled.
To do so:
Upgrade to the latest Service Release and disable the caching functionality:
To do so:
NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.
Should the issue persist after applying the workaround/fix, contact Qlik Support.
Three requirements need to be met in order to allow Anonymous users access to the Hub:
Useful information:
By default, anonymous access is disabled. The steps provided require a restart of the Proxy service after completion.
Anonymous users will need to have a license rule available for them which gives them either an Analyzer Capacity License or a Login Access Token. The instructions in this article will focus on Analyzter Capacity Licenses.
You can use the default Everyone stream, which has already been set up for anonymous access, or create your own.
We will create two rules. One to allow logged in (authenticated) users access and publishing permissions. One to allow anonymous user access, but no publishing permissons. Note that based on your requirements, this may need to modified.
We are now ready to test access.
Multiple tasks were hanging for hours on Reading (select ) queries due to hanging Commit query operations with SQL Server (MSSQL) database on the same table, necessitating the termination of tasks to release the blockage.
DBA's perspective
The commit query was pending on a customer business table, causing blocking issues as other concurrent read queries on the same table were held up by the blocking commit.
Job design perspective
The audit table-related connection did not have the auto-commit option enabled, leading to long-running commit operations.
TMC task scheduling
Execution triggers were set too close together, causing concurrency issues where multiple tasks attempted to access the same table simultaneously, leading to resource contention.
Job design optimizations
TMC scheduling optimization
Stagger task execution times to run sequentially, reducing concurrency and avoiding race conditions when accessing the same audit table.
Database-side optimization
Set a lock timeout on the database side to prevent prolonged task holding due to locks: SET LOCK_TIMEOUT timeout_period.
SQL Server table hints - WITH (NOLOCK) best practices (sqlshack.com)
Table Hints (Transact-SQL) - SQL Server | Microsoft Learn
The Qlik Sense Desktop or Server installation fails with:
INSTALLATION FAILED
AN ERROR HAS OCCURRED
For detailed information see the log file.
The installation logs (How to read the installation logs for Qlik products) will read:
Error 0x80070643: Failed to install MSI package.
Error 0x80070643: Failed to configure per-user MSI package.
Detected failing msi: DemoApps
Error 0x80070643: Failed to install MSI package.
Error 0x80070643: Failed to configure per-user MSI package.
Detected failing msi: SenseDesktop
Applied execute package: SenseDesktop, result: 0x80070643, restart: None
Error 0x80070643: Failed to execute MSI package.
ProgressTypeInstallation
Starting rollback execution of SenseDesktop
CAQuietExec: Entering CAQuietExec in C:\WINDOWS\Installer\MSIE865.tmp, version 3.10.2103.0
CAQuietExec: "powershell" -NoLogo -NonInteractive -InputFormat None
CAQuietExec: Error 0x80070002: Command failed to execute.
CAQuietExec: Error 0x80070002: QuietExec Failed
CAQuietExec: Error 0x80070002: Failed in ExecCommon method
CustomAction CA_ConvertToUTF8 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (74:54) [10:44:37:941]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (74:54) [10:44:37:942]: User policy value 'DisableRollback' is 0
MSI (s) (74:54) [10:44:37:942]: Machine policy value 'DisableRollback' is 0
Action ended 10:44:37: InstallFinalize. Return value 3.
The Failed to Install MSI Package can have a number of different root causes.
Dependencies may be missing. Install the latest C++ redistributable.
This issue may occur if the MSI software update registration has become corrupted, or if the .NET Framework installation on the computer has become corrupted (source: Microsoft, KB976982).
Repair or reinstall .NET framework.
How to troubleshoot:
Option 1
********************************************
********* Environment Variables **********
********************************************
.......
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Users\administrator\AppData\Local\Microsoft\WindowsApps;C:\WINDOWS\system32\inetsrv\
Install the Web Platform Installer Extension that includes the latest components of the Microsoft Web Platform, including Internet Information Services (IIS), SQL Server Express, .NET Framework and Visual Studio.
More information about the tool on the Microsoft page.
Verify if there are pending Windows updates. Complete them and try again.
The installation may fail if the installer is being executed from a network drive. Copy the installer to your local drive.
Talend Cloud platform provides computational capabilities that allow organizations to securely run data integration processes natively from cloud to cloud, on-premises to cloud, or cloud to on-premises environments.
These capabilities are powered by compute resources, commonly known as Engines. This article covers the four basic types.
Content:
A Cloud Engine is a compute resource managed by Talend in Talend Cloud that executes Job tasks.
A capability in Talend Cloud platform that allows you to securely run data integration Jobs natively from cloud to cloud, on-premises to cloud, or cloud to on-premises environments completely within your environment for enhanced performance and security, without transferring the data through the Cloud Engines in Talend Cloud platform.
Java-based runtime (similar to a Cloud Engine) to execute Talend Jobs on-premises or on another cloud platform that you control.
A Remote Engine Gen2 is a secure execution engine on which you can safely execute data pipelines (that is, data flows designed using Talend Pipeline Designer). It allows you to have control over your execution environment and resources because you can create and configure the engine in your own environment (Virtual Private Cloud or on-premises). Previously referred to as Remote Engines for Pipelines, this engine was renamed Remote Engine Gen2 during H1/2020. It is a Docker-based runtime to execute data pipelines on-premises or on another cloud platform that you control.
A Remote Engine Gen2 ensures:
Cloud Engine for Design is a built-in runner that allows you to easily design pipelines without setting up any processing engines. With this engine you can run two pipelines in parallel. For advanced processing of data, Talend recommends installing the secure Remote Engine Gen2.
The following table lists a comparative perspective between the two engines:
Cloud Engine (CE) |
Remote Engine (RE) |
Consumes 45,000 engine tokens |
Consumes 9,000 engine tokens |
Runs within Talend Cloud platform – no download required |
Downloadable software from Talend Cloud platform |
Managed by Talend, run on-demand as needed to execute Jobs |
Managed by the customer |
No customer resources required |
Customer can run on Windows, Linux, or OS X |
Set physical specifications (Memory, CPU, Temp Disk Space) |
Unlimited Memory, CPU, and Temp Space |
Require data sources/targets to be visible through the internet to the Cloud Engine |
Hybrid cloud or on-premises data sources |
Restricted to three concurrent Jobs |
Unlimited concurrent Jobs (default three) |
Available within Talend Cloud portal |
Available in AWS and Azure Marketplace |
Runs natively within Talend Cloud iPaaS infrastructure |
Uses HTTPS calls to Talend Cloud service to get configuration information and Job definition and schedules |
Cloud Engine for Design (CE4D) |
Remote Engine Gen 2 (REG2) |
Consumes zero engine tokens |
Consumes 9000 engine tokens |
Build upon a Docker-compose stack |
Build upon a Docker-compose stack |
Available as Cloud Image and Instantiated in Talend Cloud platform on behalf of the customer |
Available as an AMI Cloud Formation Template (for AWS) and Azure Image (for Azure) |
Not available as downloadable software as this type of engine is only suitable for design using Pipeline Designer in Talend Cloud portal |
Available as .zip or .tar.gz (for local deployment) |
A Cloud Engine for Design is included with Talend Cloud platform, to offer a serverless experience during design and testing. However, it is not meant for production (that is, not for running pipelines in non-development environments). It won’t scale for prod-size volumes and long-running pipelines. It should be used for design teams to get a preview working and test execution during development. This engine should not be used for production execution. |
It is used to run artifacts, tasks, preparations, and pipelines in the cloud, as well as creating connections and fetching data samples. |
Static IPs cannot be enabled for CE4D within Talend Management Console |
Not applicable as REG2 runs outside Talend Management Console (that is, in Customer Data Center) |
Additional engines (CE or RE) may be required if you have one or more of the following use cases:
These use cases depend on the deployment architecture in the specific customer environment and layout of the Remote Engine at the environment or workspace level configurations. This would need proper capacity planning and automatic horizontal and vertical scaling of the compute Engines.
Question |
Guideline |
How much data must be transferred per hour? |
Each Cloud Engine can transfer 225 GB per hour. |
How many separate flows can run in parallel? |
Each Cloud Engine can run up to three flows in parallel. |
How much temporary disk space is needed? |
Each Cloud Engine has 200GB of temp space. |
How CPU and memory intensive are the flows? |
Each Cloud Engine provides 8 GB of memory and two vCPU. This is shared among any concurrent flows. |
Are separate execution environments required? |
Many users desire separate execution for QA/Test/Development and Production. If this is needed, additional Cloud Engines should be added as required. |
If a source or target system is not accessible through the internet:
If one of the systems is not accessible using the internet, then a Remote Engine is needed.
When single flow requirements exceed the capacity of a Talend Cloud Engine:
If the Cloud Engine is too small (for example, the maximum memory of 5.25 GB, temporary space of 200 GB, two vCPU, or the maximum of 225 GB per hour) then, a Remote Engine is needed.
If a native driver is required:
If the solution requires a native driver, which is not part of the Talend action or Job generated code, a typical case for this is SAP with the JCO v3 Library, MS SQL Server Windows Authentication, then a Remote Engine is needed.
Data jurisdiction, security, or compliance reasons:
It may be desirable or required to retain data in a particular region or country for data privacy reasons. The data being processed may be subject to regulations such as PCI or HIPAA, or it may be more efficient to process the data within a single data center or public cloud location. These are all valid reasons to use a Remote Engine.
Cloud Engine (CE) |
Remote Engine (RE) |
Remote Engine Gen 2 (REG2) |
Cloud Engines allow you to run batch tasks that use on-premises or cloud applications and datasets (sources, targets) |
Remote Engines allow you to run batch tasks or microservices (APIs or Routes) that use on-premises or cloud applications and datasets (sources, targets) |
The Remote Engine Gen2 is used to run artifacts, tasks, preparations, and pipelines in the cloud, as well as creating connections and fetching data samples |
Consumes 45,000 engine tokens |
Consumes 9,000 engine tokens |
Consumes 9,000 engine tokens |
No download required - Runs within Talend Cloud platform |
Downloadable software from Talend Cloud platform |
Downloadable software from Talend Cloud platform |
Managed by Talend, run on-demand as needed to execute Jobs |
Managed by the customer |
Managed by the customer |
No customer resources required |
Can run on Windows, Linux, or OS X |
Require compatible Docker and Docker compose versions for Linux, Mac, and Windows |
Set physical specifications (Memory, CPU, and Temp Disk Space) |
Unlimited Memory, CPU, and Temp Space |
Unlimited Memory, CPU, and Temp Space |
Require data sources/targets to be visible through the internet to the Cloud Engine |
Hybrid cloud or on-premises data sources |
Hybrid cloud or on-premises data sources |
Restricted to three concurrent Jobs |
Unlimited concurrent Jobs (default three) |
Unlimited concurrent pipelines (configurable) |
Available within Talend Cloud portal |
Available in AWS and Azure Marketplace |
Available as an AMI Cloud Formation Template (for AWS) and Azure Image (for Azure) |
Runs natively within Talend Cloud iPaaS infrastructure |
Uses HTTPS calls to Talend Cloud service to get configuration information and Job definition and schedules |
Uses HTTPS calls to Talend Cloud service to get configuration information and pipeline definition and schedules |
Talend Help Center documentation:
Using the qlik-cli it is possible to import a list of users to a tenant from a csv file.
It will be then possible to assign roles, entitlements and space permissions to the users before they log in to the tenant.
Here's a possible example of how to do that.
Name,Email
Mick Case,Mick.Case@example.com
Davide Bironi,Davide.Bironi@example.com
Kenny Handsley,Kenny.Handsley@example.com
Leigh Kersriver,Leigh.Kersriver@example.com
Gerry Vain,Gerry.Vain@example.com
Tommy Ioni,Tommy.Ioni@example.com
Terence Attendant,Terence.Attendant@example.com
John Oughborne,John.Oughborne@example.com
William Guard,William.Guard@example.com
Renato Padovano,Renato.Padovano@example.com
# Import the csv file as an array of objects
$csv = Import-Csv -Path userlist.csv
# Initialize a counter for the subject
$counter = 1
# Loop through each object in the array
foreach ($row in $csv) {
# Generate the subject using the counter
$subject = "ExampleSubject" + $counter
# Execute the qlik-cli command with the column values and the subject
qlik user create --name $row.Name --email $row.Email --subject $subject
# Increment the counter
$counter++
}
#!/bin/bash
# Get the number of lines in the csv file
lines=$(wc -l < userlist.csv)
# Loop from the second line to the last line (skipping the header row)
for ((i=2; i<=lines; i++))
do
# Get the name and email values from the ith line using cut
name=$(cut -d, -f1 userlist.csv | sed -n "${i}p")
email=$(cut -d, -f2 userlist.csv | sed -n "${i}p")
# Generate the subject using the counter
subject="ExampleSubject$counter"
# Execute the qlik-cli command with the column values and the subject
qlik user create --name "$name" --email "$email" --subject "$subject"
# Increment the counter
((counter++))
done
NOTE: users will be created with a temporary SubjectId like "ExampleSubject1", "ExampleSubject2", and so so on. After the first login, users will get a proper SubjectId.
Roles, entitlements and space permissions will follow the users to the new subject.
Alternatives ways of adding users via scripts might be achieved via the an /api/v1/users CALL with the POST method and a payload like:
PAYLOAD:
{
"email": "name@example.com",
"name": "First Lastname",
"subject": "SubjectXYZ"
}
The information and the files in this article are provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
Qlik can technically provides a license that is stored in the TDC database server, which supports more than two TDC servers. However, it is important to remember that your sysadmin/devops must be very careful from the deployment perspective as they must develop scripts to ensure the following:
You may experience problems when executing actions with the MetaServlet API in the Talend Administration Center using the MetaServletCaller.sh or MetaServletCaller.bat scripts and the call doesn't work.
The error message you receive is:
Error: "error": “Username or password is wrong”,"returnCode": 3
The error arises because special characters in the username or password need to be escaped. Since JSON, the data format used by the MetaServlet API, does not support certain special characters without escaping.
Use the control character backslash ("\") to escape special characters.
For Example
Password: passwor"d
the quotation mark is the special character that needs to be escaped using a backslash.
Use passwor\"d
to include the quotation mark in the password.
For more information about Metaservlet, please check Qlik Talend Official Documentation
Metaservlet
Unable to generate personal access token in TMC and shows error "Token creation has failed" in TMC
Talend Cloud users can generate up to five access tokens. So as an administrator, you can view the name, owner, creation date and last date used for each token generated on the account. You can delete tokens individually or by group.
It is recommended to delete unused and old tokens to increase the system security.
Logs not showing up in TMC when a task is running on Remote Engine.
The payload of the generated metrics was exceeding the file size limit.
Most common error log:
com.fasterxml.jackson.databind.JsonMappingException: Invalid UTF-8 middle byte 0x70
at [Source: (ByteArrayInputStream); line: 1, column: 24553] (through reference chain: org.talend.observability.common.model.CloudEvent["data"]->org.talend.observability.common.model.MetricSet["metrics"]->java.util.ArrayList[42])
To address the issue and eliminate the error logs effectively , please follow these steps:
Upgrading Qlik Sense Enterprise on Windows (on-prem) fails. Reviewing the installer log files (see How To Collect Qlik Sense Installation Log File ) shows:
Error! Validation of: C:\Program Files\Qlik\Sense\\Client\1130.68f106588cb51d5970a9.js.LICENSE.txt failed: Could not find file 'C:\Program Files\Qlik\Sense\Client\1130.68f106588cb51d5970a9.js.LICENSE.txt'.
The environment previously used the Qlik PostgreSQL Installer to upgrade its bundled PostgreSQL database.
Verify if old Qlik Sense patches remained installed:
If the Uninstall option does not work, manually uninstall it instead:
A defect was observed if the Qlik PostgreSQL installer was previously used and old patches were not correctly removed by the installer. See the May 2023 Release Notes for QPI.
The error message appears when the installer is looking for the file which is no longer exists in the new version of the Qlik Sense.
Upgrading Qlik Sense Repository Database using the Qlik PostgreSQL Installer
Qlik Sense Enterprise on Windows with Qlik PostgreSQL Installer used to upgrade PostgreSQL
Example: QPI was used to upgrade PostgreSQL on November 2022. November 2022 was then upgraded to February 2023.
QB-17862
This document is a general guide and is provided as is. Modifications to the process may be necessary depending on your individual database setup.
If you have installed a standalone PostgreSQL database, or if you have used the Qlik PostgreSQL Installer (QPI) to upgrade and decouple your previously bundled database, then you can upgrade PostgreSQL at any time. This means you control maintenance and can immediately react to potential PostgreSQL security concerns by upgrading to a later service release or a later major version.
Content
This document covers the following scenario:
Run a complete backup of Qlik Sense Enterprise on Windows site as described in Backup and restore Qlik Sense Enterprise on Windows.
These steps apply if you are upgrading within a major PostgreSQL release (example: 14.5 to 14.8).
No further steps are required.
If you are moving to a higher major version, an in-place upgrade will not be possible. Instead, we will install the the new version in parallel, then then migrate the old database and eventually uninstall the old version. Our example is written using PostgreSQL 12 to 14.
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version
Changing the Database Superuser Password without Qlik Sense Installed
Cannot publish a Job to Talend Cloud from Talend Studio, the following message appears on the pop-up in Talend Studio:
Could not resolve dependencies for project <Project>.job:<JOB>:jar:0.1.0: The following artifacts could not be resolved: <Project>_jobs.code:routines:jar:8.0.1 (absent): Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.example.mse_jobs.code:routines:jar:8.0.1 has not been downloaded from it before. -> [Help 1]
Cause 1
Cause 2
Solution 1
Solution 2
Please note that merely editing the <Talend_Studio_Home>/path/Talend-Studio-xxx.ini file may not be sufficient. In cases where you are launching via a Windows/Mac/Linux GUI shortcut, please ensure that the -vm option is configured to point to the Java 17 bin.
This article provides a guide on installing Qlik Replicate on a docker image.
sudo rpm -qa|grep dockersudo yum remove docker docker-client docker-client-latest docker-common docker-latest docker-laster-logrotate docker-logrotate docker-engine
sudo yum install -y yum-utils device-mapper-persistent-data lvm2 sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo sudo yum install --allowerasing docker-ce docker-ce-cli containerd.io sudo systemctl start docker sudo systemctl enable docker
/kit
" The /kit directory is a temporary folder used to store installation files. In the example below, the RPM file is areplicate-2024.5.0-357.x86_64.rpm
. Once the installation is complete, the entire /kit folder can be safely deleted.mkdir -p /kit/ar_docker
cd /kit
rpm2cpio areplicate-2024.5.0-357.x86_64.rpm | cpio -iv --make-directories --no-absolute-filenames -D ar_docker/ ./opt/attunity/replicate/addons/samples/docker/*
mv ./ar_docker/opt/attunity/replicate/addons/samples/docker/* ./ar_docker
rm -rf ./ar_docker/opt
cd /kit/ar_docker
cp ../areplicate-2024.5.0-357.x86_64.rpm .
./create-dockerfile.sh
/kit/ar_docker/Dockerfile
, from:
RUN yum -y install /tmp/areplicate-*.rpmto
RUN systemd=no yum -y install /tmp/areplicate-*.rpm
NOTE!
The parameter systemd=no is used to solve the below error you may hit during the docker build stage: This rpm is not supported on your system (no systemctl), exiting. error: %prein(areplicate-2024.5.0-357.x86_64) scriptlet failed, exit status 43
NOTE!
The password should not be empty and must be strong enough.
WARNING!
If you want to install ODBC Drivers, please make the corresponding ODBC Drivers rpm files are ready in this folder. If you want to skip the ODBC Drivers installation at present, rename or delete the file "drivers" in this folder.
docker build --no-cache -t johnw/replicate:2024.5 .where
/johnw/replicate:2024.5
is the image tag.Do not forget the last period "."
docker run -d --name ar --hostname cdc2 -e ReplicateRestPort=3552 -p 3552:3552 -v /dockermount/data/replicate/data:/replicate/data johnw/replicate:2024.5
Now Qlik Replicate is running in the docker and can be accessed from Qlik Replicate Console GUI.
The Qlikview server has been set up with Kerberos authentication. When navigating to the QlikView Management Console the following errors are shown:
Login Failed
This web page cannot be displayed
Environment
Kerberos authentication is not supported in the QlikView Management Console.
For information regarding the AccessPoint, see Kerberos support using QlikView Webserver
App reloads in Qlik Cloud fail with the below error message:
Data has not been loaded. Please correct the error and try loading again.
The following error occurred: The memory limit for the request was reached
There are three main directions on mitigating high memory allocation problems;
The Qlik Sense Engine in Qlk Cloud is configured to have a sandbox limit for reloads so that they do not expand infinitely and bring down the Engine running the reload. Based on subscription details there is a limit for each app file. Still, additional memory is typically required during reload to process calculations before the app's data model has been updated.
During a reload the Engine will periodically measure allocated memory. If the allocated memory reaches the reload limit the reload will fail with a memory exceeded error.
Need to know the exact values?
For detailed information about Qlik Cloud guardrails, see Qlik Cloud Analytics specifications and capacity.
Large App support
Qlik Engine: Hypercube Memory Limit
QB-5268
In this article, we detail the 12 steps necessary to successfully configure Qlik Sense Enterprise on Windows after an Active Directory Domain name change or moving Qlik Sense to a new domain.
Depending on how you have configured your platform, not all the steps might be applicable. Before updating any hostname in Qlik Sense, make sure that the original value is using the old domain name. In some case, you may have configured “localhost” or the server name without any reference to the domain so there is no need in these cases to perform any update.
In this scenario we are updating a three-node environment running Qlik Sense February 2021:
The domain has been changed from DOMAIN.local to DOMAIN2.local
The servers mentioned below are already part of the new domain name DOMAIN2.local and their Fully Qualified Domain Name (FQDN) is already updated as followed:
All Qlik Sense services have been stopped on every node.
The first step is to update the postgres.conf file to listen on the correct hostname
Before doing any further changes, it is important to take a backup of your Qlik Sense Platform
Now we update the node names in the database with the new Fully Qualified Domain Name.
UPDATE public."Users"
SET "UserDirectory" = 'DOMAIN2'
WHERE "UserDirectory" = 'DOMAIN';
SELECT * FROM public."Users"
cd "C:\Program Files\Qlik\Sense\NLAppSearch\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\AppDistributionService"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\HybridDeploymentService"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\Licenses"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\NotifierService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\MobilityRegistrarService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\PrecedentsService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
cd "C:\Program Files\Qlik\Sense\DataPrepService\install"
.\Configure-Service.ps1 QlikServer3.domain2.local 4432 qliksenserepository <qliksenserepository_password>
If you are using the Qlik Logging Service;
cd "C:\Program Files\Qlik\Sense\Logging"
Qlik.Logging.Service.exe validate
cd "C:\Program Files\Qlik\Sense\Logging"
Qlik.Logging.Service.exe update -h QlikServer3.domain2.local
"C:\Program Files\Qlik\Sense\Repository\Repository.exe" -bootstrap -iscentral -restorehostname
If you are syncing your users with a User Directory Connector you will need to change the LDAP path to point to the new domain.
You will need to update the monitoring apps and their associated data connection to use the new Fully Qualified Domain Name
It is possible that you have created rules based on the User Directory. As you have changed the domain name, the user directory has also changed in Qlik Sense so you will need to update those to reflect that.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.