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.
Reload fails in QMC even though script part is successfull in Qlik Sense Enterprise on Windows November 2023 and above.
When you are using a NetApp based storage you might see an error when trying to publish and replace or reloading a published app.
In the QMC you will see that the script load itself finished successfully, but the task failed after that.
ERROR QlikServer1 System.Engine.Engine 228 43384f67-ce24-47b1-8d12-810fca589657
Domain\serviceuser QF: CopyRename exception:
Rename from \\fileserver\share\Apps\e8d5b2d8-cf7d-4406-903e-a249528b160c.new
to \\fileserver\share\Apps\ae763791-8131-4118-b8df-35650f29e6f6
failed: RenameFile failed in CopyRename
ExtendedException: Type '9010' thrown in file
'C:\Jws\engine-common-ws\src\ServerPlugin\Plugins\PluginApiSupport\PluginHelpers.cpp'
in function 'ServerPlugin::PluginHelpers::ConvertAndThrow'
on line '149'. Message: 'Unknown error' and additional debug info:
'Could not replace collection
\\fileserver\share\Apps\8fa5536b-f45f-4262-842a-884936cf119c] with
[\\fileserver\share\Apps\Transactions\Qlikserver1\829A26D1-49D2-413B-AFB1-739261AA1A5E],
(genericException)'
<<< {"jsonrpc":"2.0","id":1578431,"error":{"code":9010,"parameter":
"Object move failed.","message":"Unknown error"}}
ERROR Qlikserver1 06c3ab76-226a-4e25-990f-6655a965c8f3
20240218T040613.891-0500 12.1581.19.0
Command=Doc::DoSave;Result=9010;ResultText=Error: Unknown error
0 0 298317 INTERNAL&
emsp; sa_scheduler b3712cae-ff20-4443-b15b-c3e4d33ec7b4
9c1f1450-3341-4deb-bc9b-92bf9b6861cf Taskname Engine Not available
Doc::DoSave Doc::DoSave 9010 Object move failed.
06c3ab76-226a-4e25-990f-6655a965c8f3
Potential workarounds
The most plausible cause currently is that the specific engine version has issues releasing File Lock operations. We are actively investigating the root cause, but there is no fix available yet.
An update will be provided as soon as there is more information to share.
QB-25096
QB-26125
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. |
In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).
For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.
Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.
Index
The following versions have been tested and verified to work with QPI (1.4.0):
Qlik Sense February 2022 to Qlik Sense November 2023.
If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.
The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.
Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Download the installer here.
Qlik PostgreSQL installer Release Notes
The following versions have been tested and verified to work with QPI (1.4.0):
February 2022 to November 2023.
If you are on any version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a 9.6 update is blocked.
Uninstall the old Qlik Sense Repository Database service.
This step is required. Failing to remove the old service will lead the upgrade or patching issues.
Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts.If you do not immediately upgrade:
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.
Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.
Video chapters:
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. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.
Qlik PostgreSQL installer version 1.3.0 Release Notes
Techspert Talks - Upgrading Qlik Sense Repository Service
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades
This article covers the details of how to license a Qlik Sense Enterprise on Windows server with a Signed License Key (SLK).
Index:
To apply a Signed License Key, a secure network connection is required to be established: A signed license key requires connectivity to license.qlikcloud.com. See List of IP Addresses behind license.qlikcloud.com and lef.qliktech.com for details.
It can establish in any of the security scenarios below:
All nodes in a Qlik Sense Enterprise on Windows on-premise multi node environment need access to the license server.
The Qlik Sense Engine allows for a hard max limit to be set on memory consumption, which, if enabled on the Operating System level as well, will make a best effort to remain below the set limit.
The setting is located in the Qlik Sense Management Console > Engine > Advanced and can be configured as an option in the setting Memory usage mode.
See Editing an engine - Qlik Sense for administrators for details on Engine settings.
This setting requires that the Operating System is configured to support this, as described in the SetProcessWorkingSetSizeEx documentation (QUOTA_LIMITS_HARDWS_MAX_ENABLE parameter).
Even with the hard limit set, it may still be possible for the host operating system to report memory spikes above the Max memory usage (%).
The reason for that is because the Qlik Sense Engine memory limit will be defined based on the total memory available.
Example:
The memory working setting limit is not a hard limit to set on the engine. This is a setting that set how much we allocate and how far we are allowed to go before we start alarming on the working set beyond parameters.
QLIK-96872
Qlik Sense Enterprise on Windows , all versions
The most common reason for this is that the credentials entered are not valid. So to be sure that these credentials work elsewhere (e.g. try to launch an application using these credentials like Notepad.exe)
Other potential causes:
For (1):
For (2):
Accessing the Qlik Sense Enterprise on Windows hub or Management Console with HTTPS leads to a number of different browser errors (depending on browser vendor):
There is a problem with this website's security certificate.
Problem with security certificate or connection is untrusted.
Your connection is not private.
NEST::ERR_CERT_AUTHORITY_INVALID
When selecting Continue.... the page will display with a red cross in its URL bar and the error:
Certificate error
Qlik Sense Enterprise on Windows
The client's web browser does not consider the certificate provided by the server to be trusted.
By default, Qlik Sense Enterprise on Windows is installed with a server-side self-signed certificate. These are not trusted by clients and the error is to be expected.
Use the correct URL
Progress without action
Obtain and install a trusted certificate
Note: This still requires that the root certificate is installed locally on all clients. With trusted Certificate Authorities, this is usually the case by default.
Import the root certificate on all local clients.
Don't have a certificate by a trusted Certificate Authority? You will need to import the certificate on all local clients.
This can be achieved using a Group Policy, see Distribute Certificates to Client Computers by Using Group Policy
Identifying Qlik Sense root CA and server certificates in certificate store
Qlik Sense: Compatibility information for third-party SSL certificates to use with HUB/QMC
Qlik Sense Mobile on iOS: cannot open apps on the HUB
Qlik Sense: Trust a self-signed certificate on the client
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.
After patching Qlik Talend Studio to R2023-07, an old salesforce:event/xxx message pull will fail with:
org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: salesforce://event/Customer_Details_New__e?rawPayload=true&replayId=-1 due to: event/Customer_Details_New__e
Since Camel 3.19.0, operationName is mandatory in the salesforce URI. See camel-salesforce - Endpoint syntax should have mandatory operationName and CAMEL-18317: camel-salesforce: Add subscribe operation for details.
Old salesforce:event/xxx will be changed to salesforce:subscribe:event/xxx to fix this issue.
Talend Studio v 7.3.1; v 8.0
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:
The QlikSenseUtil comes bundled with Qlik Sense Enterprise on Windows. It's executable is by default stored in:
%Program Files%\Qlik\Sense\Repository\Util\QlikSenseUtil\QlikSenseUtil.exe
Qlik Sense Util is no longer supported as a backup and restore tool. For the officially supported backup and Restore Process, see Backup and Restore.
When attempting to execute the automatic installer.exe for Remote Engine, on Windows Server 2019, it fails with the error:
Error running C:\TalendRemoteEngine/bin/client.bat -a 8104 -h localhost -u tadmin "feature:install wrapper"
When attempting to run the Remote Engine manually by executing the trun command in the bin directory of the Remote Engine installation, the following error occurs:
The installer.exe itself can cause the error during the automatic run of the Remote Engine.
The error caused during the manual run of Remote Engine occurs when the JAVA_HOME and PATH environment variables are not set up correctly on the machine where this is happening and can cause the batch files to fail when starting.
The best way to avoid the error caused during the automatic run of the Remote Engine is to clear the existing Remote Engine installation and install it again manually with 7-Zip.
To avoid the error caused during the manual run of Remote Engine, set the JAVA_HOME and PATH environment variables according to the Setting up JAVA_HOME instructions available in Talend Cloud Installation Guide for Windows.
QlikView May 2022 now, by default, saves files in .qvf format. Is it possible to revert to .qvw as the default?
Follow these steps:
In order to revert the change, the setting can be changed to "QvDefaultFileFormat=qvf"
QlikView May 2022 (12.70) IR or higher
Disclaimer: In Qlik Cloud, SAML is a supported authentication method that can be used. However the infrastructure to make SAML works will need to be set by the customer. Please be aware that Qlik Support can not help in the setting up of SAML/SSO or related issues. If the customer needs help to set up SAML from scratch, Qlik Consulting needs to be invoked. This is out of scope for Support.
Qlik Support will do a first assessment of SAML related support cases in order to understand if the issue is related to a possible defect in the implementation of SAML in Qlik Cloud or a wrong setup.
This article gathers information needed for Qlik Support to assess a SAML related support case.
The following need to be considered for the SAML implementation in Qlik Cloud:
The following six pieces information are required when investigating a SAML-related issue:
If a traceId number is provided in the error, please also provide the traceId in text format.
See the Qlik Online Help for general information about Qlik Sense and AWS deployments. The content may change depending on the version of Sense.
In an Amazon Web Services (AWS) deployment, you install Qlik Sense Enterprise on an Amazon virtual private cloud infrastructure that is flexible, high-performance, and quick to set up.
Deploying Qlik Sense Enterprise on AWS will enable you to quickly add new applications in a simple and scalable manner. You can do this with a basic knowledge of AWS security and scalability options but without the need to follow complex on-premise installation and configuration procedures. Using AWS will enable you to get your Qlik Sense infrastructure up and running in fraction of the time required for an on-premise deployment, and will enable you to scale your deployment quickly and easily, regardless of unexpected changes in demand.
You can deploy Qlik Sense to AWS manually, or you can use an Amazon Machine Image (AMI) available in the AWS Marketplace that includes Qlik Sense preinstalled. However, predefined images do not include a file share, so can only support single node Qlik Sense deployments.
Qlik Sense Enterprise on Windows deployment to AWS (about)
Preparing your Amazon AWS platform to install Qlik Sense Enterprise on Windows
Install Qlik Sense Enterprise on Windows on the AWS server
After the Qlik GeoAnalytics installation, an activation of the product is required. During the use of the Qlik GeoAnalytics License Activation Tool you might see the error message:
Could not communicate with the license server. Check your internet connection.
Environment
Resolution
The best way to resolve the issue is to install a version post November 2020. Until the upgrade here is a workaround:
Create a file called GeoAnalyticsLicenseTool.exe.config in the same folder as the license tool executable, C:\Program Files (x86)\QlikView\GeoAnalyticsLicenseTool .
Paste this inside:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<runtime>
<AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false"/>
</runtime>
</configuration>
Cause
The LEF license servers have been moved to another location and are now using TLS 1.2 as a default.
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.
When uploading an app to Qlik Cloud, a generic "Failed to upload files:" error is displayed.
To understand the cause of the failure, enable the browser's developer tools and reproduce the issue, and then:
Installing or Upgrading Qlik Replicate may fail with references to Java conflicts.
Example error during installation:
file /app/areplicate/attunity/replicate/jvm/conf/logging.properties from install of areplicate-2023.11.0-282.x86_64 conflicts with file from package java-11-openjdk-headless-1:11.0.22.0.7-2.el8.x86_64
This is commonly caused by a different version of Java being installed as well as a symlink pointing to this instance, instead of the Java version which comes bundled with Qlik Replicate.
The files from your Qlik Replicate RPM package conflict with your already installed Java package and a symlink points to the conflicting installation folder.
Remove the symbol link, upgrade or install Qlik Replicate, and then re-create the symbol link.
Rather than maintaining a separate Java package, Qlik recommends using the JVM bundled with Qlik Replicate RPM to avoid potential version compatibility risks.