Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
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 the Case Portal. (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:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
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.
Beginning with the Qlik Sense Enterprise on Windows May 2024 release, the Hub and DevHub no longer display an About menu option.
Previous versions allowed for access to the About information from their respective menus:
Any versions at or beyond May 2024 had the option removed:
To access version information or other product details, use the Qlik Sense Management Console or the About Service API (System Info: Get).
Example use from a supported browser:
https://<server name>/api/about/v1/systeminfo
The About menu option has been removed from the Hub and DevHub to address security concerns.
IM-6008
The purpose of this article is to provide details about enabling Full Load Passthru filter in Qlik Cloud Data Integration (QCDI) and get the selected data from the source during the initial load of the Landing or Replication Tasks.
The information in this article is provided as-is and will be used at your 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.
A connection through a Snowflake connector may fail if:
Qlik Sense Enterprise on Windows
Set up proxy as a system environment variable instead of using it as a connector-level advanced parameter.
This can be done by running the command below in an admin command prompt on the affected system(s), and rebooting the system
setx https_proxy "http://proxyserver.company.com:port" /M
Adding system-wide environment variables risks breaking other vendor's apps.
This document is a general guide and is provided as is. Modifications to the process may be necessary depending on your individual database setup.
If you have installed a standalone PostgreSQL database, or if you have used the Qlik PostgreSQL Installer (QPI) to upgrade and decouple your previously bundled database, then you can upgrade PostgreSQL at any time. This means you control maintenance and can immediately react to potential PostgreSQL security concerns by upgrading to a later service release or a later major version.
Content
This document covers the following scenario:
Run a complete backup of Qlik Sense Enterprise on Windows site as described in Backup and restore Qlik Sense Enterprise on Windows.
These steps apply if you are upgrading within a major PostgreSQL release (example: 14.5 to 14.8).
No further steps are required.
If you are moving to a higher major version, an in-place upgrade will not be possible. Instead, we will install the the new version in parallel, then then migrate the old database and eventually uninstall the old version. Our example is written using PostgreSQL 12 to 14.
Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer
How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version
Changing the Database Superuser Password without Qlik Sense Installed
For almost all services or APIs running in production, the requirement exists to secure access to the service. In the rest of this article, we will look at how to ensure the following security requirements:
This article shows you how to implement these concepts when running data services or Routes in the Talend Runtime. The focus is on the cloud runtime, but also applies to on-premises environments. Microservices are not handled in this article.
The attached security.zip file contains a Talend Studio v7.0 project with a sample service and Route to experiment with. It can be imported into any Talend Studio v7.x. In addition, it contains sample configuration files for the LDAP login module described later.
For REST-based services, in a cloud environment, Talend provides support only for basic authentication, where the user name and password are sent in an HTTP header alongside the request in clear text. Therefore it is mandatory to use HTTPS instead of HTTP as the protocol to ensure that the password is encrypted. Contrary to on-premises, for cloud environments, SAML token and OAuth are not supported. If more sophisticated solutions are required, Talend recommends using an API Gateway to secure and control access to the services and APIs. Talend Help provides information on how to integrate with API Gateways and examples for deployment on AWS API Gateway and Azure API Management.
Activating basic authentication for a service or a Route is done in Talend Studio in the corresponding REST component (tRESTRequest in a data service, or cREST in a Route). A data service where authentication is enabled is shown below:
Figure 1: Authentication enabled data service
Enforcing authentication information when sending the request to the service is only half the story. The provided identity must be validated and compared to the set of accepted identities. Talend Runtime provides an authentication framework based on Java Authentication and Authorization Service (JAAS), which allows you to plug in different modules targeting a specific backend to validate identity information. Out of the box, Talend Runtime is configured to support a file-based backend, but among others LDAP can also be used to validate. For a complete list of supported backends, see the Apache Karaf documentation.
The PropertiesLoginModule login module is the one configured by default in the Talend Runtime. It is based on the ${Runtime_Home}/etc/users.properties file, which uses the properties file format. Each property represents an identity. The format of the property is as follows:
user=password[,role][,role]...
Several roles may also be grouped together and the group can be referenced in the user entry:
_g_\:group=role[,role]... user=password[,role][,_g_\:group]...
The figure below shows the users.properties file, which is part of the Talend Runtime installation. In addition to the standard users tadmin, tesb, and karaf, two users alice and bob were added.
Figure 2: Sample users file
Passwords in the properties file are in clear text by default, but can be hashed to ensure protection. To automatically hash passwords after restarting the runtime, open and edit the <Runtime_Home>/etc/org.apache.karaf.jaas.cfg file.
The encryption.enabled property must be set to true. Furthermore, the encryption algorithm in the property encryption.algorithm should be set to something like SHA-256. The configuration file should look like this:
Figure 3: org.apache.karaf.jaas.cfg
The properties file solution is fine to quickly get some identity information defined, for example, when testing, but does not scale well. Furthermore, in many cases, identity information is stored in some LDAP server or Active Directory. Talend runtime provides an LDAP module to validate identity information using the information stored in LDAP or Active Directory.
The security.zip file includes the OSGi Blueprint bundle file authentication/LDAP-login-config.xml, which activates the LDAP login module when deployed into the runtime, and the authentication/org.talend.esb.jaas.ldap.cfg file to configure the login module and adapt it to the specific environment.
Table 1: LDAP login parameters for authentication
Name |
Description |
connection.url |
The LDAP URL, for example, ldap://ldap-host.example.com:389 |
connection.username |
Username to connect to LDAP, for example, cn=admin,dc=example,dc=com. The user requires read access to the part of the Directory Information Tree (DIT) where the user information is stored. |
connection.password |
User password to connect to LDAP. |
user.base.dn |
The LDAP base DN used to look up users, for example, ou=users,dc=example,dc=com. |
user.filter |
The LDAP filter used to locate the user applied to the subtree specified in user.base.dn, for example, (uid=%u) where %u will be replaced by the username. |
user.search.subtree |
If “true”, the user lookup will be recursive (sub). If “false”, the user lookup will be performed only at the first level (one). |
authentication |
Specifies the authentication method used when binding to the LDAP server. The default is simple, where a username and password is required. To enable anonymous, set to none and leave username and password blank. |
Edit the configuration file and adapt the settings to your environment. Table 1 provides a list of the properties to be configured and their meaning. The configuration file also contains the description for each property. The sample values in Table 1 and in the configuration file correspond to the Directory Information Tree (DIT) structure shown in Figure 4.
When finished with editing, copy the configuration file to the directory <Runtime_Home>/etc.
Deploy the authentication/LDAP-login-config.xml file into the Talend Runtime. The easiest way to deploy it is to copy the file to the deploy folder of the Talend Runtime, <Runtime_Home>/deploy.
Often the LDAP server or Active Directory requires the use of Secure LDAP (LDAPS) to ensure the communication is encrypted. The LDAP login module also supports LDAPS, but in addition requires a keystore containing the X.509 certificate of the LDAP server. The location of the keystore and required passwords are specified in the OSGi Blueprint bundle file, which contains the specification of the LDAP login module.
security.zip includes an extended version of the OSGi Blueprint bundle file ldaps/LDAP-login-config.xml with an additional section for the keystore, and ldaps/org.talend.esb.jaas.ldap.cfg with additional properties to configure the keystore-related parameters. Table 2 provides a list of the additional properties that need to be configured.
Name |
Description |
truststore.path |
Absolute path to a trust store containing required Active Directory certificates, for example, /opt/talend/7.2.1/runtime/etc/keystores/ldaptruststore |
truststore.password |
Password for the specified trust store. |
The article Authorization for REST service based routes with HTTP Basic Authentication describes how to enable authorization for a Route, and how to configure the user properties file. If LDAP is used for identity validation, the user information is stored in the roles for authorization. Figure 5 shows a container object groups and three child objects that represent the different groups or roles. Users belonging to a group are referenced through the member attribute, where the fully qualified distinguished name of the user is specified.
Figure 5: Sample LDAP for groups/roles
security.zip includes an extended version of the OSGi Blueprint bundle file authorization/LDAP-login-config.xml with additional configuration parameters to retrieve roles, and authorization/org.talend.esb.jaas.ldap.cfg with additional properties to configure the parameters. Table 3 provides a list of the additional properties that need to be configured.
Table 3: LDAP login parameters for authorization
Name |
Description |
role.base.dn |
The LDAP base DN used to looking for groups/roles, for example, ou=groups,dc=example,dc=com |
role.filter |
The LDAP filter used to look for user’s role, for example, (member=%fqdn) where %fqdn will be replaced by the user's full qualified distinguished name |
role.name.attribute |
The LDAP role attribute containing the group/role string used by Talend Runtime, for example, cn |
Currently, the sample Route provided in article Authorization for REST service based routes with HTTP Basic Authentication and also included in security.zip does not work for Talend version 7.1, 7.2, and 7.3.
In the default configuration of the Talend Runtime, both HTTP and HTTPS are enabled, and the private key used for HTTPS is a well-known standard key provided by Talend. If you use HTTPS, replacing the key is a must.
org.osgi.service.http.enabled=false
The file should now look like:
The Server HTTP Configuration section of the Talend ESB Container Administration Guide provides documentation for the HTTP settings in org.ops4j.pax.web.cfg.
When implementing a REST service in a Mediation route using the cREST component as route consumer, Studio provides three ways to authenticate the service: HTTP Basic, SAML token, and OpenID Connect. Only the SAML token provides an option to enable authorization. Unfortunately, the SAML token is not an adequate solution in many use cases because third-party service clients cannot be expected to acquire a SAML token and integrate it into the request. Often HTTP basic authentication, together with HTTPS, is the only way to integrate third-party clients.
Studio does not support authorization when selecting HTTP basic authentication as an authentication type.
In Routes, you can enhance the cRest component to implement role-based authorization with the help of an authorizing filter.
Sources for the project are available in the attached Authorization.zip file.
The cREST component is based on the Camel CXFRS component and the JAX-RS implementation of CXF. In JAX-RS, the runtime is extended and customized through providers. CXF JAX-RS provides a SimpleAuthorizingFilter, extending a REST endpoint with role-based authorization.
One way to add providers in CXFRS is to add the providers option to the endpoint URL of the CXFRS component. The providers are registered as beans in the Camel registry and referenced by name in the providers option. For more information on the exact syntax in the providers option and a complete list of all other options, see the Apache Camel, CXF-RS Component page.
Figure 1 shows a Mediation route in Studio that implements a web service with authentication and authorization.
Figure 1. REST service with authentication and authorization
In the cREST component, you can enforce authentication on the Basic settings tab by enabling the Use Authentication check box and selecting HTTP Basic as the authentication protocol.
Figure 2. Basic settings of the REST endpoint
Enforcing authorization in the cREST component is slightly more involved. It requires setting the additional "providers" option, which is implemented by the bean registered under the name of "authFilter" in the Advanced settings tab, as shown in Figure 3.
Figure 3. Advanced settings of the REST endpoint
In this example, the cBeanRegister component initializes the SimpleAuthorizingFilter, and registers it under the name "authFilter", as shown in Figure 4.
Figure 4. Definition and registration of the authorizing filter
The filter is mainly a wrapper around the SimpleAuthorizingInterceptor, which does the actual work. It is also the interceptor where the roles are specified that authorize the service to execute. In this article, the setGlobalRoles method specifies the roles manager and admin in the beans definition code, which allows them to execute the service. In a real-world use case, you would specify them through a context variable.
The Authorization.zip file, attached to this article, contains an executable sample project (v6.5.1). You can experiment with the project by deploying it in a Talend Runtime and trying different outcomes. For example, you could add a few users to the etc/users.properties file with corresponding roles.
Figure 5 shows a users.properties file where the user alice has the manager and employee role, and user bob only has the employee role. Call the deployed service using the URL (http://localhost:8040/services/test). If authenticating with user alice the call is successful. If authenticating with user bob you should get HTTP return code 403. The sample not only works with the JAAS PropertiesLoginModule but also with the other login modules supported by the Talend Runtime, such as LDAPLoginModule or SyncopeLoginModule.
Figure 5. Sample users file
Database previews are not shown successfully when loading Google BigQuery tables. An Unknown Error is shown.
The data load itself is successful.
Upgrade to a Qlik Sense version which includes updated Google BigQuery drivers that support the snapshot table type.
Upgrade to:
Avoid using the snapshot table type.
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-28365 for reference.
Product Defect ID: QB-28365
When connecting to a MySQL database via JDBC, there will occur below connection error message from TAC or Talend tMysqlConnection, tMysqlInput and tMysqlOutput components.
java.sql.SQLNonTransientConnectionException: Public Key Retrieval is not allowed
The error message java.sql.SQLNonTransientConnectionException: Public Key Retrieval is not allowed
typically occurs when you're trying to connect to a MySQL database using JDBC and the connection URL is not correctly configured to allow public key retrieval for SSL connections. This is a regular setting when using MySQL 8.0+ with certain security configurations.
Add client option to your connection URL mysql-connector allowPublicKeyRetrieval=true to allow the client to automatically request the public key from the server.
jdbc:mysql://localhost:3306/db?allowPublicKeyRetrieval=true&useSSL=false
Accessing the Qlik Sense Enterprise on Windows Hub or Management Console fails with the following error:
Your connection isn’t private
Attackers might be trying to steal your information.
NET:ERR_CERT_REVOKED
The currently installed 3rd party certificate has been revoked. To resolve the issue, we will locate the certificate currently used and delete it from the Windows certificate store. This will prompt Qlik Sense Enterprise on Windows to revert back to its self-signed certificate and allow access to the Hub and Management Console.
The currently installed 3rd party certificate has been revoked.
This article provides a guide on installing Qlik Replicate on a docker image.
sudo rpm -qa|grep dockersudo yum remove docker docker-client docker-client-latest docker-common docker-latest docker-laster-logrotate docker-logrotate docker-engine
sudo yum install -y yum-utils device-mapper-persistent-data lvm2 sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo sudo yum install --allowerasing docker-ce docker-ce-cli containerd.io sudo systemctl start docker sudo systemctl enable docker
/kit
" The /kit directory is a temporary folder used to store installation files. In the example below, the RPM file is areplicate-2024.5.0-357.x86_64.rpm
. Once the installation is complete, the entire /kit folder can be safely deleted.mkdir -p /kit/ar_docker
cd /kit
rpm2cpio areplicate-2024.5.0-357.x86_64.rpm | cpio -iv --make-directories --no-absolute-filenames -D ar_docker/ ./opt/attunity/replicate/addons/samples/docker/*
mv ./ar_docker/opt/attunity/replicate/addons/samples/docker/* ./ar_docker
rm -rf ./ar_docker/opt
cd /kit/ar_docker
cp ../areplicate-2024.5.0-357.x86_64.rpm .
./create-dockerfile.sh
/kit/ar_docker/Dockerfile
, from:
RUN yum -y install /tmp/areplicate-*.rpmto
RUN systemd=no yum -y install /tmp/areplicate-*.rpm
NOTE!
The parameter systemd=no is used to solve the below error you may hit during the docker build stage: This rpm is not supported on your system (no systemctl), exiting. error: %prein(areplicate-2024.5.0-357.x86_64) scriptlet failed, exit status 43
NOTE!
The password should not be empty and must be strong enough.
WARNING!
If you want to install ODBC Drivers, please make the corresponding ODBC Drivers rpm files are ready in this folder. If you want to skip the ODBC Drivers installation at present, rename or delete the file "drivers" in this folder.
docker build --no-cache -t johnw/replicate:2024.5 .where
/johnw/replicate:2024.5
is the image tag.Do not forget the last period "."
docker run -d --name ar --hostname cdc2 -e ReplicateRestPort=3552 -p 3552:3552 -v /dockermount/data/replicate/data:/replicate/data johnw/replicate:2024.5
Now Qlik Replicate is running in the docker and can be accessed from Qlik Replicate Console GUI.
A task may fail with the following error:
[STREAM_COMPONEN ]E: The "Retrieve all source columns on UPDATE" option is turned off in the log stream task settings, but the replication task configuration requires it to be turned on. [1020101] (ar_cdc_channel.c:315)
Qlik Replicate May 2024 Sp02 and later have introduced a fix for the following scenario in a log stream setup:
The fix requires the Retrieve all source columns on UPDATE option to be turned on in your parent log stream task or the task will encounter errors.
Turn on the Retrieve all source columns on UPDATE option in your parent log stream task.
C:\Windows\System32>sftp -P 22 username@ftptest.test.com
The authenticity of host 'ftptest.test.com (18x.6x.15x.21x)' can't be established.
RSA key fingerprint is SHA256:KijFUxxxxxxxxxxxxxx/xxxxxxxxxxxxxxxxxapWjo
If the extraction does not retrieve a valid working fingerprint, contact your SFTP server administrator who can provide a fingerprint or a public key for you.
If there are connectivity issues, to request data from your data connections through a firewall, you need to add the underlying (all three) IP addresses for your region to your firewall's allow list. These addresses are static and will not change. See Allowlisting domain names and IP addresses.
Error in SFTP connector
Diagnostic
Example: (insert a valid SFTP server host IP)
Result:
In case of this or other SFTP connection errors, please work with the SFTP server administrator or SFTP server vendor in order in order to enable the generation of a publicly available fingerprint.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
How to retrieve users and user attributes from excel in Qlik Sense?
The setting and process for Qlik Sense to retrieve user information from excel are almost same as the following 'ODBC example'.
It is very important to review the below information to set up the data source files and Qlik Sense configuration correctly. The real example provided will give a better understanding how exactly it works.
Each data source has a different configuration and the following example (Excel) of adding an ODBC user directory connector.
For .csv and SQL examples, please see the help site: https://help.qlik.com/en-US/sense/Subsystems/ManagementConsole/Content/ODBC-example.htm
Do the following:
Verify that the Microsoft Excel Driver is installed.
Set up an ODBC source on the server.
You need to store the data in two separate sheets in the same excel file, for example, for example you can place it in this location: %ProgramData%\Qlik\Sense\temp.
The temp folder is not included in the default installation. You need to create the temp folder, if not already done by another QMC administrator.
SheetA contains the users and SheetB the user attributes.
Example:
SheetA
userid | name |
1 |
John |
2 |
Bill |
3 |
Tom |
SheetB
userid | type | value |
1 | jd@email.com | |
1 | lastname | Doe |
2 | bg@email.com | |
2 | lastname | Gates |
3 | th@email.com | |
3 | lastname | Hanks |
Select User directory connectors on the QMC start page or from the Start drop-down menu to display the overview. Create a new user directory connector (ODBC) and edit the properties.
Identification
All fields are mandatory and must not be empty.
Property DescriptionName | The name of the UDC configuration, defined from the QMC. |
Type |
The UDC type. |
User sync settings
Property Description Default valueSync user data for existing users |
|
Selected |
Connection
Property Description Default valueUser directory name |
The name of the user directory. Must be unique, otherwise the connector will not be configured. The name must not contain spaces. |
- |
Users table name | The name of the table containing the users. Include the file extension in the table name, for example: [SheetA$]. | - |
Attributes table name | The name of the table containing the user attributes. Include the file extension in the table name, for example: [SheetB$]. | - |
Visible connection string |
The visible part of the connection string that is used to connect to the data source. |
- |
Encrypted connection string |
The encrypted part of the connection string that is used to connect to the data source. Typically, this string contains user name and password. The two connection strings are concatenated into a single connection string when making the connection to the database. |
- |
Synchronization timeout (seconds) | The timeout for reading data from the data source. | 240 |
Example:
User table name: [SheetA$]
Attributes table name: [SheetB$]
Visible connections string: Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)};Dbq=%ProgramData%\Qlik\Sense\temp
Click Apply to apply your changes.
Go to the User directory connectors overview and check if the user directory is displayed as Configured and Operational.
If the User directory name is not unique the connector will not be configured. If not operational, check the repository system log in: %ProgramData%\Qlik\Sense\Log\Repository\Trace.You have added an ODBC data source and initial synchronization will be performed within five minutes (by default).
R4Z Db2 mainframe install is completed but no Changes are coming through.
Check that the Tables you wish to be performing CDC replication upon, have been "turned on" for capturing the changes from the DB2 z/OS Logs.
Do this by using the following command. This can be performed by the DB2 Database Administrator.
Option 1: Make sure the Table has been altered for CDC:
ALTER TABLE schema.table DATA CAPTURE CHANGES
Option 2: If the UserId has the permissions it can be configured on the Db2z Endpoint in the Advanced tab.
Change Data Capture to: Automatically enable Data Capture Changes (requires admin privileges)
Varbinary Datatypes on Postgres Target databases are treated as LOB datatypes. Temporarily CSV Files generated by Replicate currently include LOB datatypes even when LOB support is turned off for the task. This leads to data being inputted into the wrong columns if there are LOB datatypes in your tables and LOB support is turned off.
Sample error of a numeric datatype column flowing into a Datetime column:
[TARGET_LOAD ]E: Command failed to load data with exit error code 3, Command output: psql:M:/Replicate/data/tasks/x3_testr4x_rez_ods_ls_pqsl_AgentTest_ac/data_files/1/LOAD00000001.csv.sql:1: ERROR: date/time field value out of range: "0"
The temporary CSV files of Replicate do not remove the LOB columns when LOB support is turned off. This leads to incorrect column matches.
QB-28455
A common request received is a method of grouping Qlik Sense apps into a folder. Eg: If there are many documents that address different categories (such as economics, politics, entertainment, charity etc) in the Hub, it may be good to be able to create folders within 'My work' in Hub to organize my documents and have them in the right folder.
See Folders in your own workspace and streams for details on the feature request and vote to provide us with more feedback!
The request is partially implemented using application tagging. See Fig 1.
Fig 1
A Qlik Replicate task using a SAP ODP Endpoint to replicate a table fails with the error:
[SOURCE_CAPTURE ]E: Text '%% TO BE DEFINED %%' could not be parsed at index 0 [1024719] (custom_endpoint_capture.c:800)
Modify the custom extractor and verify that the table or object is Delta enabled in SAP.
The Extractor or Object defined in the Qlik task is custom and not Delta enabled.
RECOB-8311
After a Qlik Sense upgrade, the Qlik Sense Repository service fails to start. The following error is logged in the Windows Application Event log:
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
System.IO.FileLoadException: Could not load file or assembly 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Qlik.Sense.Logging, Version=37.3.0.0, Culture=neutral, PublicKeyToken=1a848309662c81e5'
at Repository.QRSService.Start(Action`1 terminate)
at
The initial recommendation is to repair the installation. See How to repair an installation.
If the repair does not resolve the problem:
The Qlik.Sense.Logging.dll present in [Installation Qlik Sense folder]\Repository\ was missing required inforamtion.