After an upgrade to Qlik Sense Enterprise on Windows May 2023 patch 3 or later, REST connections fail with the following error: 

"WITH CONNECTION" is not allowed. To allow "WITH CONNECTION", select Allow "WITH CONNECTION" in the connector settings.

The Allow WITH CONNECTION option is not exposed in the REST Connector GUI and cannot be changed.

Qlik Sense Enterprise on Windows August 2023 and later are not affected.

Resolution

To resolve the issue, upgrade to August 2023.

To manually mitigate the issue in the May release branch, replace the  qsdfw_qsefw_qlikview.qliksourceconfig file. Qlik is investigating a solution which does not require manual intervention.

Backup the affected file before continuing with the workaround. When taking the backup, do not keep the backed up file in the same folder. (see end notes)

1. On each Qlik Sense Server node, navigate to: C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector\
2. Locate qsdfw_qsefw_qlikview.qliksourceconfig
3. Replace qsdfw_qsefw_qlikview.qliksourceconfig with the file attached to this article. 
4. This resolves the issue. 
   
   Subscribe to this article or monitor the release notes for information on an automated fix.

End notes:

The folder C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector can only contain one qliksourceconfig file with correct name: qsdfw_qsefw_qlikview.qliksourceconfig

If there are two qliksourceconfig files (even with different names, such as a backup), the first one in alphabetical order will be chosen.

Cause 

QB-20735

Environment

Qlik Sense Enterprise on Windows May 2023 Patch 3 and later 

Does not affect August 2023 and later releases.

Internal Investigation ID(s) 

QB-20735

Some connectors require an encryption key before you create or edit a connection. Failing to generate a key will result in:

Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING - you must manually set an encryption key before creating new connections.

Environment

Qlik Sense Desktop February 2022 and onwards
Qlik Sense Enterprise on Windows February 2022 and onwards
all Qlik Web Storage Provider Connectors 
Google Drive and Spreadsheets Metadata 

Resolution

PowerShell demo on how to generate a key:

# Generates a 32 character base 64 encoded string based on a random 24 byte encryption key
function Get-Base64EncodedEncryptionKey {
$bytes = new-object 'System.Byte[]' (24)
(new-object System.Security.Cryptography.RNGCryptoServiceProvider).GetBytes($bytes)
[System.Convert]::ToBase64String($bytes)
}

$key = Get-Base64EncodedEncryptionKey
Write-Output "Get-Base64EncodedEncryptionKey: ""${key}"", Length: $($key.Length)"

Example output:

Get-Base64EncodedEncryptionKey: "muICTp4TwWZnQNCmM6CEj4gzASoA+7xB", Length: 32

Qlik Sense Desktop

This command must be run by the same user that is running the Qlik Sense Engine Service (Engine.exe). For Qlik Sense Desktop, this should be the currently logged-in user.

Do the following:

1. Open a command prompt and navigate to the directory containing the connector .exe file. For example:

   "cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"
   
   

2. Run the following command:

   QvWebStorageProviderConnectorPackage.exe /key {key}

   Where {key} is the key you generated. For example, if you used the OpenSSL command, your key might look like: QvWebStorageProviderConnectorPackage.exe /key zmn72XnySfDjqUMXa9ScHaeJcaKRZYF9w3P6yYRr

3. You will receive a confirmation message:

   Info: Set key. New key id=qseow_prm_custom.

   Info: key set successfully!

Qlik Sense Enterprise on Windows

The {sense service user} must be the name of the Windows account which is running your Qlik Sense Engine Service. You can see this in the Windows Services manager. In this example, the user is: MYCOMPANY\senseserver.

Do the following:

1. Open a command prompt and run:

   runas /user:{sense service user} cmd. For example:runas /user:MYCOMPANY\senseserver

2. Run the following two commands to switch to the directory containing the connectors and then set the key:

   1. "cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"

   2. QvWebStorageProviderConnectorPackage.exe /key {key}

      Where {key} is the key you generated. For example, if you used the OpenSSL command, your key might look like: QvWebStorageProviderConnectorPackage.exe /key zmn72XnySfDjqUMXa9ScHaeJcaKRZYF9w3P6yYRr

3. You should repeat this step, using the same key, on each node in the multinode environment.

4. Encryption keys will be stored in: "C:\Users\{sense service user}\AppData\Roaming\Qlik\QwcKeys\"

   For example, encryption keys will be stored in "C:\Users\QvService\AppData\Roaming\Qlik\QwcKeys\"

Note:

It is important to make sure to run the command prompt with Qlik Sense Service Account and has access to all the required folders/files.

Cause

This security requirement came into effect in February 2022. Old connections made before then will still work, but you will not be able to edit them. If you try to create or edit a connection that needs a key, you will receive an error message: Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING) - you must manually set an encryption key before creating new connections.

Related Content

Setting an encryption key

Most Qlik Web Storage Provider Connectors require an encryption key. If no key exists, the following error will be displayed when authenticating:

Error retrieving the URL to authenticate: ENCRYPTION_KEY_MISSING - you must manually set an encryption key before creating new connections.

Resolution

General information, as well as a list of which connectors require an encryption key, can be found in Setting an encryption key | Qlik Connectors Help.

The actual generation of a key depends on your organization's best practices, but we can provide you with an example on how to go about it with OpenSSL:

The below example is not supported by Qlik Support. Review it with your local security office to see what method your organization follows.

1. Download and install OpenSSL.
   See https://slproweb.com/products/Win32OpenSSL.html
2. Open the OpenSSL folder (default C:\Program Files\OpenSSL - Win64\bin).
   
   
   
   
3.  Open the command prompt as an administrator and run these commands:
   1. cd C:\Program Files\OpenSSL -Wind64\bin
   2. openssl rand -base64 256
      
4. Copy and save the successfully generated key. 
   
   
   
   

5. Follow the instructions on how to set the encryption key in Qlik Sense Enterprise on Windows and/or Qlik Sense Desktop:
   
   Setting an encryption key on Qlik Sense Enterprise on Windows 
   Setting an encryption key on Qlik Sense Desktop 

6. Create the data connection. 

Related Content 

Setting an encryption key | Qlik Connectors Help
Setting an encryption key on Qlik Sense Enterprise on Windows 
Setting an encryption key on Qlik Sense Desktop 

Environment

Qlik Sense Enterprise on Windows 
Qlik Sense Desktop 

The following error can occur when using SAP BW Connector to extract data from InfoProvider/CompositeProvider.
--------
[ERR] [QVX] RfcAbapException:JOB_CANCELLED
Job aborted, check log for Job /QTQVC/READ_MPDATA in Job Overview (transaction SM37)
---------

Environment

• Qlik SAP Connector

Resolution

Reported bug QB-18952 was closed by R&D as WAD(working as designed) .

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID  QB-18952  for reference.

Workaround

From the SAP System,

1. Go to transaction SE37 and execute function module /QTQVC/GET_METADATA. 
2. Check the concerned INFOPROVIDER

The allowed maximum width  is 8192 characters.

From the INFOPROVIDER, if the field is of, for example 15282 characters wide, a simple workaround would be to split the extraction into two or more extractions. Then in Qlik Sense or QlikView, depending on your data model, use JOIN / CONCATENATE.

Cause

Product Defect ID: QB-18952

The native Qlik PostgreSql connector (ODBC package) does not import strings with more of 255 characters. Such strings are just cut off, the following characters are not shown in the applications. No warnings are thrown during the script execution.

The problem affects the Qlik connector but not all the DNS drivers.

Environment

Qlik Sense February 2023 and higher versions
Qlik Cloud

Resolution

When setting up the PostgreSQL connection, set the parameter TextAsLongVarchar  with value 1 in the connector Advanced settings.

When TextAsLongVarchar is set, and the Max String Length is set to 4096, 4096 characters are loaded. 

Notice that there still are limitations to this functionality related to the datatype used in the database. Data types like text[] are currently not supported by Simba and they are affected by the 255 characters limitation even when the TextAsLongVarchar parameter is applied.

Qlik has opened an improvement request to Simba to support them.

As workaround, it is possible to test a custom connector using a DSN driver to deal with these data types.

Internal Investigation ID

QB-21497

If Oracle is configured with a Physical Standby, and the Oracle LOG_ARCHIVE_DEST_n initialization parameter is configured with the DELAY option, running a Full Load and Apply Changes task on an Oracle Physical Standby instance may result in missing or erroneous data in the target database.

The following warning may be thrown in the log files: 

Using standby database could have caused the missing events problem during Full Load and CDC synchronization.

If you do not have the DELAY parameter configured and there is no data loss, this warning message can be ignored. Please check with your DBA if the DELAY parameter is set.

Resolution:

This issue can be resolved using an internal parameter: standbyDelayTime, which should be set to a value little bit bigger than the Delay parameter of LOG_ARCHIVE_DEST_n initialization parameter. Units are in minutes.

For information on how to set internal parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?

This solution may lead to redundant records for a table without PK/UI if there were INSERT operations during that period. Example - LOG_ARCHIVE_DEST_2 = 'DELAY=10'

Environment

Qlik Replicate

Related Content:

Supported standby configurations | Qlik Replicate Help

It may be necessary to remove line feeds (LF) and carriage returns (CR) from BLOB or CLOB datatype fields. However, Qlik Replicate tasks have a limitation on LOB fields preventing functions from being used on them.

Workaround:

Use a source lookup to retrieve the field value, bypassing the inherent data type.

The general form of the function is as follows:

source_lookup(TTL,'SCHM','TBL','EXP','COND',COND_PARAMS)

Use of the standard replace chars function:

replaceChars(X,Y,Z)

Combined usage for both functions for the transformation expression:

ReplaceChars(source_lookup(1,'DBO','table','field','id=?',$id),X'0A','|')

Related Content

Qlik Replicate Transformation: Source Lookup - CLOB datatype - limitations on string functions
Data Enrichment functions 

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.

Qlik Sense or QlikView may not load all data from a CSV file.

Resolution

Sometimes a special character is used to mark the end of the file. If this character is found in the middle of a text file (for example, enclosed by quotation marks), the file may not load correctly. In this instance, we can modify how Qlik Sense and QlikView read data. 

Qlik Sense:

1. Select the .csv file you want to load in the File Wizard
2. Set Quoting to None 
3. Check Ignore End-Of-File character? 
   
   
   

QlikView

1. Select the .csv file you want to load in the File Wizard
2. Set Quoting to None 
3. Check Ignore EOF
   
    

Cause

Due to a problem with quotes or special characters in the file. See Help Site File Wizard: Type

Environment

Qlik Sense all supported versions, including Qlik Cloud
QlikView all supported versions

After an upgrade of Qlik Replicate to May 2023 (2023.5.0.322), Databricks tasks fail with the following error:

[METADATA_MANAGE ]E: The host configured in the proxy settings is not valid [1020401] (cloud_imp.c:2138)

[METADATA_MANAGE ]E: Failed while preparing stream component 'Databricks_AdageAZ'. [1020401] (metadatamanager.c:855)

[METADATA_MANAGE ]E: Cannot create the target utility component [1020401] (metadatamanager.c:760)

[TASK_MANAGER ]E: Creating Metadata Manager's utility components failed [1020401] (replicationtask.c:3896)

[TASK_MANAGER ]W: Task 'Adage_AZ_Apply_Changes_All' encountered a fatal error (repository.c:6064)

Resolution

An upgrade of Qlik Replicate may set the proxy settings in the Databricks Lakehouse (Delta), even if no proxy has previously been used. Disable the proxy to resolve the issue.

1. Open the Databricks Lakehouse (Delta) target endpoint
2. Open the Advanced tab
3. Expand Proxy Sever
4. Uncheck Use Proxy Server 
   
   

In the data integration process from a Salesforce source to a Snowflake target, it's crucial to ensure all records are accurately captured. However, sometimes gaps can occur in Change Data Capture (CDC) operations, resulting in missing records.

In this article, we aim to explore such an issue and guide you through the required troubleshooting steps and eventual solution.

Issue

One of the source table in Salesforce is 'WorkOrder,' and discrepancies in data capture were observed in the logs. The root of the problem becomes evident when examining consecutive SELECT queries:

Query 1:

Timestamp: 2023-07-17 13:41:04.251

Query: SELECT count() FROM WorkOrder WHERE SystemModstamp > 2023-07-17T17:24:28.000Z and SystemModstamp < 2023-07-17T17:40:04Z

Query 2:

Timestamp: 2023-07-17 13:56:31.411

Query: SELECT count() FROM WorkOrder WHERE SystemModstamp > 2023-07-17T17:41:04.000Z and SystemModstamp < 2023-07-17T17:55:31Z

Upon closer examination, it's evident that the tracking column 'SystemModstamp' in Query 2, which is "> 2023-07-17T17:41:04.000Z," does not align with the previous query's 'SystemModstamp' value, which was "< 2023-07-17T17:40:04Z."

Consequently, any changes within this time period (SystemModstamp between '>= 2023-07-17T17:40:04Z' and '<= 2023-07-17T17:41:04.000Z') were not captured, leading to missing records.

Resolution

After a thorough analysis, the root cause of this issue was identified. The transaction consistency timeout of 60 seconds was found to be inadequate. To address this problem effectively, the following steps are recommended:

• Analyze Longest Transactions: Salesforce transactions vary in duration. To ensure comprehensive data capture, it's crucial to identify the longest transactions that may exceed the default consistency timeout.
  
  
• Set Transaction Consistency Timeout: Adjust the "Transaction consistency timeout" value in your CDC configuration to accommodate the longest transactions. This adjustment ensures that CDC operations span the entire duration of transactions, preventing data gaps and missing records.
  
  To set the Transaction Consistency Timeout:
  
  
  1. Open the Salesforce Source Endpoint
  2. Navigate to the Advanced tab 
  3. Locate Transaction consistency timeout (sec): and set the value accordingly
     
     

By following these steps, you can enhance the accuracy and completeness of your data capture process when loading data from a Salesforce source to a Snowflake target. This proactive approach will help prevent future instances of missing records and maintain the integrity of your data integration pipeline.

The Qlik Compose Monitor UI does not show Inserted Rows or Updated Rows for the data mart even though the rows are inserted and updated in the database.

Resolution

Upgrade to 2022.5.1032 (2022, May – sp13).

 Cause

RECOB-7493

Information provided on this defect is given as is at the time of documentation. For up-to-date information, please review the most recent Release Notes with RECOB-7493 for reference.

Environment

    Qlik Compose 2021.05 - sp11 (2022.5.0.958)

Creating and adding a new target endpoint to Azure SQL DB and testing the connection fails with:

SYS-E-HTTPFAIL, Failed to load dynamic endpoint properties.
SYS,GENERAL_EXCEPTION,Failed to load dynamic endpoint properties,Failed to get 'SQLServer_New' syntax

Resolution

Review the active Internal Parameters set in the endpoint. 

1. Go to the  Endpoint connection
2. Switch to the Advanced tab
3. Click Internal Parameters
4. Review the set parameters for a syntax parameter set to a specific value (in our example: SQLServer_New).
5. Remove the Internal Parameter.
   
   

Environment

Qlik Replicate 

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.

Running the full load on a table, it appears the data alignment is off because the target .csv file has null values when the source field is defined as not nullable. 

Environment

Qlik Replicate  
Aurora Postgres

Identifying the root cause:

Verify the source table DDL:

Examining the source table DDL will show a datatype with no precision (varchar NOT NULL,). 

Example:

Resolution

This is a documented limitation. See VARCHAR(n).

VARCHAR without a length (n) is not recognized as a valid data type by target endpoints. Consequently, if a source column data type is set to VARCHAR without an explicit length, Replicate will set a default length of 8000 bytes.

Workaround:

You can change the default by deploying an internal parameter, unboundedVarcharMaxSize, and setting a custom value. 

1. Go to the  Endpoint connection
2. Switch to the Advanced tab
3. Click Internal Parameters
4. Add unboundedVarcharMaxSize
   
   
   
   For more information about Internal Parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?

Task requirements

This task needs to capture soft deletes and allow the source table to reuse primary key values without a PK violation on the target.

Summary

Setting up this task requires four steps:

1. Add a table to the task and two fields to the target primary key.
2. Add transformations to the two new fields.
3. Configure the task to use upsert mode.
4. Show results of updates and deletes on the target table

Adding the two extra fields to the target side primary key and having the NOW timestamp ensures that the target record will be unique compared to the source record with only one field primary key.

This will allow the source to reuse a deleted records primary key without throwing a PK violation on the target. The transformations on the fields set unique values into the additional key segments.

Setting error handling and the apply conflicts handling policy to Upsert Mode (No record found for applying an Update: INSERT the messing target record) normally works by converting the source statement (whether Insert, Update, Delete) into a Delete followed by and Update. The unique three segment primary key is not able to be found during the delete which is why the records persist on the target.

The Steps

Add a table to the task and two additional fields to the target primary key

Example source table structure:

Note the single field Primary Key MyPK.

In our example, we have added Operation and OperationDateTime as the additional fields.

Example source table records:

In the Table Settings for your task, go to Transform and mark your newly added fields as target side primary keys.

In our example, we have marked Operation and OperationDateTime.

Add transformations to the two new fields

Transformation are added through the Expression Builder, located in the Table Settings. You will modify the fields marked as keys in the previous step, Operation and OperationsDateTime.

Operation: set the expression to INSERT, UPDATE or DELETE based on the source transaction. 

Transformation function:

CASE
WHEN $AR_H_STREAM_POSITION = ''
THEN "INSERTED"
ELSE operation_indicator("DELETED", "UPDATED", "INSERTED" )
END

OperationDateTime: set the expression to to NOW date time

Transformation function:

Datetime('now')

Configure the task to use Upsert mode

1. Go to Task Settings...
2. Open Error Handling and navigate to Apply Conflicts
3. Set No record found for applying an UPDATE to INSERT the missing target record
   
   
   

Show results of updates and deletes on the target table

Results in target table after updates and deleting source record #6 and reuse of primary key on source.

Target table after full load:

Target table results after updates and delete on source:

Target table after reuse of source primary key new record inserted.

Outcome

Results show that the target table is acting like an Audit table; all source transactions are stored.

The target table can have multiple records that have the same primary key on the source (MyPk 6).

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.

Related Content

Upsert/Merge
Soft Delete

Environment

Qlik Replicate 

Global expressions are not propagated to all tables. 

Defining a soft delete transformation can be done on each individual table as needed. However, if you want to do it for all tables in the task you will want to use a Global Transformation.  

Issue

The issue manifested when defining a Global Expression to do a soft delete.

The field is supposed to be automatically added to all tables in the task. The field was not added to all tables. It was random results as some tables had the field and others did not.

When reviewing the process of defining the expression we noticed there are two screens which would allow you to enter the expression.

When we used both the Transformation Scope / Advanced Options screen and the Transformation Action / Value screen, not all tables got the field. 

Example: Transformation Scope, with Advanced Options expanded:

Resolution

Environment

#Qlik Replicate 

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.

Related Content

Transformation - Operation Indicator - Archive User - Soft Delete

MySQL allows the zero date (and/or zero month) in data rows, which is a specific behaviour of MySQL and does not exist in most other RDBMS. This behaviour causes invalid date errors while replicating data to heterogeneous databases.

In this article, we will explain the solutions in both Full Load and CDC stages.

Resolution

To handle zero date in Qlik Replicate for both Full Load and CDC stages:

How to handle zero date in Full Load stage

MySQL provides an ODBC parameter ZERO_DATE_TO_MIN to control this behavior. please take note MySQL adds one day for zero date values.

1. Open MySQL source endpoint
2. Go to the Advanced tab
3. Go to the Additional ODBC connection properties
4. Add below connection string in the input label:
   
   ZERO_DATE_TO_MIN=1;
   
   

   Based on this setting, the Full Load stage gets a non-zero date. For example, the source value 2022-12-00 in MySQL will become 2022-12-01 in the target endpoint after the Full Load is finished.
   
   
   
   

How to handle zero date in CDC stage

The Full Load steps will not have an impact on the CDC stage. That means the source value 2022-12-00 will be 2022-12-00 still in the CDC stage. To mitigate this, we need to create a transformation to replace the zero date 00 with 01 as we do in the Full Load stage.

The simple global transformation expression can be:

date(substr($AR_M_SOURCE_COLUMN_DATA,1,8)||replace(substr($AR_M_SOURCE_COLUMN_DATA,9,2),'00','01'))



For more information on how to set transformations, see: Starting the Global Transformation Rules wizard.

Related Content

Transformation: Date Time - Invalid Value - MySQL

Environment

Qlik Replicate all versions
MySQL all versions

Internal Investigation ID(s)

Support case #00107317

An Automation fails with the below error when trying to run,

The following error occurred: Connector *********:****** not found (: Requested endpoint could not be provisioned due to failure to acquire a load slot: The user does not have permission to the gateway (DirectAccess-0002) LIB CONNECT TO '*********:******') The error occurred here: LIB CONNECT TO '*********:******'

Resolution

The User

• Must have at least "Can Edit" permissions for the space that the gateway is registered with.

The User needs at least "CanConsume" on both spaces:

• For the data connection space
  
• The space that the Direct Access gateway is associated with.

Note that those spaces might be one and the same, but they can also be separate.

Cause

Error "DirectAccess-0002" indicates that the User does not have permission to the gateway.

Environment

• Qlik Data Gateway  - Direct Access
• Qlik Application Automation 

In some scenarios we need stop and resume a task. However for Hana trigger-based CDC task, if the option "Use log table" is enabled, resuming the task, or while you trying to startup the task from a given timestamp, you may get the below information (with SOURCE_CAPTURE set to Trace):

2021-09-09T22:12:34:881897 [SOURCE_CAPTURE  ]T:  Resume from 'timestamp:2021-09-09T20:30:00'
2021-09-09T22:12:34:881897 [SOURCE_CAPTURE  ]T:  Start from timestamp is not supported in the Log-Table mode

Environment

• Replicate versions 6.6/7.0
• Replicate version   2021.5

The option "Use log table" is enabled by an Internal Parameter in versions 6.6/7.0. In version 2021.5 it's in GUI property like below:

Resolution

Start the task by source change position, rather than the timestamp. Here is a query to prepare the stream position in the correct format by a timestamp:

;Get the stream position by timestamp
;Before using the query, please replace the $SCHEMA$ to your artifacts schema where the table "attrep_cdc_log" is located.
;The timestamp format is 'YYYY-MM-DD HH:MM:SS' (Note, the timestamp should be the one on HAHA Server side, not the replicate server's)
;The range will be from the first (not included) event that happened after the time specified to the last (included) event in the table

SELECT 'V1:'||MIN("$rowid$")||':'||MAX("$rowid$")||':0:'||MIN("$rowid$") AS "STREAM POSITION" from "$SCHEMA$"."attrep_cdc_log" WHERE "CHANGE_EVENT_TIME" >= 'YYYY-MM-DD HH:MM:SS'

A unique row will be returned:

V1:670636:686112:0:670333

Then in the Replicate UI, start the task by source change stream position:

Internal Investigation ID

Salesforce support case #02260694.

How to Connect NPrinting to Single or Multiple Qlik Sense servers:

• You may use this article to connect to NPrinting to a single or multiple QS servers
• In some cases you may wish to connect your NPrinting server to multiple Qlik Sense server environments. The process described in this article will describe how to enable this feature and how to manage possible errors encountered.
• Note that all additional QS servers must be in the same domain as the original QS and NP servers.
• If having issues connecting to multiple Qlik Sense servers, see Qlik NPrinting will not read Qlik Sense certificates

Environments:

• This feature is ONLY available in NPrinting June 2019 release and newer versions.
• NOTE: This feature is not supported in NPrinting April 2019 and earlier versions.

Implement the solution: 

• Go to Qlik Sense QMC>Start>Certificates
• Export the Qlik Sense server certificates from each additional Qlik Sense server.
• Use the NPrinting server computer name  or the Friendly Url Alias of the NPrinting Server as the "Machine Name" that is used to log into the NPrinting Web Console with.
• Export a certificate for both if both addresses below are used to access the NP web console.
  
  • Computer name:  nprintingserverPROD1
  • Friendly URL/Alias address:  Internal.nprintingserver.domain.com

• Select include secret key and
• do NOT include a password when exporting the certificates. See Exporting certificates through the QMC on the Qlik Sense Online Help for details. 

• Navigate to the exported certificates location on the QS server and rename the exported file 'client.pfx' with a suitable name. ie: if your Qlik Sense server name is QS1, prepend the file client certificate file name as follows: QS1client.pfx (Naming of this file should ideally reflect the Qlik Sense server that the file was exported from. You may use however, any name that you wish)
• Copy this file to the NPrinting server path:
  

"C:\Program Files\NPrintingServer\Settings\SenseCertificates"

• Restart all NPrinting services
• If newly installing NPrinting May 2023 IR or later, please check this article if you are having NPrinting Qlik Sense connection failures: NPrinting Qlik Sense Connections Fail with Fresh Install of May 2023 NPrinting and Higher Version

NOTE: Reminder that the NPrinting Engine service domain user account MUST be ROOTADMIN on each Qlik Sense server which NPrinting is connecting to.

Test  access to the additional Qlik Sense server.

• Open the NPrinting Web Console
• Create a new NP App. ie: "NP_App_QSserver-2"
• Create a new NP connection and use the Virtual Proxy Address for the new target Qlik Sense server
• Verify your connection
• Save your connection to load the metadata for the first time.
• Create a test report and preview
• If having issues connecting to multiple Qlik Sense servers, see Qlik NPrinting will not read 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.

Related Content

• NPrinting Qlik Sense Connections Fail with Fresh Install of May 2023 NPrinting and Higher Version
• https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm
• https://help.qlik.com/en-US/nprinting/February2021/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#anchor-1