Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in Manage Cases. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
This article gives an overview of the available blocks in the Qlik Platform Operations connector in Qlik Application Automation.
The purpose of the Qlik Platform Operations connector is to simplify the deployment and management of multiple tenants within Qlik Cloud. To learn more about the multitenant model in Qlik Cloud, please review the following series of tutorials.
This connector consists of:
To authenticate, you will need to provide your OAuth2 client ID and client secret. If you have a multitenant license, enter a regional OAuth client (generated via My Qlik) or a tenant OAuth client (generated from within a tenant). Note that only regional OAuth clients can create new Qlik Cloud tenants. In order to use your own tenant, you need to create an OAuth m2m client (trusted) in the management console on your tenant. For more information, please check this article.
Most blocks require a specified tenant as the target. A tenant is uniquely identified by name and the region that it is deployed to. For example, for mytenant.eu.qlikcloud.com, enter mytenant.eu. You can use the Get Tenant Name and Region block to obtain the tenant from a full URL.
Let's now go over a basic example of how to deploy a tenant, create an automation inside the deployed tenant and run it using the Qlik Platform Operations:
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.
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.
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
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
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:
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"
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
You will receive a confirmation message:
Info: Set key. New key id=qseow_prm_custom.
Info: key set successfully!
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:
Open a command prompt and run:
runas /user:{sense service user} cmd. For example:runas /user:MYCOMPANY\senseserver
Run the following two commands to switch to the directory containing the connectors and then set the key:
"cd C:\Program Files\Common Files\Qlik\Custom Data\QvWebStorageProviderConnectorPackage"
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
You should repeat this step, using the same key, on each node in the multinode environment.
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.
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.
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.
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)
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.
QB-20735
Qlik Sense Enterprise on Windows May 2023 Patch 3 and later
Does not affect August 2023 and later releases.
QB-20735
To install or upgrade your existing Qlik NPrinting governance dashboard, simply deploy the new QVF and reload the app: NPrinting Governance Dashboard - version3
If and only if you have altered the engine.config file(s) on your NPrinting Engine computer(s) to change the default 'resolvers-count' value, then go to the 'deployment summary' sheet and enter the 'resolvers-count' value under 'Available Resolvers'. This value sets a baseline that the new concurrency metric can evaluate to ensure your NPrinting environment is not core constrained.
Please enjoy and post comments/suggestions in GitHub preferably, or in the community comments below.
Version 3.0 (4/12/2022)
-Fixed a bug introduced by NP May 2021 SR3 where the reload fails in the load script:
< Field 'id' not found FROM "nprinting"."public"."task_execution" >
-Updated background colours on the "Task Recipients" Pivot Table to green
Version 2.0
Deployment Summary Sheet:
-New KPI "Peak Connection Concurrency". This is the number of unique connections used at any one time by executing publish tasks, subscriptions, on-demand requests, or metadata reload requests. It does not include preview requests. If this number exceeds 60% of your resolver count, queuing is expected to occur and reports will take longer to run. The metric will turn red indicating it is time to add logical engine processors to your NPrinting Engine(s) to a maximum of 16 logical processors per engine.
-New KPI "Peak Execution Concurrency". This is the number of concurrent execution requests at any one time . It is the sum of executing publish tasks + executing subscription requests + executing onDemand Requests + executing Metadata reload requests. If multiple reports are running in a single publish task, it counts as just '1' in this resolver . Does not include 'preview' requests.
Report Delivery Sheet:
-New filters added
Data Connections Sheet:
-New filters added
-Section Access field (yes/no ) added
Qlik Lineage Sheet:
-New filters added
-New KPIs added: Complex reports , Medium reports, simple reports
App Content Sheet:
-new filters added
Task Recipients Sheet:
-new filters added
Execution Analysis Sheet:
-New table "Days when Concurrency Exceeded". Shows the number of days where the peak concurrency connections exceeds 60% of vResolvers.
-New table "Peak Concurrency by Day". Shows peak concurrency by day.
Report Performance Sheet:
-Container with 4 distribution plots showing execution length for publish tasks, subscriptions,ondemand requests and metadata reloads. Colored by status (green = success, red = failed)
-Container with 4 tables showing detailed executions
Users Sheet:
-New Filters added
Execution Log Messages:
-New Filters added
Load Script / Model:
- vResolvers variable set to the sum of logical processors on each NP engine found
section access field added to connections
New master date table intervalmatched to executions.
vMonthsToLoad variable determines how many trailing months to generate in the master date table (default is 3 months)
For anybody upgrading you will need to re-edit the data source in the load script and if and only if you have changed the resolvers-count setting in the NPrinting engine.config file .... then after reloading the app , go to the deployment summary sheet and update the vResolvers variable to be equivalent to the same value as 'resolvers-count' in the engine.config. If you have multiple NP engines, sum the number together and set vResolvers to the sum of the values found in the engine.config files.
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.
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.
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
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
SAML is not supported by default in QlikView but can be implemented by creating a custom authentication module that will convert SAML requests/responses to QlikView Ticket to log the user in.
This customization is provided as is. Qlik Support cannot provide continued support of the solution. For assistance, contact our Professional Services or engage in our QlikView Integrations forum.
Currently, this solution only works for SP initiated authentication. Making it work for IDP-initiated authentication might require further code changes in the library/module source code.
This has been tested with QlikView 12.10 SR7.
<GetWebTicket url="/QvAjaxZfc/GetWebTicket.aspx"/>
to<GetWebTicket url="/QvAjaxZfc/GetWebTicket.aspx">
<TrustedIP>fe80::b178:730a:5c2a:86d2%11</TrustedIP>
</GetWebTicket>
public void ValidateAttribute(SamlAttribute samlAttribute)
{
if (!Uri.IsWellFormedUriString(samlAttribute.Name, UriKind.Absolute))
throw new DKSaml20FormatException("The DK-SAML 2.0 profile requires that an attribute's \"Name\" is an URI.");
after
public void ValidateAttribute(SamlAttribute samlAttribute)
{
/*
if (!Uri.IsWellFormedUriString(samlAttribute.Name, UriKind.Absolute))
throw new DKSaml20FormatException("The DK-SAML 2.0 profile requires that an attribute's \"Name\" is an URI.");
*/
<QlikViewSaml
accessPointUrl="https://qlikserver1.domain.local/"
authenticatePage="QvAjaxZfc/Authenticate.aspx"
webTicketPage="QvAjaxZfc/GetWebTicket.aspx"
tryPage="https://qlikserver1.domain.local/qlikview/"
backUrl="https://qlikserver1.domain.local/webticketerror.html" />
Replace https://qlikserver1.domain.local/ by your qlikview server URL in the above code.<AllowedAudienceUris>
<Audience>https://qlikserver1.domain.local</Audience>
</AllowedAudienceUris>
<Federation xmlns="urn:dk.nita.saml20.configuration">
<SigningCertificate findValue="CN=qlikserver1" storeLocation="LocalMachine" storeName="My" x509FindType="FindBySubjectDistinguishedName"/>
*In this case, we use a certificate that has "CN=qlikserver1" as its distinguished name.<IDPEndPoints metadata="C:\idpdata\">
...
After upgrading QlikView to May 2023 IR, charts may show as blank objects in Qlik NPrinting.
Qlik NPrinting Designer displays the images correctly in preview mode.
Qlik NPrinting Any version
QlikView May 2023 IR
Nprinting Reports: Excel, PowerPoint, PDF
This is currently being investigated.
The issue is found to be with QlikView May 2023 IR not with any Qlik NPrinting versions. It works perfectly fine with QlikView May 2022 SR2 and earlier supported QlikView versions.
Also, the problem occurs when Qlik View Server Connection is used in Qlik NPrinting connections.
QV-24977
Information on this defect is given as is at the time of documenting. For up-to-date information, please review the most recent Release Notes with the ID QV-24977 for reference.
After upgrading to QlikView 12.70 SR2 users cannot open documents from the AccessPoint once the session timeout is reached. The following error is displayed:
Failed to open document, You don't have access to this document
QlikView May 2022 (12.70) IR to SR2
This is caused by QV-24743 and QV-24830.
Fix scheduled to be released in:
Upgrade to the appropriate version when it has become available. Refer to the QlikView Release Notes for details once the versions have been released.
QV-24743 and QV-24830
This article provides information on how to get started with the ServiceNow connector in Qlik Application Automation.
The connector for ServiceNow is making use of Basic Authentication. To connect you will also need the name of your instance.
When you connect to ServiceNow in Qlik Application Automation you will be presented with the following screen.
You can obtain the instance name from the URL that you use to access ServiceNow. You can use your username / password of your account provided it has enough privileges for what you aim to do. It is recommended to create a service account for integrations and limit it's roles to what is necessary.
Most of the blocks for the ServiceNow connector make use of the Table API of ServiceNow.
ServiceNow documentation for the Table API can be found at: https://developer.servicenow.com/dev.do#!/reference/api/rome/rest/c_TableAPI
The following data types have easy to use blocks for all CRUD operations:
• Incident
• Change Task
• Problem
• Change Request
Furthermore it is possible to work with user objects, listing journal items, audit lines, obtaining and adding attachments.
When modifying or deleting objects from the Table API, make sure to be using the "sys_id" field of objects as the identifier.
With the blocks "get table content by id", "create table content", "delete table content", "update table content", "list table content", it is possible to work with every object through the use of the Table API. These blocks also allow you to look up the name of a table with the "do lookup" functionality. As this lookup obtains information from the sys_db_object table in ServiceNow, it's possible that this lookup does not work due to your permissions.
There is also a "Raw API Request" available. This block allows providing your own sub path starting from the Base URL of ServiceNow, HTTP method and optionally a JSON body.
This can be used to contact other API groups than the Table API of ServiceNow as well as custom scripted API's.
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.
If after the procedure is completed errors are logged of a wrong password, see Qliksenserepository password error in the event logs after changing the database service user password for further information.
# TYPE DATABASE USER ADDRESS METHOD
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5
Updated:
# TYPE DATABASE USER ADDRESS METHOD
# IPv4 local connections:
host all all 127.0.0.1/32 trust
# IPv6 local connections:
host all all ::1/128 trust
cd "C:\Program files\Qlik\Sense\Repository\PostgreSQL\12.5\bin"
*12.5 refers to the PostgreSQL version. Adjust accordingly depending on what version is installed. psql -h 127.0.0.1 -p 4432 -U postgres
The response will provide the postgres=# prompt, which we will use to change the passwords.alter user postgres with encrypted password 'EnterYourNewPasswordHere';
Response:
alter user qliksenserepository with encrypted password 'EnterYourNewPasswordHere';
Response:This concludes the required steps.
To verify if the password was correctly changed, you can either run psql again, connect with the PGAdmin, or review the Qlik Sense Repository log for success messages on boot.
If after the procedure is completed errors are logged of a wrong password, see Qliksenserepository password error in the event logs after changing the database service user password for further information.
This article explains how the Qlik Reporting connector in Qlik Application Automation can be used to generate a bursted report that delivers recipient-specific data.
For more information on the Qlik Reporting connector, see this Reporting tutorial.
This article offers two examples where the recipient list and field for reduction are captured in an XLS file or a straight table in an app. Qlik Application Automation allows you to connect to a variety of data sources, including databases, cloud storage locations, and more. This allows you to store your recipient lists in the appropriate location and apply the concepts found in the examples below to create your reporting automation. By configuring the Start block's run mode, the reporting automations can be scheduled or driven from other business processes.
In this example, the email addresses of the recipients are stored in a straight table. Add a private sheet to your app and add a straight table to it. This table should contain the recipients' email address, name, and a value to reduce the app on. We won't go over the step-by-step creation of this automation since it's available as a template in the template picker under the name "Send a burst report to email recipients from a straight table".
Instead, a few key blocks of this template are discussed below.
In this example, the email addresses of the recipients are stored in an Excel file. This can be a simple file that contains one worksheet with headers on the first row (name, email & a value for reduction) and one record on each subsequent row.
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.
Importing a Qlik Sense App (.qvf) in the Qlik Sense Management Console fails. There are various causes for this issue and this article will help in identifying the most common root causes.
In the process of importing an App one must access the Sense QMC, Start-> Apps -> Import
- Select a QVF (App) to import using the Browse, and select <Import>.
This process will result in one of the following:
Review the log file for more detailed errors to assist in further troubleshooting. For basic log file information, see Logging Storage.
Locate the logs in the following locations:
C:\ProgramData\Qlik\Sense\Log\Repository\Trace\SERVERNAME_System_Repository.txt
C:\ProgramData\Qlik\Sense\Log\Engine\trace\SERVERNAME_System_Engine.txt
Note: If you are running a multi node environment, each node will have its own local copy. Review all of them. In addition, if the logs have been archived since the issue occurred, review the location of the archived log, which by default is in the configured Service Cluster location.
Verify that the account running the Qlik Sense Services has the correct permissions: It requires Read/Write permissions.
In the case of large Apps, verify that enough disk space is available. Check the available space on the central node's C:\ disk. Even if Sense is installed on another drive, C:\ (and its temporary folder) will be used for the calculation.
At least 2 times the App size need to be available for the import to succeed.
Example: If the app is 8 GB then a minimum of 16 GB free disk space is required to Import the app.
Qlik Sense shows error when importing an app - log files read "request entity too large"
Cannot import App (qvf) to the QMC "Failed to import app. Please check the log file"
Import of apps in Qlik Sense failed when FIPS is enabled
All users with the Automation Creator role can create automations.
To add or remove the Automations Creator role:
Automations at large can be enabled or disabled as a feature in Qlik Cloud. See Managing automations for more information on how to manage automations.
Also see a related video posted on Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly
This option is available in Qlik Sense June 2018 Patch 1 and later releases.
Description of related problem:
Getting errors "Connection to the Qlik Sense engine failed for unspecified reasons. Refresh your browser or contact our system administrator" for external users on other browsers except for IE when they open the Qlik sense app and leave it inactive until it exceeds the Firewall session idle timeout. This is followed by a connection reset for the TCP WebSocket session.
For Qlik Sense Enterprise for Business (Cloud), see Loading of an app is hanging when using QlikSense Cloud.
Cause:
TCP WebSocket connection is terminated by the firewall because the firewall is not receiving any TCP traffic such as keep-alive packets from client browser (e.g. Firefox, older Chrome versions). Specific web browsers have their own tcp keep-alive behavior.
This issue may be found with less frequency with IE because it sends the TCP Websocket keep-alive more frequent than any other main stream browser. Here are the default intervals for the three main browsers latest releases as of September 2020:
Default TCP-Keep-Alive intervals:
General info
This functionality is by default switched off not to affect any existing customers. Customers who do not experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it will send unnecessary traffic on the network. See How are WebSockets used in QlikSense ? for more information.
<add key="WebSocketPingInterval" value="0"/> <!-- Interval in seconds for the web socket ping to the client (a value of "0" is disabling the ping)–>
Where value is a suitable positive number depending on the inactive web socket timeout setting in the network. The effective interval that the Qlik Sense Proxy server will send keep-alive messages towards the client my oscillate between 2 x value and 1 x value, since it also takes into account backend inter-process socket activity. Eg: setting the value of WebSocketPingInterval to 30 may lead to keep-alive messages sent to the client every 30 or 60 seconds.It is possible that the same WebSocketPingInterval value has different behaviors in each Qlik Sense Hub section due to various network device. The value may keep the connection live in Dashboard but still lose connection in Data Load Editor. You may test with a lower WebSocketPingInterval value until the proper value is found to keep connection in all sections. For example, when connecting CloudFlare as web application firewall, the WebSocketPingInterval value may need to set to 10 seconds otherwise "connection lost" may still be received in Data Load Editor even the rest of Qlik Sense Hub keeps connected.
4. Restart the Qlik Sense Proxy Service.
Setting sensitivity in Qlik Catalog allows you to mark certain fields as sensitive, indicating that they require extra care to maintain security and privacy.
When exporting data, the chosen obfuscation method is automatically applied to sensitive fields to ensure confidentiality. Users are prompted to select the obfuscation method during the export process.
In more detail, administrators can configure sensitivity settings for individual fields, deciding which ones should be considered sensitive. Sensitivity enforcement applies obfuscation to sensitive fields upon export, hiding or transforming the data. Administrators can choose from different obfuscation methods like CharClassObfuscator, DigestObfuscator, NumericObfuscator, ConstantValueObfuscator, and DictionaryObfuscator.
Each method has its own way of transforming or masking the data. By selecting a specific obfuscation rule for sensitive fields, administrators can control how the data will be transformed when exported.
Examples of obfuscation methods include replacing digits and letters, converting values into hash codes, modifying numeric values, returning constant values, or mapping data to different values using a dictionary.
Overall, Qlik Catalog provides a way to manage sensitivity and apply obfuscation methods to protect sensitive data when published, ensuring that it remains secure and confidential.
To use the sensitivity feature for source fields:
Note:
The sensitivity feature for fields only applies when you publish to a target location using the Publish option in Catalog.
Qlik Catalog
Attempting to start the Data Movement server on Linux (service repagent start) fails with the following error:
Failed to start service
One of following error messages can be seen in the repsrv.log file in such scenarios.
Failed to write file
Failed to write entire file
The root cause is likely a lack of storage. See the Data Movement system requirements for details: Recommended hardware. Either free up storage by removing unnecessary files or directories, or increase the available capacity.
To verify current capacity run df -h from the root ( / ) directory.
To review which directories take up the most space run the following from root:
sudo du -h --max-depth=1 | sort -rh
To find files larger than 100MB which may clutter the storage, run:
sudo find / -type f -size +100M -exec ls -lh {} \;
Directory has reached 100% capacity and has consumed all of the storage that was available.
Qlik Data Movement
Opening the Qlik Enterprise Manager Analytics tab fails with the following error:
SYS-E-JSERVNAVAIL, Java service 'AnalyticsCtlClient' not yet available
SYS,JAVA_SERVICE_NOT_AVAILABLE,AnalyticsCtlClient(statusCode: 500
Reviewing the service log files indicates:
Failed to start jetty server. Failed to bind to /127.0.0.1:3102
A simple reboot of the server running the Qlik Enterprise Manager may resolve the issue. If the issue persists after a reboot, the process occupying port 3102 may need to be killed manually.
In this article, we will outline steps listed in the user guide with the addition of screenshots for Windows installations for replacing self-signed certificates. We take these steps to ensure a secure connection to Replicate.
1. Stop the Replicate UI and Server services
2. As administrator, from the following location, C:\Program Files\Qlik\Replicate\bin, run
RepUiCtl.exe certificate clean
3. Create a new private key file (note this will be generated in the current working directory):
openssl genpkey -algorithm RSA -out private.key -outform PEM
4. Create the cert.crt file based on the private key file created earlier:
openssl req -new -addext "subjectAltName = DNS:SSL-TEST.exampledomain.com" -key private.key -x509 -days 365 -out cert.crt
5. Create the cert.pfx file based on previous info:
openssl pkcs12 -export -certpbe PBE-SHA1-3DES -keypbe PBE-SHA1-3DES -nomac -inkey private.key -in cert.crt -out cert.pfx
6. Import the newly created certificate, by double clicking on the cert.pfx file generated in previous step. This will open the 'Certificate Import Wizard.'
Select, 'Local Machine' and click next.
7. Specify the cert.pfx file you want to import. Click 'Next' and then enter the password from step #3.
8. Select 'Automatically select the certificate store based on the type of certificate', then click 'Finish'.
9. Open up Windows MMC for Certificates on Local Computer.
10. Place the newly imported certificate in the 'Trusted Certificates' folder
11. Run the command to delete anything current
netsh http del sslcert ipport=0.0.0.0:443
12. Double click on the certificate in trusted certs folder to find the certificate thumbprint under the details tab
13. Use this thumbprint in the certhash of following command:
netsh http add sslcert ipport=0.0.0.0:443 certhash=b26fae671d12ab9afcc82cd93321f7e00dc300d6 appid={4dc3e181-e14b-4a21-b022-59fc669b0914}
Restart the services and check if you have the lock icon on your Replicate URL.
Note: For chrome, you may need to also add the certificate to chrome://settings/security -> 'Manage device certificates' -> Trusted Root Certificate Authorities.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
The 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)
---------
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.
From the SAP System,
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.
Product Defect ID: QB-18952