With Qlik SAP Connector version 8.0.2, when extracting data using  SAP BW Connector, decimal values are separated by comma instead of point. This issue occurs also in version 8.0.1.
The behavior may depend on regional settings

Example of expected behavior. 

Environment

• Qlik Sense Enterprise
• Qlik SAP Connector

Resolution

Bug QB-18820 reported to R&D was closed as fixed. A solution will be available in next release.

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-18820 for reference.

Workaround:

Step 1: Download and apply the attached patch

1. Navigate to C:\Program Files\Common Files\Qlik\Custom Data\ 
2. Copy "QvSAPBWConnector" folder and save it on another location (ex: desktop). 
3. Delete "QvSAPBWConnector" folder 
4. Download file "qvsapbwconnector-1.5.3-6+0e8c250-manual-rel.zip" and extract this file  (you will get "qvsapbwconnector" folder) 
5. Rename this folder "qvsapbwconnector" to "QvSAPBWConnector" and paste it in C:\Program Files\Common Files\Qlik\Custom Data\ 
6. Test and if required, restart Qlik services

Step 2:

1. Create a new SAP BW connection
2. Check Connection String Properies and then BEx Legacy Mode (datatypes)

Cause

Product Defect ID: QB-18820

When using Qlik Map Object to display countries like Canada, France, Spain etc., their respective overseas territories will normally not be included.
The example below shows Canada, but the Overseas Territories (see yellow circled area) are not rendered as belonging to Canada

Qlik Map object is based on OpenStreetMap data (see https://www.openstreetmap.org/copyright) and Overseas Territories have special status.

Environment

• Qlik Sene Enterprise
• QlikView
• Qlik GeoAnalytics

When using GeoAnalytics Map Extension, you may need to avoid users to overwrite the "GeoAnalytics Server URL".

• GeoAnalytics Map Extension in Qlik Sense

• GeoAnalytics Map Extension in QlikView

Thus, to hide "GeoAnalytics  Server URL" when implementing app with map extension,

1. Navigate to the location where the GeoAnalytics extensions are located 
2. Open "IdevioMap" folder >> edit "settings.js" file 
3. Set "allowCustomServer" to "false".

Environment

• Qlik Sene Enterprise
• QlikView
• Qlik GeoAnalytics

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

After upgrading Qlik Replicate may cause scheduled jobs to fail due to changes in the Scheduler functionality.

Example error: 

[UTILITIES ]E: Command request 'RESUMETASK_REQ' (55) cannot be found. [1020111] (scheduler.c:270)

In this specific example, the scheduled job didn't run because it had selected the option to "RESUME TASK",  which has been removed in more recent versions of Replicate.

Environment

• Qlik Replicate 
  Example: Upgrade from 7.0 to 2021.1

Resolution

A quick solution is to export/import the repository, below are the steps:

1. Under Replicate server -> Logging -> Log File Management -> Uncheck any Log roll over you might have
2. Replicate Server -> Scheduler -> Take a screenshot here as you'll need to recreate the jobs
3. Disable all the scheduled jobs
4. Export repository by going on cmd to Replicate bin/ folder and running:
   

   repctl exportrepository

5. It's going to create a JSON file called Replication_Definition.json under Replicate/data/imports , please backup this file by renaming it
6. Edit it with notepad++ and empty the scheduler section, it should be like this:
   

   "scheduler": {
   
   },

7. Save it and make sure it's called Replication_Definition.json
8. Import repository by running under Replicate /bin folder:
   

   repctl importrepository json_file=Replication_Definition.json

   
   If you have a custom location of the data folder, make sure you specify it by adding the flag -d before the json_file.
9. Recreate the scheduled jobs
10. Test the schedule

With Qlik Application Automation, you can get data out of Qlik Cloud and distributing it to different users in formatted Excel. The workflow can be automated by leveraging the connectors for Office 365, specifically Microsoft SharePoint and Microsoft Excel. 

Here I share two example Qlik Application Automation workspaces that you can use and modify to suit your requirements. 

Content:

• Considerations
• Example 1: Scheduled Reports
• Example 2: On-Demand Reports
• Environment

Video:

Considerations

• This example is built on distributing a SharePoint link. It is also possible to use attachments with the Mail block (see Creating a Qlik Reporting Service report).
• Qlik Application Automation has a limit of 100,000 rows when getting data out of a Qlik Sense straight table object.
• The On-Demand example uses an extension in QSE SaaS to send data to the Automation. An update to the Qlik Sense Button object is expected soon, which will provide a native way to pass selections to an Automation.

Example 1: Scheduled Reports

1. Download the 'Scheduled Report.json' file attached to this document.
2. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right clicking in the editor canvas, and selecting 'Upload workspace'.
3. Select the 'Create Binary File (Personal One Drive)' block, select 'Connection' in the block configurator to the right, and then create your connection to Microsoft SharePoint.
4. Select the 'Get Straight Table Data' block. Under 'Inputs' in the block configurator, lookup your the App Id, Sheet Id, and Object Id for the relevant QSE SaaS table you wish to output.
5. Select the 'Create Excel Table With Headers' block, select 'Connection' in the block configurator, and then create your connection to Microsoft Excel.
6. Select the 'Send Mail' block. Under 'Inputs' in the block configurator update the 'To' to reflect the addresses you wish to deliver to.
7. With the 'Send Mail' block still selected, select 'Connection' in the block configurator and add your Sender details.
8. To test, Save and then Run the Automation
9. If you receive any warnings or errors, navigate to the relevant blocks and ensure your Connection is selected in the block configurator. 
10. Select the 'Start' block. Under 'Inputs' in the block configurator, change Run Mode to Scheduled and define your required schedule. 

Example 2: On-Demand Reports

Note - These instructions assume you have already created connections as required in Example 1.

1. Download the 'On-Demand Report v3.json' file attached to this document.
2. Download and install the 'qlik-blends' extension. See: 
   https://github.com/rileymd88/qlik-blends/files/6378232/qlik-blends.zip
3. Create a new Automation in QSE SaaS, give it a name, and then upload the workspace you just downloaded by right-clicking in the editor canvas, and selecting 'Upload workspace'.
4. Ensure your Connections are selected in the block configurator for each of the following blocks, 'Create Binary File (Personal One Drive)', 'Create Excel Table With Headers', 'Add Rows To Excel Worksheet Table (Batch)', 'Create Sharing Link', and 'Send Mail'.  Save the Automation.
5. Select the 'Start' block and ensure Run Mode is set to Triggered. Make note of the of URL and Execution Token shown in the POST example. 
6. Open your chosen QSE SaaS application, and Edit the Sheet where you wish to add a Button to trigger an On-Demand report. 
7. Under 'Custom Objects' look for 'qlik-blends' from the Extensions menu and drag this into your Sheet.
8. Under the 'Blend' properties to the right, add-in your POST webhook URL and Token as noted in Step 5.
9. We will now add three measures to the 'qlik-blends' object. It is important you add them in the order described.  Add the first measure, using the following function in the expression editor: GetCurrentSelections()
10. Add the second measure, using the following function DocumentName()
11. The final measure will be the Object ID of the table you wish to use. To find the Object ID, select 'Done Editing'.  Then right click on the table, select 'Share', select 'Embed', then look for the Object ID under the preview. Copy this value, go back into Editing mode and paste this as your third measure value. 
12. With the 'qlik-blends' object selected, under Form select 'Add items'. For 'Item type' select Text. Under default value you can choose to add a default email address. For 'Label' and 'Reference'  type 'Email'. It is critical that Reference is updated to 'Email'.  Turn 'Required input' on. 
13. You can change the Appearance properties to suit your preferences, such as updating the Button label and message, enabling Dialog, and changing the Color under Theme.
14. Back in the Automation, under the Start Block. Set  'Run asynchronously' = yes to allow multiple requests to run at the same time (This will also increase the max run time from 1min to 60min)
15. Once happy, test the On-Demand report by entering an email and clicking the button.

This On-Demand Report Automation can be used across multiple apps and tables.  Simply copy the extension object between apps & sheets, and update the Object ID (Measure 3) for each instance. 

Environment

• Qlik Application Automation 
• Qlik Cloud 
• Microsoft Office 365

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.

Starting at Qlik Sense Enterprise on Windows May 2021, the bundled PostgreSQL has been upgraded to version 12.5.

However, PostgreSQL 12.5 will only be deployed during a fresh installation of Qlik Sense Enterprise on Windows May 2021. This means that, if you are upgrading to 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:

• Move Qlik Sense database to standalone PostgresSQL database in which case you will have control of which PostgreSQL version is deployed as long as it is supported by the system requirements
• Continue to use the bundled PostgreSQL with version 12.5 (see the process below)

Content:

• Step 1: Upgrading your Qlik Sense site
• Step 2: Backing up your Qlik Sense site
• Step 3: Uninstall Qlik Sense on the central node
• Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node
• Step 5: Restoring your Qlik Sense site

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.

Step 1: Upgrading your Qlik Sense site

The first step is to upgrade your environment to Qlik Sense Enterprise on Windows May 2021 following the steps and recommendations provided on this link.

Once the upgrade is done make sure your Qlik Sense site is completely operational.

Step 2: Backing up your Qlik Sense site

At this point, you have an operational Qlik Sense site running on Qlik Sense Enterprise on Windows May 2021, however, the bundled PostgreSQL is still on version 9.6.

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.

Step 3: Uninstall Qlik Sense on the central node

You will now need to uninstall Qlik Sense from the central node following these instructions.

During the uninstall:

• Have all rim nodes stopped.
• Don't check the box Remove Qlik Sense demo apps, certificates, and data folders.
• After uninstall and before reinstall rename C:\programdata\qlik to C:\programdata\qlik.old and rename C:\program files\qlik to C:\program files\qlik.old (if you changed it on another drive adjust accordingly)

Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node

Now that Qlik Sense Enterprise on Windows May 2021 is uninstalled on the central node, you will reinstall it as a result will deploy a bundled PostgreSQL 12.5. Instructions available here.

• select the same host name and database settings as before
• The file share can point at a temporary one since you will take the original one again after restoring the QSR database in step 5.

Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.

Step 5: Restoring your Qlik Sense site

You now have a clean Qlik Sense Enterprise on Windows May 2021 deployed on your central node with PostgreSQL 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.

Environment

Qlik Sense Enterprise on Windows May 2021 and later

Environment

• Qlik Sense Enterprise SaaS
• Qlik Application Automation

This article shows how to generate a report from a Qlik Sense app, upload the report to any cloud storage platform, create a sharing link, and send out an email with the link in the body. 

We can send the report as an attachment using the Send Mail block in the Mail connector, but this block only supports attachments of size 40MB. An alternative solution is to store reports in any of the cloud storage platforms that support the creation of sharing links and send emails with the links.

I will go through a few examples to show how this can be achieved using the following cloud storage connectors:

1. Dropbox
2. Microsoft OneDrive
3. Microsoft SharePoint
4. Amazon S3

I will not go through the steps on how to generate the report using Qlik Reporting blocks as it's already explained in this article.

The four automation files used in the examples are attached to this article. More information on importing automations can be found here.

Dropbox

The following steps explain how to create a public URL using the Dropbox connector.

1. Store the generated report on Dropbox using the "Copy File on Dropbox" block. Configure it to use the output from the "Generate Report" block as the Source File and set the Destination connector to Dropbox. Include the Path from the output of the "Generate Report" block in the Destination Path parameter to use the generated filename.
   
   
   
   
2. Add the "Create Sharing Link" block from the Dropbox connector to the automation and configure it to use the path of the file from the output of the "Copy File on Dropbox" block in the Path parameter.
   
   
   
   
3. Add the "Send Mail" block from Microsoft Outlook 365 connector to the automation. Configure the Content Body parameter to use the public URL generated in the step above.
   
   
   
   

Microsoft OneDrive

The following steps explain how to create a public URL using the Microsoft OneDrive connector.

1. Store the generated report on Microsoft OneDrive using the "Copy File on Microsoft OneDrive" block. Configure it to use the output from the "Generate Report" block as the Source File and set the Destination connector to Microsoft OneDrive. Include the Path from the output of the "Generate Report" block in the Destination Path parameter to use the generated filename.
   
   
   
   
2. Add the "Get Item By Path" block from the Microsoft OneDrive connector to the automation. Configure it to use the file path from the output of the "Generate Report" block in the File Path parameter to use the generated filename.
   
   
   
   
3. Add the "Create Sharing Link" block from the Microsoft OneDrive connector to the automation. Configure it to use the ID of the file from the output of the "Get Item By Path" block in the Item Id parameter.
   
   
   
   
4. Add the "Send Mail" block from Microsoft Outlook 365 connector to the automation. Configure the Content Body parameter to use the public URL generated in the step above.
   
   
   
   

Microsoft SharePoint

The following steps explain how to create a public URL using the Microsoft SharePoint connector.

1. Store the generated report on Microsoft SharePoint using the "Copy File on Microsoft SharePoint" block. Configure it to use the output from the "Generate Report" block as the Source File and set the Destination connector to Microsoft SharePoint. Include the Path from the output of the "Generate Report" block in the Destination Path parameter to use the generated filename. Use the do lookup functionality to find a Drive Id or a Site Id,  but do not specify both.
   
   
   
   
2. Add the "List Items On Drive By Site" or "List Items On Drive" block from the Microsoft SharePoint connector to the automation to get all the items on a drive/site. Use the do lookup functionality to find a Drive Id or a Site Id.
   
   
   
   
3. Add a "Filter List" block to retrieve the generated report stored in SharePoint based on the report name. Note that the report name is equivalent to the Path obtained from the output of the "Generate Report" block. Set the condition as shown in the screenshot below.
   
   
   
   
4. Add the "Create Sharing Link" block from the Microsoft SharePoint connector to the automation. Configure it to use Drive Id and Id from the output of the "Filter List" block in the Drive Id and Item Id parameter. Set the Scope parameter value to anonymous to provide access to the sharing link to anyone (including individuals outside your organization) without needing to sign in. Keep in mind that this won't work if the anonymous support is disabled by the SharePoint admin. More info about enabling the external sharing option can be found here. Also, configure the Expiration Date Time Parameter which indicates the expiration time of permission.
   
   
   
   
5. Add the "Send Mail" block from Microsoft Outlook 365 connector to the automation. Configure the Content Body parameter to use the public URL generated in the step above.
   
   
   
   

Amazon S3

The following steps explain how to create a public URL using the Amazon S3 connector.

1. Store the generated report on Amazon S3 using the "Copy File on Amazon S3" block. Configure it to use the output from the "Generate Report" block as the Source File and set the Destination connector to Amazon S3. Include the Path from the output of the "Generate Report" block in the Destination Path parameter to use the generated filename. Also, configure Region and Bucket parameters.
   
   
   
   
2. Add the "Create Presigned Object URL" block from the Amazon S3 connector to the automation and configure it to use the path of the file from the output of the "Copy File on Amazon S3" block in the Key parameter. Also, configure Region, Bucket, and Expiration parameters.
   
   
   
   
3. Add the "Send Mail" block from Microsoft Outlook 365 connector to the automation. Configure the Content Body parameter to use the public URL generated in the step above.
   
   
   
   

Related Content

• Qlik Reporting
• Multi app reports
• Microsoft Outlook 365 Connector

Can Qlik Replicate be integrated into a third-party monitoring tool, such as APM Agent?

Resolution

Qlik Replicate can be monitored using the Qlik Enterprise Manager API, but cannot be directly integrated into (for example) APM Agent for monitoring purposes.

For information on the Qlik Enterprise Manager APIs, see Qlik Enterprise Manager API guide . 

Environment

Qlik Replicate 

The below error is logged in the QlikView Server Event logs:

Error    System: file system LastWriteTimeException: Last write time for \ failed: LastWriteTimeException \ failed: boost::filesystem::last_write_time: The system cannot find the file specified: "\\servername\USA\QLIKVIEW\EXT\Document\zoomToFit\Definition.xml ": no such file or directory    550365d6-ae70-44a2-9ea8-aace5b5b8d38

For information on QlikView logs, see QlikView Services and Log Guide 

Environment

• QlikView 12.50

Resolution

Check the extension name (in red above) to make sure it is installed properly .

You can set the audit trail retention size and age using the CLI in Qlik Enterprise Manager.

The command: aemctl.exe audit_trail control [--age hours] [--size megabyte]

 See Setting the audit trail retention size and age for details.

Previous documentation versions of Qlik Enterprise Manager may refer to an incorrect syntax. Always use the most recent guide.

Scenario:

• An MSSQL to Snowflake via Logstream task
• Apply changes and store changes are both enabled
• Store before and after on update settings are used

Records are missing from the __CT table.

Resolution

An enhancement was introduced in Qlik Replicate (version 2022.11), adding a feature which forces Qlik Replicate always to write the change table entry. 

Enable the feature in the task settings:

1. Open the task settings
2. Click More Options
3. Add the following feature flag: writeEqualBeforeAndAfterImagesToChangeTable
4. Set it to On
   
   

Environment

Qlik Replicate 

Apply latency increases in a task. The target endpoint Snowflake Azure has a custom policy defined meant to mask/hide values for certain fields in the target. LOB support in the task is disabled. 

The following is logged:

00005856: 2023-04-02T00:08:37 [TARGET_APPLY ]I: Column 'Field_Name' is unsupported in table def 'table_XX' since the LOB support is disabled (metadatamanager.c:2632)

Resolution

The target table has a masking policy defined. This policy is not applied by Qlik Replicate.

Example: Field_Name VARCHAR(30) NOT NULL WITH MASKING POLICY #unknown_policy,

If there is masking policy in the target table, Qlik Replicate will consider it as a LOB column. Therefore, when LOB is support is disabled, we see the mentioned warning.

Field_Name is part of the Primary key. To prepare any update statement the PK columns, values are needed. Without them, Qlik Replicate cannot prepare the update statements.

If Qlik Replicate creates the table without a masking policy in the target table, then disabling LOB support will not impact this table to replicate all columns.

Environment

Qlik Replicate 

A Qlik Replicate task has stopped due to a Connection error at Kafka Target endpoint:

00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: Failed to get Kafka metadata: Local: Broker transport failure. _TRANSPORT [1020401] (kafka_client.c:432)
00003824: 2023-04-13T08:24:16 [TASK_MANAGER ]E: Failed while preparing stream component 'st_0_INT_Bootstrap_Kafka_Target'. [1020401] (subtask.c:853)
00003824: 2023-04-13T08:24:16 [TASK_MANAGER ]E: Cannot initialize subtask [1020401] (subtask.c:1297)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: Stream component 'st_0_INT_Bootstrap_Kafka_Target' terminated [1020401] (subtask.c:1565)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2022.11/kafka#producer-1: sasl_ssl://URL:1921: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed: broker certificate could not be verified, verify that ssl.ca.location is correctly configured or root CA certificates are installed (add broker's CA certificate to the Windows Root certificate store) (after 82ms in state CONNECT) [1022601] (kafka_client.c:236)
00003824: 2023-04-13T08:24:16 [TARGET_APPLY ]E: RDKAFKA - 3 - ERROR: [thrd:app]: QlikReplicate/2022.11/kafka#producer-1: sasl_ssl://URL:9093/bootstrap: SSL handshake failed: ssl\statem\statem_clnt.c:1921: error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed: broker certificate could not be verified, verify that ssl.ca.location is correctly configured or root CA certificates are installed (add broker's CA certificate to the Windows Root certificate store)

Resolution

Add broker's CA certificate to the Windows Root certificate store. Once this is done, put the cert file on the Qlik Replicate installation server and refer to the .pem at the CA path field.

After updating the EP settings with the above-mentioned, restart the task or stop and resume so the changes will take effect. First, test the connection using the test connection button.

Environment

Qlik Replicate 

When trying to use Qlik Data Transfer for the first time after a correct installation, you might have the below white screen:

Having a white screen basically means one of the Qlik DataTransfer micro service is not started and/or not working. This can be checked in the Windows Event Application (Source: Qlik Sense Service Dispatcher) or in the Qlik DataTransfer logs (C:\ProgramData\Qlik\DataTransfer\Log).

In the \DataUploadService logs you will see this error message:

localhost 6.0.0 Global INFO Responding certificates after reading it from defined location.
localhost 6.0.0 Global ERROR Unable to unlock the ReloadService, cannot continue.
localhost 6.0.0 Global ERROR Exception: Error: Unable to unlock the reload service.

Resolution

This error message is happening directly after the step of reading certificate:

INFO Responding certificates after reading it from defined location.

Verify the certificate:

Verify what certificates you have listed in the MMC console.

1. Are no certificates listed?
   
   
   
   

2. A group policy or other system security settings may have prevented certificates from being installed. Follow the Reset certificates steps found in the second half of the article after lifting potential restrictions on the account or machine which previously prevented the certificates from being installed. 

3. If you see some Qlik DataTransfer duplicate certificates (fig 1), duplicates must be deleted.
   
   fig 1
   
   
4. Delete the two duplicates (which have no Friendly Name listed. 
5. Restart the Qlik DataTransfer service.

Are other Qlik Products installed on the same server?

Installing Qlik Sense Enterprise on Windows (Desktop or otherwise) will also lead to compatibility issues, including certificate mismatches.

1. If the other product was previously uninstalled, the certificate may still be present.
2. Verify in the MMC console and navigate to Certificates (Local Computer) --> Personal -- Certificates to see if another QlikClient certificate is installed.
3. Remove it.
4. Then follow the Reset Certificates steps found below.

Are you using a Proxy?

A proxy system variable may be set in Windows. Example: https_proxy=http://PROXY:80 

Qlik Data Transfer does not support the use of a proxy. Delete the Windows variable.

Reset Certificates 

If only Qlik DataTransfer is installed on the machine, do the following:

1. In Windows Services, stop the Qlik DataTransfer service.

2. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and delete the certificates there.
   
   

3. Navigate to C:\Program Files\Qlik\DataTransfer\DataUploadService\install-utils.

4. Run Remove-Certificate.ps1 in PowerShell.

5. Delete the following folder: C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate
   

6. Start the Qlik DataTransfer service.

7. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:

   • client.pfx

   • server.pfx

If Qlik DataTransfer and Qlik Sense Enterprise on Windows are installed on the machine, do the following:

1. In Windows, Services, stop the Qlik DataTransfer service.

2. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and delete the certificates in the folder.
   
   

3. In the Windows Certificate Store, delete the following certificates:

   • Local Computer > Personal > QdtClient

   • Local Computer > Trusted Root Certification Authority > <hostname.domain> or <hostname>

   • Current user > Personal > QdtClient

   Alternatively, you can run Remove-Certificate.ps1 in PowerShell as the administrator.
   
   

4. Run Configure-Service.ps1 in PowerShell as the Qlik Sense services user.

   1. For the first input dataTransferCertificatePath, enter C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate.

   2. For the second input qsefwPresent, enter Yes.

5. Navigate to C:\ProgramData\Qlik\DataTransfer\DataUpload\certificate and confirm the following files are present:

   • root.pfx

   • client.pfx

   • server.pfx

6. Restart the Qlik DataTransfer service.

Related Content 

Installing and Using Qlik DataTransfer  
Troubleshooting Qlik DataTransfer 

Environment

Qlik Data Transfer any release

The distribution of QlikView apps from QlikView Distribution Service to Qlik Cloud fails with the error "TestCloudLicense: Failed - Unauthorized. Failed to retrieve qv_nodes tag."

Environment

• QlikView 
• Qlik Cloud 

Resolution

• The license used in Qlik Cloud is missing the QV_NODES tag, which allows the access to QlikView apps from Sense Deployments. For QlikView to distribute to a Qlik Cloud tenant,  the tag must be present in the tenant license.

Please, reach out to your account manager to have that fixed.

• This issue could also occur if there are missing configuration entries in he QVDistributionService.exe.config  file, refer to the following article QlikView Distribute to cloud fails: The type initializer for System.IdentityModel.Tokens.Jwt.JsonExtensions threw an exception.

Your Qlik Cloud license includes information on what licenses and features are enabled for you. You will receive a list of all your enabled features in your original license email and we always recommend to store the email for future reference.

However, you can also call the License APIs in your browser and obtain information on what features are included in your license from there.

Resolution

1.  Access your tenant's URL and authenticate
   
   
2. Append /api/v1/licenses/overview to the URL
   Example: https://mytenant.myrg.qlikcloud.com/api/v1/licenses/overview
   
   
3. The information will be visualized in the browser
   
   
   • Most browsers will show the raw JSON format 
     
     
     

      

   • Other browsers (such as Firefox) have a built-in JSON visualizers:
     
     
     
     
4. Search for the key that you are expecting to find and the values associated with it to confirm that the feature is enabled:
   
   

   {"name":"qvNodes","valid":"./.","values":{"count":3}},

   {"name":"reportingService","valid":"./.","values":{"quantity":1000,"value":""}}]​

Environment

Qlik Cloud 

Testing the connection to an AWS RDS hosted Mariadb database fails with:

SYS-E-HTTPFAIL, No MySQL ODBC Unicode Driver version x.x or above is installed..
SYS,GENERAL_EXCEPTION, No MySQL ODBC Unicode Driver version x.x or above is installed.

Resolution

Verify that the Qlik Replicate documentation was followed correctly and that the /etc/odbcinst.ini file contains an entry for MySQL. See Driver prerequisites | Qlik Replicate Help.

If a new driver was installed, it may have overwritten a previous entry or wrongly added a new one.

Per Qlik documentation:

[MySQL ODBC 5.3.13 Unicode Driver]
Driver = /usr/lib64/libmyodbc5w.so
UsageCount = 1

Per the driver installation:

[MySQL ODBC 5.3 Unicode Driver]
Driver=/usr/lib64/libmyodbc5w.so
UsageCount=1

Remove .13 in the .ini file to resolve this.

Environment

Qlik Replicate