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.
Qlik Support advises using the driver version for your endpoints that was certified for the version of Qlik Replicate you are using. The use of a driver running a different version than what was certified can lead to unpredictable results.
Before troubleshooting a potential defect, always ensure a supported driver is in use.
However, it is acceptable in most cases to use a later patch for the driver so long as it is the same major version. For example:
The current release of Qlik Replicate is May 2024. It requires ODBC driver version 18.3 for Microsoft SQL Server source and target. The other currently supported Qlik Replicate releases, November 2023, May 2023, and November 2022, all were certified with driver version 18.1.
However, the driver version 18.3 can be used.
Generally speaking, if the version of the driver is the same and has only been patched (as is the case between driver 18.1 and 18.3) we do not anticipate any issues using it with November 2023, May 2023 and November 2022 versions. If an issue is encountered on these versions with ODBC driver version 18.3, please open a support case.
This is generally true with using a patched version of the certified driver for other databases/endpoints as well, but there might be exceptions. Some endpoints mandate only specific versions for the driver. If there is a doubt, please open a support case.
After a DB2 LUW Upgrade, Qlik Replicate tasks fail with:
"ReadNextBufferWait: Error reading buffer Error at 'Reading log records': Unexpected Error. Original SQLCODE -1263: ' message SQL1263N The archive log file "S0673464.LOG" is not a valid log file for database "REP" on database partition "0" and log stream "0".
Reload the task using the DB2 LUW Endpoint.
Qlik Replicate saves the last save stream position when a task is stopped.
Since the DB2 LUW environment was upgraded, the transaction log will be different and the task (tables) need to be reloaded.
An SQL Lite file called DB2LUW_TIMESTAMP_MAP is defined in the tasks directory, which stores the LSN/LRI position with the timestamp for the given task. This file includes the old DB2 LUW transaction log which is pointing to the old DB2 transaction log version.
Opening a local QlikView document (.qvw) using the QlikView Desktop running on ClientOS in WebView mode fails. The Desktop client does not respond as expected and displays:
Lost connection to server.
Reconnecting
The error occurs if:
Upgrade to QlikView 12.90 (May 2024) IR or higher.
As a temporary workaround, turn off WebView mode:
Product Defect ID: QV-25106
Some of the master dimension in the Qlik Sense app cannot be seen in the selection tool.
Calculated dimension are not be displayed by design, and this is a current product limitation, but you can expect that a Master Dimension with a single field as expression would be displayed.
Environment
Cause:
The problem occurs when a Master Dimension is created using the left bar of Qlik Sense app. In this case, Sense will automatically add the '=' sign to the field you import.
So the master dimension is considered as a calculated dimension and not shown by the selection tool
Resolution:
It is necessary to avoid the "=" in the master dimension.
Here are the steps to follow.
While working with the Oracle source endpoint the Unique Index is not displayed in the Qlik Replicate GUI console.
The source table creation SQL statement is as below:
CREATE TABLE FBI2 (ID INTEGER, NAME1 CHAR(20), NAME2 CHAR(20), NAME3 VARCHAR2(20));
CREATE UNIQUE INDEX FBI_IDX2 ON FBI2(NAME1, NAME2, NAME3 DESC);
In the provided sample, the unique index is created as a function-based index. The DESC (default is ASC) property applied to NAME3 makes the index a function-based index (FBI). When querying the table index information, it's clear that the “SYS_NC00005$” field replaces the actual underlying field “NAME3”.
This is a limitation in the Oracle source endpoint, see Function-based indexes are not supported.
Hence the Unique Index cannot show up in the Task Setting GUI.
Case #00168364
This article highlights the difference between redo log thread vs the OCI thread used by ASM for Oracle source endpoints.
[SOURCE_CAPTURE ]I: Start processing archived Redo log sequence 174669 thread 1 name +RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174669.8435.1172797103 (oradcdc_redo.c:1011)
[SOURCE_CAPTURE ]I: Start processing archived Redo log sequence 154324 thread 2 name +RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_2_seq_154324.11355.1172797615 (oradcdc_redo.c:1011)
The two threads which you are seeing above are the two redo threads defined for a 2 node Oracle RAC database.
A redo thread is a set of redo log files that an Oracle instance uses to log changes made to the database. Each instance in an RAC environment has its own redo thread.
That is why you will see 2 different sequences for both the threads:
log sequence 174669 thread 1
log sequence 154324 thread 2
[SOURCE_CAPTURE ]T: ASM file '+RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174694.1245.1172802097' opened. Params: block size '512', block count '7389811', redo thread id '1' OCI Thread Id: '0' (oradcdc_io.c:864)
[SOURCE_CAPTURE ]T: ASM file '+RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174694.1245.1172802097' opened. Params: block size '512', block count '7389811', redo thread id '1' OCI Thread Id: '1' (oradcdc_io.c:864)
[SOURCE_CAPTURE ]T: ASM file '+RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174694.1245.1172802097' opened. Params: block size '512', block count '7389811', redo thread id '1' OCI Thread Id: '2' (oradcdc_io.c:864)
[SOURCE_CAPTURE ]T: ASM file '+RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174694.1245.1172802097' opened. Params: block size '512', block count '7389811', redo thread id '1' OCI Thread Id: '3' (oradcdc_io.c:864)
[SOURCE_CAPTURE ]T: ASM file '+RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174694.1245.1172802097' opened. Params: block size '512', block count '7389811', redo thread id '1' OCI Thread Id: '4' (oradcdc_io.c:864)
[SOURCE_CAPTURE ]T: ASM file '+RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174694.1245.1172802097' opened. Params: block size '512', block count '7389811', redo thread id '1' OCI Thread Id: '5' (oradcdc_io.c:864)
[SOURCE_CAPTURE ]T: ASM file '+RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174694.1245.1172802097' opened. Params: block size '512', block count '7389811', redo thread id '1' OCI Thread Id: '6' (oradcdc_io.c:864)
[SOURCE_CAPTURE ]T: ASM file '+RECO/P50K266N/ARCHIVELOG/2024_06_28/thread_1_seq_174694.1245.1172802097' opened. Params: block size '512', block count '7389811', redo thread id '1' OCI Thread Id: '7' (oradcdc_io.c:864)
The above 8 OCI Thread Ids in the logs are the 8 ASM parallel read threads which the Qlik Replicate task has opened to read a single archived redo log file.
Qlik Enterprise Manager (QEM) fails to monitor Qlik Replicate.
The following issues can be observed:
Possible error messages:
This is a known issue and Qlik is actively working on a patch. Please review the release notes for QB-26321 and QB-27571 for updates.
QB-26321 and QB-27571
QB-26321 and QB-27571
With Store Changes (see Change Processing) turned on for CDC tasks, Qlik Replicate tasks may crash or stop unexpectedly.
The following errors may be logged in the task log:
2024-07-30T09:53:22:497564 [AT_GLOBAL ]E: An exception occurred!!! (win32_exception_handler.c:109)
2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: Backtrace at exception: !{C:\Program Files\Attunity\Replicate\bin\at_base.dll!4537ab...
2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: exception code is 3221225477 (win32_exception_handler.c:112)
2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: tid=22112 (win32_exception_handler.c:115)
2024-07-30T09:53:22:499561 [AT_GLOBAL ]E: exception as string is EXCEPTION_ACCESS_VIOLATION (win32_exception_handler.c:118)
Upgrade to 2024.5 SP02 (for Windows and Linux) when available.
To work around the issue:
Product Defect ID: QB-28312
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-28312 for reference.
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
Reloads fail with error:
A reload fails with:
Requested endpoint could not be provisioned due to failure to acquire a load slot: Your version of Direct Access gateway is no longer supported. Go to 'Data gateways' in the Management Console to download the latest version (DirectAccess-0001)
Upgrade Qlik Data Gateway - Direct Access to a supported version.
If you are already on a supported version of Qlik Data Gateway, rerun the reload. Likely, the services were still initializing when the issue occurred.
This message can occur when the Qlik Data Gateway version is not supported
Or it could also be caused if the services are starting when the request is sent, causing the version being misreported. This is usually an isolated issue with very few reload failures.
An escalation is a request from a customer concerning a specific case that is currently under
investigation by Qlik Support. The customer has a case that has business-critical impact without a workaround provided and requires a faster resolution than what is provided in the standard resolution process.
The Escalation Management process aims to bring order, structure, focused management attention and additional resources to those customer situations which could otherwise result in a high level of customer dissatisfaction. Any Qlik® customer or partner with a valid maintenance contract may initiate an escalation on an existing support case. Escalations are intended for existing cases. Please do not report new issues through Escalation Management. New issues should be raised through the Qlik Support portal.
Escalations can occur for several reasons. Having a defined process allows Qlik to identify, track, monitor and manage situations that require increased awareness and quick action.
Please note that for an issue to be escalated, a support case must first be created (we will not accept escalations solely based on communications via email). If a case has been worked through our standard support processes and with our teams and you are not satisfied with the level or timeliness of service you received, you can escalate accordingly. See Escalation Triggers for more information.
Americas |
Qlik Data Analytics ProductsGiuseppe Novello Akshesh Patel Qlik Data IntegrationJayashree Guin Robert Kittles Christian Tan Lori Wittal Evan Teitelbaum TalendChristian Tan |
EMEA |
Qlik Data Analytics ProductsAlbert Candelario Benoit Canal Patrick Vanotti Qlik Data IntegrationAnne Arnoult Fabio Cunha TalendAnne Arnoult |
APAC |
Qlik Data Analytics ProductsKiran Shankar Ayaka Hanazono Yasser Ahmed Kahn Sankar Reddy K Qlik Data IntegrationJohn Wang Ravi Chintam Robin Patel Shaona Zhang TalendRobin Patel
|
Global Customer Support |
Qlik Customer Support / Talend Customer CareSuresh Kumar |
Americas | Hien Le hien.le@qlik.com |
EMEA | Réginald de Visscher reginald.devisscher@qlik.com |
APAC |
Vineet Chopra |
Global | Daniel Coullet daniel.coullet@qlik.com |
In this webinar we will discuss:
- Qlik Sense Enterprise on Windows, deployment scenario
- Configuration best practices
- Important settings
Note: For information on deployment of newer product releases, see Deploying Qlik Sense Enterprise on Windows.
Q: It states not recommended to have share on same as node. VM site, SAN mapping a C and D drive to SAN, with C installation and the D drive shared. Is this still not recommended?
A: You should have a separate server for the fileshare for a multi node deployment. That is also to load balance the network traffic and TCP connections to your nodes. You can have on a single node your shared folder on D with your setup. SAN is supported.
Q: Is there a recommended "best practice" approach for a separate dev/test/prod server instance?
A: In this case 3 server cluster
Q: I am trying to install Qlik Sense February 2019 on windows server 2012 r2. So, I faced an error that server dispatcher installation failed. How to solve this error?
A: Open the logs in the %temp% folder, check for the ServiceDispatcher logs. It could be fileshare/database/powershell/user related. If you don’t see anything with value 3 you need to contact Qlik support and attach your log installation files.
Q: Is it possible to install Qlik sense and NPrinting in the same machine?
A: No that is not a supported scenario. In worst case you overwrite the Sense CA certificates while entering.
Q: If we are upgrading then we need to import the extensions from the QMC or we can just simply copy and paste the extensions in Extensions folder?
A: When you upgrade the extensions will stay linked in the DB, you do not need to reimport them, but you might have to adjust them to make them work with the new installation.
Q: Hi, can we get dashboard bundles with silent installation?
A: No right now there is no option for that. We have brought this to the attention via feature request to R&D and hope for an improvement.
Q: When we will be able to connect MySql DB to Qlik Cloud business directly?
A: I will reach out to product management, the current cloud options are limited, but there are some new things coming.
Q: Good day Sebastian, I'd like to know the needed network requirements to enable users from Domain B to use an already up-and-running Qlik Sense Server installation on Domain A. That includes being able to access an Oracle database running on Domain B, all from Domain A.
A: Sense users can be synced from more than one domain, as long as you have domain trust between the system.
Q: I will do a Qlik Sense v.3.2 SR 2 to February 2019 upgrade tomorrow. Any known issues I should know about?
A: If you upgrade from 3.2 SR2 to February 2019 directly there are many things which can go wrong, please contact support before you start. You need to do a few steps in-between.
Q: What kind of issue could occur if not using the .NET framework version 4.7.2?
A: e.g. QlikSenseUtil will not start. So, you can't change connection stings for the Repository Service.
Q: Some time ago there were a problem with the special characters in passwords for repository (both main and logging). is it solved?
A: Yes, more robust, but I would still not use an @ in the password
Q: A lot of my clients have IIS services on their server they want to use. This uses 443 standard and cannot be changed. Is there a way to avoid the standard 443 or 80 ports?
A: Yes, there is, just not under the installation. 80 is disabled by default and can be changed in the system once spun up. You can have 443 changed to another port, just disable IIS on that port during the install.
Q: We just upgraded to Nov 18 Patch 3 release and we created a new QLogs database (standalone) right before. Where can I turn on centralized logging? During upgrade process there was no option to enter the QLogs details.
A: On the help you will find the additional steps to enable Qlogs, after adding the DB. https://help.qlik.com/en-US/sense/February2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Deployment/Qlik-Logging-Service.htm
And also https://qliksupport.force.com/articles/000043238
Q: Does configuring centralized logging prevent single-node logs written to the file system?
A: No, it will log to both by default.
Q: How do we install Qlik Sense February 2019 with a remotely managed database and we can't change user rights?
A: Please contact support for help. There are some issues with Azure standalone Postgres DB instances in the February 2019 release, Support can offer a workaround.
Q: Hi, I've been trying to install Sense Desktop (only) on my laptop. It's saying the install was successful, but I can't see it I the installed programs in control panel. Do you have any suggestions please?
A: Qlik Sense Desktop is a per user installation only rather then per machine. Try to see if the files are on disk: (replace username with your userId form windows)
C:\Users\username\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Qlik Sense\ Qlik Sense Desktop.lnk
C:\Users\username\AppData\Local\Programs\Qlik\Sense\QlikSense.exe
If you do not see them, please contact support.
Q: We tried to install it with a remotely managed database and the installation failed.
A: Please send us the installation logs so we can have a look.
Q: How to disable usage of port 4244 in dialog box “Edit proxy” for Authentication listen port? Just make it empty? What is impact on Monitoring apps or others? (Current Qlik Sense version is November 2018)
A: You can’t do that, you still need Windows authentication to work for Sense to validate the users on the system. Your Monitoring apps would stop reloading if you block it.
Q: I configured the file share in the same node of the central node. It is ok?
A: Yes, that is fine as long as you have a small deployment. Beyond 2 nodes you should move to a separate fileserver.
Q: Is what you talked about a brand-new installation? we have Nov 2018 installed so we just need to do an upgrade?
A: This was a new installation, and update has nearly the same but a few steps less. You would just have to do an upgrade from November 2018 to February 2019. Sometimes the Patches can’t be deinstalled automatically, then make sure to deinstall e.g. Nov 2018 Patch 1 first before upgrading.
Q: If we update Qlik Sense from Previous version and we have several Nodes - should we update Central first and Rim then? What will be the process of upgrade?
A: First you stop all the nodes, in the order all Rim, then Central node last. After that you would first upgrade the Central node, and then all the Rim nodes.
Q: How many engine nodes a central node can take?
A: You will only have one Engine service per node, but you can as much rim nodes as you want into the deployment. That is only limited by your license or the database performance.
Q: What license model is required for Multicloud?
A: Signed license model, which was introduced in the February 2019 release.
Q: Why do I need a shared folder for Sense?
A: The binary files for your apps and extensions for all the nodes are stored on this file share.
Watch the video here for more information https://qliksupport.force.com/articles/000028399
Q: Are there Docker install files for Qlik Sense Enterprise?
A: Not for Qlik Sense Enterprise, but for the Multicloud instances. Please reach out to your Account manager to get more information.
Q: How will antivirus program block our installation?
A: The installer has e.g. PowerShell scripts inside and they are running from %appdata%\local\temp which might be blocked and as a result the installation fails.
If you have installed Sense successfully then you need to add the following exceptions, please review: https://qliksupport.force.com/articles/000031189 and
https://qliksupport.force.com/articles/000028726 for more details
Q: After an upgrade, my monitoring apps are no longer working. Is there a reason this has happened?
A: There can be many reasons, please contact support. Review: https://qliksupport.force.com/articles/000036815
And
https://qliksupport.force.com/articles/000060688
Q: Could you please explain the shortly the port of the local dB of 4432 vs 5432
A: 4432 is the standard port for the database in Qlik Sense when using the inbuild database. If you have a standalone Postgres installation the standard port is 5432. Both ports will work with a Sense installation.
Q: General recommendation when is time to upscale QS?
A: When your users start complaining about performance, or you see that the engine need time to calculate heavy requests. Those are just two, but there is no general recommendation, like to it from 100 users onwards. That depends on your needs and your user’s behavior. Give us a call and we can set you up with the right person to discuss this further.
Q: Could you migrate directly from the November 2017 version to Feb 2019 one?
A: Yes, you can.
Q: Why, when the installer asks me to look at the log, why is there no link to the log?
A: The blue text usually brings you to the logs. If you do not see that one, please open %temp% and you should see them there.
Q: Upgrading Question. Integral reference problem when the repository service starts. Where to start checking? Thanks!
A: A good start point is Windows Event logs and C:\programdata\qlik\sense\log\repository\trace\Servername_system_repository.log
They should give you a hint, then just check our knowledgebase or contact us at the support, we are happy to help you out further.
Q: Can we update from the November release to the newest February release without a lot of problems?
A: Yes, November 2018 to February 2019 is not connected with a lot of problems.
Q: We are thinking about cloud deployment. To make it fully elastic, probably it is best to give each of our customer own dedicated environment. for example, we have 20 customers. is it possible to have 20 independent environments, but only 1 QMC?
A: That is the idea, but there could be an issue with the licensing in your model. Please contact the Account Manager for more details.
Q: Do I need to uninstall the antivirus during installation?
A: No just pause it, no need to uninstall.
Q: On which AD group should we put the users?
A: Prior to the installation in the Local Computer\Administrators group. The installer will add it in
“Qlik Sense Service Users” and “Performance Monitor Users”.
How to specify superuser password in a silent installation. (doesn't appear in spc.cfg xml file..)
Qlik_Sense_setup.exe [-silent] … {dbpassword="password}…
Just with the Setup.exe as a parameter.
dbpassword | [password] | Password for the database superuser that creates the user that runs the database. |
Q: Do we need a fresh installation of Qlik Sense Enterprise if we are migrating from one Qlik Sense server to another. My client is currently using services from External IT provider. Now Client wants to have QS enterprise back on premises. What to keep in mind doing this task.
A: Yes, you would do a fresh installation, and then import the DB of your old installation. For this you need to install the same version on the target system as you have on the source system.
Q: Can the file share be running on a Linux server? What kind of configuration would imply from the Windows server and Qlik Sense side?
A: Yes, we support it as long as your server can handle SMB 3.0, but not all distributions might work the same. As also not all NAS vendors are working. I was mistaken about this point in my presentation. The support was added for Sense, just not for QlikView.
See more information here: https://help.qlik.com/en-US/sense/February2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_Deployment/Persistence.htm
Note: Qlik cannot verify support for all storage vendors, and recommends that customers test their preferred infrastructure. In the event of an issue arising that is attributed to storage, Qlik Support may request that customers replicate the issue on a Windows hosted file share.
For implementation advice which fits your needs please reach out to your Account owner or Qlik consulting services.
Q: Fileshare can be in the same central node?
A: Yes, that is possible, but if you get beyond a two-node deployment it will makes sense to separate the fileshare, not to have much traffic on the central node.
Q: Can you repeat how access and read logs stored in log-database?
A: You have 3 tables in the Qlogs database
public.log_entries
public.archive_entries
public.settings
the table "log_entries" contain following columns for the logs:
"id","entry_timestamp","entry_level","thread","logger","process_host","process_name","process_id","payload"
example line:
"1","2019-03-18 14:52:25.973511+01","INFO","11","Service.Proxy.Qlik.Sense.Common.Monitoring.HardwareInfo","QlikServer1","proxy",1760,"{""Description"":""Command=Start proxy;Result=0;ResultText=Success"",""ProxySessionId"":""0"",""ProxyPackageId"":""0"",""RequestSequenceId"":""0"",""UserDirectory"":""INTERNAL"",""UserId"":""System"",""ObjectId"":""0"",""ObjectName"":""Not available"",""Service"":""Proxy"",""Origin"":""Not available"",""Context"":""Not available"",""Command"":""Start proxy"",""Result"":""0"",""Message"":""Disk C:\\: Volume label: , Free space: 32221552640 bytes(30.01 GB(s)), Total disk space: 53160701952 bytes (49.51 GB(s)), File system: NTFS""}"
archive is used when cleaning the log database, the deleted entries will be stored defined amount of time and then getting cleaned out as well.
Q: Is advisable allocate Qlik Sense Server in DMZ? Why Y/N.
A: All nodes in a site, including nodes without an engine, require access to both the database and file share. In demilitarized zone (DMZ) deployments this may require opening additional ports, or you would have to add the DB and fileshare in the DMZ as well.
After a Qlik NPrinting upgrade, some cells are blocked out with black color.
Example:
This is a known Vizlib extension defect. Verify that a Vizlip extension is in use and contact Vizlib support for further support.
Uncheck Keep Source Formatting in the template editor.
QB-22744
The Fast Change button may stop working after a QlikView upgrade. The button appears not to respond after being clicked.
By default, 'straight table' cannot be used as a fast change option if the table is a linked object. To confirm if a 'straight table' is in use:
Set RestrictLinkedTypeChanges at the below path:
Set the value as either RestrictLinkedTypeChanges=-1 or RestrictLinkedTypeChanges=<greater than the number of linked objects> (Stop the QVS service before making this changes) The other options is to unlink the objects (right click on the chart, and click 'linked objects>unlink this object)
The settings.ini may have been adjusted to allow this. These changes were reset to default after an upgrade. The settings.ini must be backed up and reviewed after an upgrade to ensure all custom settings remain intact.
Jira QV-25359
This article describes how to import Qlik Sense apps by using an automation. There are 2 possible approaches:
The difference between this approach and the Copy App block in the Qlik Cloud Services connector is that you can specify whether or not to include the data that's in the app. This can be done by setting the "No Data" parameter.
Example automation:
Blocks:
Export app
This approach allows you to import an app from a file. First, use the Export App To Base 64 Encoded File block in combination with the Cloud Storage connector to create the file on any of the supported destinations. In the below example, Dropbox is used.
Import app
To import the file again, use the Open File & Read Data From File blocks from the Cloud Storage connector and use the output from the read block as input for the Import App From Base 64 Encoded File block from the Qlik Cloud Services connector.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Due to an issue with MySQL ODBC Driver 8.0.027 to 8.0.033, empty TEXT columns may not be replicated correctly during Full Load.
Qlik Replicate
MySQL ODBC Driver 8.0.027 to 8.0.033
Empty TEXT columns may not be replicated correctly during Full Load. For example, if one table row contains a TEXT column with a value and the same column in the next row contains an empty value (but not NULL), both rows will display the value of the first row on the target. See Limitations and considerations | Qlik Replicate Help.
When the source table has a text column that is blank (not null) the data from the previous row that had data is duplicated.
As an example if have the following 3 rows:
1 'SOME DATA'
2 null
3 '' <---empty string not null
The the output rows will have the following:
1 'SOME DATA'
2 null
3 'SOME DATA'
To resolve the issue, downgrade to MySQL ODBC 8.0.026.
The ODBC parameter no_ssps can also be used to resolve the issue.
Set it to no_ssps=1;
Until MySQL resolved the issue, the parameter should be set on Full Load ODBC connections. See 5.2 Connector/ODBC Connection Parameters | dev.mysql.com.