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.
You can apply styling to customize the app based on your company standards. These styles are managed through custom themes.
To create your own custom theme, you’ll need to compile a compressed zip folder with three key components:
See Themes overview.
Once you’ve created the theme, you can upload it to your Qlik Cloud Management Console.
C:\Windows\System32>sftp -P 22 username@ftptest.test.com
The authenticity of host 'ftptest.test.com (18x.6x.15x.21x)' can't be established.
RSA key fingerprint is SHA256:KijFUxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxapWjo
If the extraction does not retrieve a valid working fingerprint, contact your SFTP server administrator who can provide a fingerprint or a public key for you.
If there are connectivity issues, to request data from your data connections through a firewall, you need to add the underlying (all three) IP addresses for your region to your firewall's allow list. These addresses are static and will not change. See Allowlisting domain names and IP addresses.
Error in SFTP connector
Diagnostic
Example: (insert a valid SFTP server host IP)
Result:
In case of this or other SFTP connection errors, please work with the SFTP server administrator or SFTP server vendor in order in order to enable the generation of a publicly available fingerprint.
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.
In Replicate Oracle source endpoint there was a limitation:
Object names exceeding 30 characters are not supported. Consequently, tables with names exceeding 30 characters or tables containing column names exceeding 30 characters will not be replicated.
The limitation comes from low versions Oracle behavior. However since Oracle v12.2, Oracle can support object name up to 128 bytes, long object name is common usage at present. The limitation in User Guide Object names exceeding 30 characters are not supported can be overcome now.
There are two major types of long identifier name in Oracle, 1- long table name, and 2- long column name.
1- Error messages of long table name
[METADATA_MANAGE ]W: Table 'SCOTT.VERYVERYVERYLONGLONGLONGTABLETABLETABLENAMENAMENAME' cannot be captured because the name contains 51 bytes (more than 30 bytes)
Add an internal parameter skipValidationLongNames to the Oracle source endpoint and set its value to true (default is false) then re-run the task:
2- Error messages of long column name
There are different messages if the column name exceeds 30 characters
[METADATA_MANAGE ]W: Table 'SCOTT.TEST1' cannot be captured because it contains column with too long name (more than 30 bytes)
Or
[SOURCE_CAPTURE ]E: Key segment 'CASE_LINEITEM_SEQ_NO' value of the table 'SCOTT.MY_IMPORT_ORDERS_APPLY_LINEITEM32' was not found in the bookmark
Or (incomplete WHERE clause)
[TARGET_APPLY ]E: Failed to build update statement, statement 'UPDATE "SCOTT"."MY_IMPORT_ORDERS_APPLY_LINEITEM32"
SET "COMMENTS"='This is final status' WHERE ', stream position '0000008e.64121e70.00000001.0000.02.0000:1529.17048.16']
There are 2 steps to solve above errors for long column name :
(1) Add internal parameter skipValidationLongNames (see above) in endpoint
(2) It also requires a parameter called "enable_goldengate_replication" is enabled in Oracle. This can only be done by end user and their DBA:
alter system set ENABLE_GOLDENGATE_REPLICATION=true;
Take notes this is supported when the user has GoldenGate license, and Oracle routinely audits licenses. Consult with the user DBA before alter the system settings.
Internal support case ID: # 00045265.
"C:\Program Files\NPrintingServer\Settings\SenseCertificates"
NOTE: Reminder that the NPrinting Engine service domain user account MUST be ROOTADMIN on each Qlik Sense server which NPrinting is connecting to.
The Qlik NPrinting server target folder for exported Qlik Sense certificates
"C:\Program Files\NPrintingServer\Settings\SenseCertificates"
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.
This article documents how to convert a Direct Task into a Log Stream Task without reloading the target.
Re-enter the Password
This article explains how to import and export master items to and from a Qlik Sense app using the Microsoft Excel connector in Qlik Application Automation.
Content:
The first part of this article will explain how to export all of your master items configured in your Qlik Sense App to a Microsoft Excel sheet. The second part will explain how to import those master items from the Microsoft Excel sheet back to a Qlik Sense App.
For this, you will need a Qlik Sense app in your tenant that contains measures, dimensions, and variables you want to export. You'll also need an empty Microsoft Excel file. The image below contains a basic example on exporting master items.
The following steps will guide you through recreating the above automation:
An export of the above automation can be found at the end of this article as Export master items to a Microsoft Excel sheet.json
For this example, you'll first need a Microsoft Excel file with sheets configured for each master item type (dimensions, measures, and variables). Use the above example to generate this file. The image below contains a basic example on importing master items from Microsoft Excel to a Qlik Sense app.
An export of the above automation can be found at the end of this article as Import master items from a Microsoft Excel Sheet.json
Follow the same steps to build automations that import/export dimensions and variables.
Let's go over some edge cases when exporting information to Microsoft Excel:
Please check the following articles for more information about working with master items in Qlik Application Automation and also uploading data to Microsoft Excel.
Follow the steps provided in this article How to import & export automations to import the automation from the shared JSON file.
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.
This article describes how to import Qlik Sense apps by using an automation. There are 2 possible approaches:
The difference between this approach and the Copy App block in the Qlik Cloud Services connector is that you can specify whether or not to include the data that's in the app. This can be done by setting the "No Data" parameter.
Example automation:
Blocks:
Export app
This approach allows you to import an app from a file. First, use the Export App To Base 64 Encoded File block in combination with the Cloud Storage connector to create the file on any of the supported destinations. In the below example, Dropbox is used.
Import app
To import the file again, use the Open File & Read Data From File blocks from the Cloud Storage connector and use the output from the read block as input for the Import App From Base 64 Encoded File block from the Qlik Cloud Services connector.
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.
Due to an issue with MySQL ODBC Driver 8.0.027 to 8.0.033, empty TEXT columns may not be replicated correctly during Full Load.
Qlik Replicate
MySQL ODBC Driver 8.0.027 to 8.0.033
Empty TEXT columns may not be replicated correctly during Full Load. For example, if one table row contains a TEXT column with a value and the same column in the next row contains an empty value (but not NULL), both rows will display the value of the first row on the target. See Limitations and considerations | Qlik Replicate Help.
When the source table has a text column that is blank (not null) the data from the previous row that had data is duplicated.
As an example if have the following 3 rows:
1 'SOME DATA'
2 null
3 '' <---empty string not null
The the output rows will have the following:
1 'SOME DATA'
2 null
3 'SOME DATA'
To resolve the issue, downgrade to MySQL ODBC 8.0.026.
The ODBC parameter no_ssps can also be used to resolve the issue.
Set it to no_ssps=1;
Until MySQL resolved the issue, the parameter should be set on Full Load ODBC connections. See 5.2 Connector/ODBC Connection Parameters | dev.mysql.com.
By default, Talend Remote Engine creates job execution logs in a directory below:
TalendRemoteEngineInstallationDirectory\TalendJobServersFiles\jobexecutions\logs
Is there any way we can change the default location of these logs?
This article aims at How to change default location of execution Logs for Remote Engine (R.E)
To change the location of Talend Jobserver files, Please follow below steps
After R.E restart, when new jobs are deployed from TMC you can see execution logs in new location
In a Windows multi-node deployment, the App Distribution Service (ADS) distributes apps from Qlik Sense Enterprise on Windows to Qlik Sense Enterprise SaaS. The service is installed on every node. However, Qlik Sense does not have load balancing for ADS, meaning if not all nodes have access to the apps, distribution may fail. See App Distribution from Qlik Sense Enterprise to Qlik Cloud fails when distributed from RIM NODE.
If you wish to disable app distribution from certain nodes:
[appdistributionservice]
Disabled=true
Identity=Qlik.app-distribution-service
DisplayName=App Distribution Service
ExePath=dotnet\dotnet.exe
UseScript=false
[hybriddeploymentservice]
Disabled=true
Identity=Qlik.hybrid-deployment-service
DisplayName=Hybrid Deployment Service
ExePath=dotnet\dotnet.exe
UseScript=false
The steps below are for an example test setup of SAML authentication using auth0 as Identity Provider with Qlik Sense Enterprise on Windows.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, reach out to our Professional Services or engage in our active Integrations forum.
Note: These steps assume an auth0 "Developer" account has already been created
{
"groups": [
"Everyone"
]
}
function (user, context, callback) {
if((user.user_metadata || {} ).groups){
context.idToken['https://qlik.com/groups'] = user.user_metadata.groups;
}
callback(null, user, context);
}
function (user, context, callback) {
context.idToken['https://qlik.com/sub'] = user.email;
callback(null, user, context);
}
Description | SAML_auth0 | An appropriate description |
Prefix | auth0 | This will be the prefix used when accessing Qlik Sense via URL |
Session cookie header name | X-Qlik-Session-auth0 | Needs to differ for every Virtual Proxy |
Authentication method | SAML | The authentication enabled via auth0 |
SAML host URI | https:// | The Qlik Sense Server |
SAML entity ID | https://.auth0.com | This can be found in the metadata file downloaded from auth0 under entityID |
SAML IdP metadata | Choose File: This is the xml file downloaded from Auth0 | The IdP metadata file downloaded from auth0 |
SAML attribute for user ID | See Claim Types (learn.microsoft) | This is also found in the metadata file from auth0 |
SAML attribute for user directory | [Auth0] | Directory name |
SAML signing algorithm | SHA-1 | Used by auth0 |
From R2024-05, Java 17 will become the only supported version to start most Talend modules, enforcing the improved security of Java 17 and eliminating concerns about Java's end-of-support for older versions. In 2025, Java 17 will become the only supported version for all operations in Talend modules.
Starting from v2.13, Talend Remote Engine requires Java 17 to run. If some of your artifacts, such as Big Data Jobs, require other Java versions, see Specifying a Java version to run Jobs or Microservices.
Content
Qlik Talend Module | Patch Level and Version |
Studio | Supported from R2023-10 onwards |
Remote Engine | 2.13 or later |
Runtime | 8.0.1-R2023-10 or later |
For Windows users, please follow the JDK installation guide (docs.oracle.com).
For Linux users, please follow the JDK installation guide (docs.oracle.com).
For MAC OS users, please follow the JDK installation guide (docs.oracle.com).
When working with software that supports multiple versions of Java, it's important to be able to specify the exact Java version you want to use. This ensures compatibility and consistent behavior across your applications. Here is how you can specify a specific Java version on the following products (such as build servers, shared application server, and similar):
For Studio users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps:
-vm
<JDK17 HOME>\bin\server\jvm.dll
For Remote Engine (RE) users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
For Runtime users who are using multiple JDKs, please follow the appropriate instructions listed above and follow the proceeding additional steps.
If Runtime is not running as a service:
With the Enable Java 17 compatibility option activated, any Job built by Talend Studio cannot be executed with Java 8. For this reason, verify the Java environment on your Job execution servers before activating the option.
To use Talend Administration Center with Java 17, you need to open the <tac_installation_folder>/apache-tomcat/bin/setenv.sh file and add the following commands:
# export modules export JAVA_OPTS="$JAVA_OPTS --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
Windows users use <tac_installation_folder>\apache-tomcat\bin\setenv.bat
Follow the steps below to configure the JobServer to use the new Java version.
Navigate to the JobServer Configuration:
Go to the <JobServerRootDir>\conf directory, where <JobServerRootDir> is the path to your Talend JobServer installation.
Open the Configuration File for Editing:
Locate the TalendJobServer.properties file and open it with a text editor of your choice.
Set the Java 17 Executable Path:
Find the line dedicated to the Job launcher path within the file. You will modify this line to point to the Java 17 executable.
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH="C:\\Program Files\\Java\\jdk-17\\bin\\java.exe"
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=/usr/lib/jvm/java-17-openjdk/bin/java
Replace the example paths with the actual path where Java 17 is installed on your system. Ensure to point directly to the Java executable within the bin directory of your JDK installation.
Save Your Changes:
After editing, save the TalendJobServer.properties file.
Restart Talend JobServer:
For the changes to take effect, restart your Talend JobServer.
After completing these steps, Talend JobServer will utilize Java 17 for executing Jobs, ensuring compatibility with the latest Java version supported by Talend modules.
For Java 17 users, Talend CICD process requires the following Maven options:
set "MAVEN_OPTS=%MAVEN_OPTS% --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
For Java 17 users, Talend CICD process requires the following Maven options:
export MAVEN_OPTS="$MAVEN_OPTS \ --add-opens=java.base/java.net=ALL-UNNAMED \ --add-opens=java.base/sun.security.x509=ALL-UNNAMED \ --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED"
<name>TALEND_CI_RUN_CONFIG</name> <description>Define the Maven parameters to be used by the product execution, such as: - Studio location - debug flags These parameters will be put to maven 'mavenOpts'. If Jenkins is using Java 17, add: --add-opens=java.base/java.net=ALL-UNNAMED --add-opens=java.base/sun.security.x509=ALL-UNNAMED --add-opens=java.base/sun.security.pkcs=ALL-UNNAMED </description>
Overview
Enable your Remote Engine to run Jobs or Microservices using a specific Java version.
By default, a Remote Engine uses the Java version of its environment to execute Jobs or Microservices. With Remote Engine v2.13 and onwards, Java 17 is mandatory for engine startup. However, when it comes to running Jobs or Microservices, you can specify a different Java version. This feature allows you to use a newer engine version to run the artifacts designed with older Java versions, without the need to rebuild these artifacts, such as the Big Data Jobs, which reply on Java 8 only.
When developing new Jobs or Microservices that do not exclusively rely on Java 8, that is to say, they are not Big Data Jobs, consider building them with the add-opens option to ensure compatibility with Java 17. This option opens the necessary packages for Java 17 compatibility, making your Jobs or Microservices directly runnable on the newer Remote Engine version, without having to go through the procedure explained in this section for defining a specific Java version. For further information about how to use this add-opens option and its limitation, see Setting up Java in Talend Studio.
Procedure
c:\\Program\ Files\\Java\\jdk11.0.18_10\\bin\\java.exe
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=c:\\jdks\\jdk11.0.18_10\\bin\\java.exe
ms.custom.jre.path=C\:/Java/jdk/binMake this modification before deploying your Microservices to ensure that these changes are correctly taken into account.
For Java Option Command --add-opens, using SPACE or = depends on OS, JDK version or the place where you setup, there are 3 cases:
1. support both SPACE and =
2. support SPACE only
3. support = only
Example:
--add-opens=java.base/java.net=ALL-UNNAMED
--add-opens java.base/java.net=ALL-UNNAMED
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.
Upgrading Qlik Sense Enterprise on Windows does not automatically upgrade the bundled PostgreSQL version. New versions of PostgreSQL are only deployed during a new install. This means upgrading to, for example, Qlik Sense Enterprise on Windows May 2021, PostgreSQL will remain on 9.6.
For many organizations, running on the latest supported PostgreSQL version is a security requirement. To achieve this:
Content:
The information in this article is provided as-is and to be used at your own 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.
This process requires a full reinstallation of the product. Despite the fact that a backup is being taken as part of the process, it is highly recommended to have a second backup plan in place such as a Virtual Machine snapshot and/or a Server Backup.
It is highly recommended to test this process in a test environment to get familiar with it.
The first step is to upgrade your environment to Qlik Sense Enterprise on Windows. This article was originally written for May 2021, but can be applied to any version. Follow the required steps and recommendations for an upgrade for your version. Example: August 2023.
Once the upgrade is done make sure your Qlik Sense site is completely operational.
At this point, you have an operational Qlik Sense site running on your new version of Qlik Sense Enterprise on Windows. However, the bundled PostgreSQL is still on version 9.6 or 12.5, depending on the originally installed version.
The next step will be to backup your entire Qlik Sense site following these instructions (including the certificates) . The backup is essential as it will need to be restored later on.
You will now need to uninstall Qlik Sense from the central node following these instructions.
During the uninstall:
Now that Qlik Sense Enterprise on Windows is uninstalled on the central node, you will reinstall it as a result will deploy either a bundled PostgreSQL 14.8 (August 2023 and later) or a bundled PostgreSQL 12.5 (May 2021 to May 2023). Instructions available here (choose your version).
Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.
You now have a clean Qlik Sense Enterprise on Windows deployed on your central node with PostgreSQL 14.8 or 12.5. You now need to restore your environment to retrieve all your configurations and apps.
Please follow the Restoring a Qlik Sense site (including the certificates).
Note: While restoring the database backup you will most likely receive the following error which can be ignored. This error is caused by the version discrepancies between the pg_dump that made the dump file and the pg_restore that's restoring it - in example files coming from PostgreSQL version 9.6 vs files coming from PostgreSQL version 12.5. QSR backup taken and restored with the same version of PostgreSQL will not produce that error.
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 3; 2615 2200 SCHEMA public postgres
pg_restore: error: could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;
pg_restore: warning: errors ignored on restore: 1
Once the environment is restored, you should be able to start your central node and rim nodes successfully.
Qlik Sense Enterprise on Windows May 2021 and later
Amazon DynamoDB is a fully managed NoSQL database service that provides fast and predictable performance with seamless scalability. You can use Amazon DynamoDB connector to make changes and perform various action on database tables and items within those tables, specific to a region or global.
This article explains how the Amazon DynamoDB connector in Qlik Application Automation can be used within Qlik Cloud.
Content
By default, users and roles don't have permission to create or modify DynamoDB resources. They cannot perform tasks using the AWS Management Console, AWS Command Line Interface (AWS CLI), or AWS API. To grant users permission to perform actions on the resources that they need, an IAM administrator can create IAM policies. The administrator can then add the IAM policies to roles, and users can assume the roles.
To learn how to create an IAM identity-based policy by using these sample JSON policy documents, see Creating IAM policies in the IAM User Guide.
The Amazon DynamoDB connector consists of the following blocks:
The Amazon DynamoDB connector's Put/Update Item blocks can be programed for diverse tasks including:
The Amazon DynamoDB connector allows you to write back App data to the source database. If clients do not have access to their firm's database, the company may offer an update on the Item. We can utilize the Put/Update blocks which can then update the database.
Refer to How to build a write back solution with native Qlik Sense components and Qlik Application Automation for instructions on how to configure the writeback. In the automation, instead of using the JIRA connector.
Use the Amazon DynamoDB connector's Put Item/Update Item block, as illustrated:
Edits an existing item's attributes, or adds a new item to the table if it does not already exist. You can put, delete, or add attribute values. You can also perform a conditional update on an existing item (insert a new attribute name-value pair if it doesn't exist, or replace an existing name-value pair if it has certain expected attribute values).
*In API terms, this endpoint behaves like a PATCH method which can perform partial updates.
Creates a new item, or replaces an old item with a new item. If an item that has the same primary key as the new item already exists in the specified table, the new item completely replaces the existing item. You can perform a conditional put operation (add a new item if one with the specified primary key doesn't exist), or replace an existing item if it has certain attribute values. You can return the item's attribute values in the same operation, using the ReturnValues parameter.
To manipulate data in an Amazon DynamoDB table, you use the 'Put Item', 'Update Item' etc. operations.
For these data manipulation operations, you can specify a condition expression to determine which items should be modified. If the condition expression evaluates to true, the operation succeeds; otherwise, the operation fails.
An expression that defines one or more attributes to be updated, the action to be performed on them, and new values for them.
One or more values that can be substituted in an expression.
Examples of Update Expressions, Conditions Expressions, and Expression Attribute Values:
The following error message appears repeatedly in the logs.
2024-01-20 08:50:10 ERROR RepoProjectRefresher -
2024-01-10 16:58:47 ERROR GC - D:\Talend\7.3.1\tac\apache-tomcat\temp\_git\
The main reason for the log type is that the RepoProjectRefresher faces out of memory issues. By default, TAC automatically caches/checks out the project source code into the tac\apache-tomcat\temp folder. When the source code accumulation is large, the RepoProjectRefresher module will consume a lot of memory. When maximum value is reached, a GC error will occur and a GC error log will be generated.
Note: The RepoRefresher cache functionality has been deprecated in the latest version of TAC v8.0.1
Disable the Git caching mechanism for the TAC project by following these steps:
update t731.configuration set value='true' where configuration.key='git.whiteListBranches.enable';
update t731.configuration set value='\"Technical labels of project\",\"Active branch name\"' where configuration.key='git.whiteListBranches.list';
! 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 (see Backup and restore Qlik NPrinting).
! 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: