In the QlikView Server Session log, the Client Address is coming through as the webserver's IP for AJAX sessions.
The webserver is the server requesting the ticket, but is not the client.
The IP address written in the sessions log's "Client Address"
...In the QlikView Server Session log, the Client Address is coming through as the webserver's IP for AJAX sessions.
The webserver is the server requesting the ticket, but is not the client.
The IP address written in the sessions log's "Client Address" tab is the IP address of the "client" machine connecting to the server on port 4747.
In the case of AJAX, the "Client Address" will be the IP address of the webserver machine.
If IE Plugin or Desktop is used then the IP address will be of the client machine hosting the desktop or IE (end-point).
For information on how to accurately locate the client IP address, see How to find the IP address of a QlikView client accessing documents .
Environment:
- Labels:
-
Configuration
Known issues experienced when performing an upgrade of QlikView 11.20 to any of the later versions.
Applies for an upgrade to:
QlikView 12.20 / November 2017 What's New in QlikView November 2017
QlikView 12.30 / November 2018 What's New in QlikView November 2018
Known issues experienced when performing an upgrade of QlikView 11.20 to any of the later versions.
Applies for an upgrade to:
QlikView 12.20 / November 2017 What's New in QlikView November 2017
QlikView 12.30 / November 2018 What's New in QlikView November 2018
QlikView 12.40 / April 2019 What's New in QlikView April 2019
QlikView 12.50 / April 2020 What's New in QlikView April 2020
QlikView 12.60 / May 2021 What's New in QlikView May 2021
The linked information is not exclusive to problems, but also includes changes in behavior.
Preparation for an Upgrade
Review the Upgrade Instructions as documented on our official Online Help.
Watch our Upgrading from QlikView 11.20 recording, which covers the end of support for QlikView 11.20 including:
- What to consider before upgrading
- What to expect after upgrading to QlikView 12.10 or QlikView November 2017 or beyond
- Major architectural differences introduced in 12.10 and November 2017 or beyond
- How they will change the behavior of your QlikView deployment for the better
- New features available after upgrading
Intended Changes
User / Administrator impact behavior change
Tasks are not executed as expected and are shown in status Queued |
Tasks that may have originally failed due to resource constraints, or destabilized the QlikView environment, will now be queued. A queueing system was introduced in QlikView 12.10, which works together with an overload protection to help stabilize the QlikView environment. This change is part of the improved Publisher load balancing introduced in version 12.10. |
Unable To Export Large Objects To Excel After Upgrading to November 2017 |
To prevent large exports from causing system instability, time and memory limits have been implemented, and this can result in exports failing or delivering only partial data. These limits can be changed to accommodate larger exports. |
Reloads that were functioning fine in QlikView 11.20 or QlikView 12.x, begin to fail after an upgrade to QlikView November 2017. | Reload tasks that completed successfully in QlikView 11.2 or 12.x may fail after an upgrade to the November 2017 release.
A new script reload mode was introduced in the November 2017 release, and this can result in some scripts failing. Reloads now use the BNF mode. This change adds consistency to the product, as reloads now use the same syntax checks as the script editor. For details about the change and guidance on avoiding errors resulting from this change, see QlikView November 2017: Failing reloads and BNF script reload mode.
|
Send to Excel feature now uses the .xlsx format by default beginning in the November 2017 release. | In earlier versions, the default format was .xls. QlikView now uses the same default file format as Microsoft. The change to .xlsx improves exporting performance and stability. |
QlikView 12 Task - Log files are copied at the successful end of a reload and do not appear in the standard location when a reload is in process. | Beginning in QlikView 12 SR1, document reload logs are written locally on the node handling the task and stored in %ProgramData%\QlikTech\ QlikViewBatch. When the reload completes, the log is then copied to the Source Document folder and the QDS Application Data folder. This change is a log optimization for QlikView Publisher. It was implemented to avoid the increase in reload times that can occur when logs are written to remote folders during the reload. For details, see the QlikView 12 SR1 release notes. |
Before() function does not calculate properly if “Suppress Zero-Values” is checked in the Chart Properties > Presentation tab. | Beginning in QlikView 12, the suppress zero setting is now fully applied in conjunction with inter-record functions, but this was not the case in earlier versions. See Internal behavior change of before() function in Qlikview 12 and later. |
Change in how alternate states evaulate and expand variables | Beginning in QlikView 12, variables always belong to a specific alternate state, eliminating the random behavior that could occur with alternate states in earlier versions of QlikView. After an upgrade, QlikView documents using more than one alternate state should be tested to verify that alternate state still renders the desired outcome. |
The sort order in a table is not correct after the upgrade to QlikView 12.10 |
Sort order for charts containing disabled/hidden columns is set to default after the upgrade. This is a result of changes made to resolve inconsistent sorting behavior in charts containing disabled/hidden columns. |
Functions that refer to paths fail, while they used to work in 11.20 |
Functions are failing because of changes in how relative paths are handled. In QlikView versions 12 and later, functions have been improved to reference paths relative to the Directory statement, rather than to the location of the .qvw, as in earlier versions. |
Quotes in Set Analysis change in behavior - "error in expression" or "incomplete visualization" or "invalid dimension" | These errors are often the result of an incorrect use of single and double quotation marks. The errors did not occur in earlier versions because a defect prevented QlikView from recognizing the differences between single and double quotes. The product defect has been fixed, and single and double quotes must now be used correctly. For details, see the following resources: |
After upgrading, opening or navigating in a document results in “Lost Connection to Server, Reconnecting” messages. |
Time-out settings are now applied using SocketTimeOutInSeconds in the WebServer settings. These settings override the QVSTimeout setting that was used in previous versions of QlikView. This change was made to add consistency in timeout settings between services. See QVStimeout Overridden by new WebServer Setting for details. |
Reloading a script in QlikView 12 fails with "ApplyMap error: map_id not found" |
In versions 12.10 SR6 and later, a mapping table must be loaded before the ApplyMap() function can run. Unless a mapping table has been loaded, scripts that reloaded successfully in earlier versions will now fail to reload with the following error: “ApplyMap error: map_id not found.” |
Pie charts behave differently in versions 12.10 and higher. | When dimension limits are applied and total grouping mode was added to the expression, the order of the dimensions was reversed in 11.2 and 12.0. The order is no longer reversed in versions 12.10 and later. The behavior in versions 11.2 and 12.0 was the result of a product defect that was fixed in 12.10. |
Calendar objects no longer close or minimize after a selection is made |
In version 11.2, the calendar object closes when a selection is made. To close the object in versions 12.x and higher, you must now click outside the calendar area. This is a design change relating to the touch enhancements implemented in QlikView 12. |
Issues encountered
User / Administrator impact
QlikView 12: dashboard stuck on Loading in Internet Explorer - Qva is undefined |
QlikView 12 removes support for IE 8, 9, and 10. Compatiblity modes and old browser versions lead to the Full Browser (ajax) Client to no longer work. |
Issue with "XPassword" and OLE DB SQL Server Native Client 11.0 Driver in QlikView November 2017 (12.20) | Issues connecting to the OLE DB SQL Server Native Client Driver due to Integrated Security. |
- Labels:
-
Administration
-
Deployment
When purchased, our Qlik products are delivered with a 16-digit license key (LEF) and/or the Signed License key (SLK). What key is applied may differ depending on your requirements or the version of the product.
You’ll have two activation options:
- T
When purchased, our Qlik products are delivered with a 16-digit license key (LEF) and/or the Signed License key (SLK). What key is applied may differ depending on your requirements or the version of the product.
You’ll have two activation options:
- The Signed License key (SLK), available for most Qlik products
- (legacy) And a combination of the 16-digit key, a control number, and the License Enabler File (LEF)
These license activation methods cannot be mixed. A license activated with an SLK cannot also be activated using the key + control number method.
In this blog post, we will cover the differences between the two activation methods, as well as what benefits the Signed License key brings to the table. Details on how to activate them will follow in the second post to this short series.
What is a Signed License Key (SLK)?
- The SLK is an encrypted JSON web token used to activate Qlik Sense Enterprise or ABDI. It contains product information, available access types for users, and any applicable product add-ons or limitations.
- The SLK is to be used for activating Qlik Sense Enterprise on Windows licenses using the Professional/Analyzer user model. Qlik Sense Core Based and Token based licenses should use the legacy LEF activation method.
- You cannot change from an SLK activated system to a LEF activated system.
- The SLK requires online connectivity to our licensing server for both activation and continued operation.
- For information on how to apply an SLK, see How to Apply a Signed License Key
- The time (Subscription date, Analyzer capacity reset) is on UTC
The SLK is mandatory for:
- The use of Qlik Sense Analyzer Capacity licenses
- Any deployments using Qlik Sense Enterprise on Kubernetes or Qlik Sense Enterprise on Cloud Services, as well as Multi-Cloud (a combination of Qlik Sense Enterprise on Windows and Cloud offerings)
- Unified Licenses, which combine Qlik Sense and QlikView
- See Qlik product licenses for more information.
What is a License Enabler File (LEF)?
- Every license has a LEF. Each 16-digit license number that you get can be translated into a LEF, regardless of the method used to activate the license. The LEF itself contains all the instructions for the Qlik Product, such as license level, numbers of users, access types available for assignment, as well as all the limitations or add-on.
- When applying your license using the license number and control number, the LEF will be downloaded to the product during activation. It will be updated with each refresh request.
- The first line of the LEF is always your 16-digit license number and it ends with a checksum so that an unauthorized alteration of the content is impossible.
- It requires a control number for activation
- You can change from a LEF activated system to an SLK activated system (but not the other way around). Always use LEF activation if your license has tokens.
- The LEF can be activated offline and used offline, see How to license a QlikView or Qlik Sense server without Internet access for details.
- The time (Subscription date) is on UTC
The LEF activation method is currently required for:
- Qlik Sense
- Core-based licenses
- Token-based licenses
- See Qlik product licenses for more information.
- QlikView
- CAL-based licenses
- See Licensing QlikView for more information.
How do I get an SLK?
- Your signed license key will be sent to you in the license delivery email.
- If you did not receive your SLK via email, please contact Customer Support. Please make sure to provide the corresponding 16-digit license key and the Support team will be able to get the SLK for you.
- There is no way to get the SLK from the Support Portal at this time.
Benefits of using an SLK
Using the Signed License Key makes more product and deployment options available to you.
Examples of these are:
- Multi-site deployments, such as connecting a Qlik Sense Enterprise site with a QlikView Server deployment using Qlik Sense Enterprise license options. This is enabled by accepting a Dual-Use offer for each QlikView deployment that should be enabled for a Unified License scenario.
- Multi-geo deployments, such as having Qlik Sense Enterprise sites in different locations using the same list of users.
- Qlik Sense Enterprise for Kubernetes and Qlik Cloud Services. Either stand-alone or in a multi-cloud setup.
- Consumption-based licenses, such as Qlik Sense Enterprise Analyzer Capacity. This additional user license is possible to use in a single or multi-cloud scenario.
All the above is enabled by the use of the Signed License Key. This is made possible by the local deployment syncing all entitlement data (assigned users access, etc.) with all available deployments sharing the same SLK. The synchronization is done using the Qlik Licensing Services and our license backend hosted in Qlik Cloud.
If you are curious about more information around the Qlik Licensing Service, see the Qlik Licensing Service Reference Guide.
How do I get a LEF?
- You can get the LEF and control number from the Support Portal by following the steps outlined in How to request a control number and LEF
And this is it for an overview of our available license types and activation methods. We’ll follow this up with part two soon, detailing the move from a LEF activated license to an SLK. Until then, give this post a like if you found it helpful! And please let us know if you have any questions or feedback in the comments.
- Labels:
-
Configuration
-
Licensing
It may be necessary to export Data Connections to either move Data Connections between environments or to import Data Connections into the Qlik Analytics Platform (which doesn't have a front-end interface to easily recreate these connections).
To ac
...It may be necessary to export Data Connections to either move Data Connections between environments or to import Data Connections into the Qlik Analytics Platform (which doesn't have a front-end interface to easily recreate these connections).
To achieve this, keep in mind:
- Data Connections can only be created inside the Data Load Editor.
- Data Connections cannot be created directly in the Management Console.
- Exporting a QVF from Qlik Sense Enterprise strips the Data connections from the application for security purposes.
- Apps created using Qlik Sense Desktop store the Data connections locally within the file
- Apps containing Data Connections that are imported to the QMC will retain the Data Connections and add them to the environment.
Resolution:
With these considerations in mind, Qlik Sense Desktop can be utilized to maintain a 'blank' QVF (No loaded data) that contains all the data connections needed for moving to a higher environment or bringing connections into QAP.
Follow this process:
- Open Qlik Sense Desktop
- Create/Open a QVF dedication for the Data Connections you wish to transfer and maintain
- Create the Data Connections in the QVF
- Test to verify that the connections work as expected.
- Save this QVF and store it (this will be your go-to file to import these connections whenever you need to)
- Import QVF into QMC of Qlik Sense Server or QAP to add the data connections
3rd Party solutions:
The information here is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Related Content:
- Labels:
-
App Development
Preface:
Qlik Log Reader is Qlik's proprietary high speed redo log parser for parsing the Oracle redo logs, it also provides greatly improved performance and reduces the load on the Oracle server when compared with other methods such as Oracle LogMin
...Preface:
Qlik Log Reader is Qlik's proprietary high speed redo log parser for parsing the Oracle redo logs, it also provides greatly improved performance and reduces the load on the Oracle server when compared with other methods such as Oracle LogMiner.
When the Oracle redo logs are stored in ASM, Replicate enables several techniques to improve the read performance. This includes the Copy redo logs to a temporary folder, which allows Replicate to Copy the redo logs and read it from a faster storage.
The problem originates in the 32KB packet size limitation when reading directly from ASM. Other methods like reading using the 'binary file' allows readings MBs of data, and this is why the Copy to folder does help improve performance.
Replicate now supports a new method for reading from ASM. This is accomplished by reading ASM via parallel threads. Starting from Replicate v6.2 this is the default read method for ASM. This allows Replicate to read the redo log in several threads thus improving the performance.
The Parallel Method:
Starting from Replicate v6.2 the default ASM read mode is 4 parallel threads, the parameter that configures this is called parallelASMReadThreads, the maximum value for this parameter is 8 threads. Finding the right value for a specific environment may require few testing cycles.
Using the parallel method may add some overhead as follows:
-
Some CPU overhead to the Replicate and Oracle machines.
-
More network traffic as we will be reading in 4 threads.
That being said, this overhead is understandable and may not be noticeable. Also note that the Copy method also introduces overhead:
-
Storage for the temporary location.
-
More permissions and managing the deletion of the copied logs.
-
Copying the redo logs and reading from the temporary location.
Further Optimizations with Parallel:
The parallel method does not solve the 32KB ASM read limitation, however, it does help by reading in several threads. We have added another mechanizm that can be enabled by setting the asmUsePLSQLArray internal parameter.
When enabled, Replicate will buffer 50 reads at the ASM server (where the PL/SQL is processed) and send back this larger buffer. This will cause less round trips but it will still read in 32KB buffers.
The user can enable asmUsePLSQLArray even when reading using a single thread, however, the benefit will be seen when working with parallel ASM threads. The benefit will vary from system to another, we have observed up to 10-20% improvement in throughput in some cases.
Limitation:
The 50 buffers setting is fixed. This feature can only be used on platforms where the redo log block size = 512 bytes: Linux, Windows, this excludes HPUX.
Advanced Tweak:
The parallel mode can be further optimized using the readAheadBlocks parameter.
Currently, each thread will read:
- (readAheadBlocks / parallelASMReadThreads)
The default value of the readAheadBlocks is 100,000 (in blocks), and the maximum value is 2,000,000.
Important Note
Our testing and experience so far has shown that a value of 100,000 (50MBs) is optimal for most platforms.
Summary
Support for the parallel ASM read is available starting from these versions:
- Qlik Replicate 6.1 or higher.
- Labels:
-
Configuration
The maximum number of parallel user connections for a single user in Qlik Sense is five (5). This can be exceeded by users by accident or by unexpected behavior.
Click here for Video Transcript
The related log file for this issue is:
C:\Programdata\Q
The maximum number of parallel user connections for a single user in Qlik Sense is five (5). This can be exceeded by users by accident or by unexpected behavior.
Click here for Video Transcript
The related log file for this issue is:
C:\Programdata\Qlik\Sense\Log\Repository\Audit\AuditSecurity_Repository.txt
The related message reads:
Access was denied for User: 'Domain\USER', with AccessID '264ff070-6306-4f1b-85db-21a8468939b5', SessionID: 'e3cd957b-a501-4bec-a3f8-d35170a73efa', SessionCount: '5', Hostname: '::1', OperationType: 'UsageDenied'
Environment:
Resolution:
See How to count sessions in Qlik Sense on possible scenarios on when multiple sessions are created.
When the user is consuming too many sessions, they will need to wait until the first one has correctly timed out. This is dependent on the Qlik Sense configuration.
If none of those apply, and a user is not actively connecting more than 5 times, then the below should be investigated:
Service Account has a licence assigned and QMC interaction consumes sessions
The end-user does not have a license/token assigned
In some instances, the error message may wrongfully be shown when no license/token was assigned to a user. Note that this should not be the case with the service account, as mentioned above.
iFrame access using an iOS device with Safari
iOS does not allow cookies from websites in iFrames without having first visited the embedded site directly.
To resolve this, access the site hosting the iFrame once. After that, cookies can be accepted.
The session is being resumed after the client device disconnected for an extended period of time
In the following scenarios, the client device is disconnected from Qlik Sense during an active session:
- Entering sleep mode
- Lost VPN connection
- Flight mode activated
- Lost network connection
When the session is resumed, all request sent to server contain the previous session cookie, which has expired during the disconnection. The requests with invalid session cookie leads to re-authentication for multiple requests, which leads to session count being rapidly exhausted.
This issue has been addressed and resolved in below releases, where Release Notes on "Handle 'invalid cookie' bursts in the Qlik Sense proxy Service" for additional configuration details.
- Qlik Sense Enterprise on Windows November 2019
- Qlik Sense Enterprise on Windows September 2019 Patch 1
- Qlik Sense Enterprise on Windows June 2019 Patch 6
- Qlik Sense Enterprise on Windows April 2019 Patch 5
- Qlik Sense Enterprise on Windows February 2019 Patch 6
Database maintenance of closed sessions not working correctly
Verify if any of the following tables in the Qlik Sense Repository Database (QSR) includes 5 or more records for the user that are older than 5 minutes:
- LicenseProfessionalAccessUsages
- LicenceUserAccessUsages
- LicenseAnalyzerAccessUsage
If that is the case, the maintenance/cleanup of old sessions might not be working properly.
This issue has been addressed and resolved in the below releases.
- Qlik Sense Enterprise on Windows February 2020
- Qlik Sense Enterprise on Windows November 2019 Patch 1
- Qlik Sense Enterprise on Windows September 2019 Patch 2
- Qlik Sense Enterprise on Windows June 2019 Patch 6
- Labels:
-
Administration
-
Configuration
A QlikView application (QVW) file can not be opened in the QlikView desktop client or there is a need to bypass the loading of data into memory.
Possible reasons or symptoms for this can be;
- Application requires more memory than currently available
A QlikView application (QVW) file can not be opened in the QlikView desktop client or there is a need to bypass the loading of data into memory.
Possible reasons or symptoms for this can be;
- Application requires more memory than currently available
- Calculations triggered on opening requires more memory than currently available
- Moving application to memory and preforming initial calculations takes longer time than anticipated, appearing as if QlikView desktop client has hung
Open application without data in QlikView desktop client
- Open the QlikView Desktop client.
- Go to Help > Show Start Page
- On the start page go to Recent Documents
- Locate the QlikView document that should be opened without data.
If the QlikView document can not be found in the Recent Document list, go to next section "Open Reload application without data from command prompt" - Right click on the document and select "Open <document> Without Data"
- The document is opened without data
- Save the file with a new file name in order to not overwrite the original file
Open application without data from command prompt
- Open a Windows Command Prompt
- Launch QlikView Desktop client with the /nodata switch;
"C:\Program Files\QlikView\qv.exe" /nodata C:\QlikVew\SourceDocs\qvd_generator.qvw - The document is opened without data
- Save the file with a new file name in order to not overwrite the original file
NOTE: If the file can not be opened without data, it may be corrupt and you should revert to a backup version of the file.
- Labels:
-
App Development
Log files are a crucial component when troubleshooting QlikView issues ranging from app performance issues, crashes, as well as task failures and general stability problems. This article highlights which log files are needed when and where to find th
...Log files are a crucial component when troubleshooting QlikView issues ranging from app performance issues, crashes, as well as task failures and general stability problems. This article highlights which log files are needed when and where to find them.
For information about other services, see QlikView Services and Log Guide.
Content:
- System About information:
- The QlikView installation logs:
- Service and related log files:
- Service:QVS (QlikView Server)
- Service:QMS (Management Service)
- Service:QDS (Distribution Service)
- Service: DSC (Directory Service Connector)
- Service:QVWS (WebServer)
- Service:Service Dispatcher/License Service
- Using the Log Collector (QlikView Server May 2022 and later)
It is useful when Qlik Support requires log files to assist in investigating an issue. With a complete set of logs, Qlik Support can make more accurate analysis and provide most efficient assistance on support cases. In this case, supplying the general environment information is advisable as well.
System About information:
- Open the QlikView Management Console
- Navigate to System > About
- Click More
- Copy the contents and save them as a .txt file to transfer them to Qlik Support
The QlikView installation logs:
Note: All logs must be collected for the range of dates when the issue is reported or seen. Always specific a date and time range to Qlik Support.
Service and related log files:
Service: QVS (QlikView Server)
Default Location:
Default Location: C:\ProgramData\QlikTech\QlikViewServer
See Qlik Help for more information.
Customized locations:
The location might have been changed. Identify the correct path from the QlikView Management Console > System > Setup > QVS@node > Logging > Log Folder. Alternatively, review the settings.ini stored in C:\ProgramData\QlikTech\QlikViewServer\settings.ini for the value configured in ServerLogFolder=
Commonly used for:
- Qlikview Server problems
- Performance data
- End user session problems
- CAL information
Service: QMS (Management Service)
Default Location:
C:\ProgramData\QlikTech\ManagementService\Log
See Qlik Help for more information.
Commonly used for:
- Errors in the Management Console
- Task setup issues
- Failures to commit settings
Service: QDS (Distribution Service)
Default Location:
C:\ProgramData\QlikTech\DistributionService\
Each QDS node has its own subfolder numbered 1, 2, 3, etc..
See Qlik Help for more information.
Customized Location:
The location might have been changed. Identify the correct path from the QlikView Management Console > System > Setup > QDS@node > General > Application Data Folder
Necessary logs to collect:
%Application Data Folder%\#\Log\Date(YYYYMMDD) Log folder
%Application Data Folder%\#\Log\YYYYMMDD.txt
%Application Data Folder%\#\Log\LoadBalancer_YYYYMMDD.txt
%Application Data Folder%\#\Log\Root_YYYYMMDD.txt
%Application Data Folder%\#\Log\WebService_YYYYMMDD.txt
%Application Data Folder%\#\Log\Workorder_YYYYMMDD.txt
Commonly used for:
- Distribution Service crashes
- Task failures
Detailed logs: Task log
Location:
C:\ProgramData\QlikTech\DistributionService\1\Log\
< Date > \ < Sub Folder for each distribution or reload >
Commonly used for:
- Task failures
- Distribution errors
Detailed logs: Document* (Script) Reload log
Location:
C:\ProgramData\QlikTech\DistributionService\1\Log\
< Date > \ < Sub Folder for each distribution or reload >
Commonly used for:
- Details about Task failures and reload execution, such as execution timelines and the amount of data loaded.
* The document log is a copy of the script log which needs to be enabled per document so that it will be produced by the reload task. Refer to How To Enable QlikView Document Reload Log
Service: DSC (Directory Service Connector)
Default Location:
C:\ProgramData\QlikTech\DirectoryServiceConnector\Log
See Qlik Help for more information.
Commonly used for:
- Failing to add users or groups to documents
- Authentication issues when using DMS mode
- Custom Directory problems
- Active Directory and LDAP issues
Service: QVWS (WebServer)
Default Location:
C:\ProgramData\QlikTech\WebServer\Log
See Qlik Help for more information.
Commonly used for:
- Front end web traffic diagnosis
- Ticket requests
- Load balancing determination
- Document lists
- Works in unison with IIS **
** If using IIS as Webserver, please also attach IIS log (C:\inetpub\logs\LogFiles\W3SVC1)
Service: Service Dispatcher/License Service
Default Location:
C:\ProgramData\QlikTech\LicenseService\Log
Using the Log Collector (QlikView Server May 2022 and later)
With the release of QlikView Server May 2022, log collection functionality was built into the product. The log collector will collate all of the QlikView Service logs, as well as the QlikView Server About information and Windows Events logs, if specified, for the start and end dates chosen into a .zip file and output to %ProgramData%\QlikTech\LogCollector.
Related Content:
Event Log Verbosity in Qlik View
Best setup setting for QlikView Server logging
Troubleshooting QlikView Server resource problems and crashes
Recommended Log files to analyze QlikView problem
QlikView Services and Log Guide
- Labels:
-
Configuration
-
Deployment
Several questions were raised up about the use of Qlik Sense Map Object. This article highlights few of them but the list is not exhaustive. As addition, see also Qlik Sense / NPrinting: Export vs Using Proxy, Q&A.
Question: when using built-in map ob
Several questions were raised up about the use of Qlik Sense Map Object. This article highlights few of them but the list is not exhaustive. As addition, see also Qlik Sense / NPrinting: Export vs Using Proxy, Q&A.
Question: when using built-in map object, what does the Qlik Server connect to? Qlik proprietary server? 3rd party geo services?
Answers: maps.qlikcloud.com and arcgisonline.com.
But if you are using your own Enterprise GeoAnalytics Server, you can change the in-built map chart url. See How to change the map url in built-in map chart to a local GeoAnalytics map server
Question: What information is transmitted out via the Internet?
Answers:
- on data traffic: Qlik Online Help for Qlik GeoAnalytics > Using Qlik GeoAnalytics for Qlik Sense What data is transferred to the server from the map extension?
- on ports: Qlik Online Help for Qlik Sense for administrators > Planning your deployment > Ports
Environment:
- Qlik Sense Enterprise
- Qlik sense Desktop
- Labels:
-
Configuration
End of Support for Qlik products follows Release Management Policy, as documented in the Product Terms found on the Qlik Site: On-Premise Products Release Management Policy
For detailed information on end of life and release dates, see:
End of Support for Qlik products follows Release Management Policy, as documented in the Product Terms found on the Qlik Site: On-Premise Products Release Management Policy
For detailed information on end of life and release dates, see:
Qlik Sense Enterprise on Windows Product Lifecycle
Qlik NPrinting Product Lifecycle
QlikView Product Lifecycle
Related Content:
- Labels:
-
Administration
-
Deployment
-
General Question
How to configure to use a new .pfx certificate for use with Qlik NPrinting Web Console and/or the NewsStand after converting it to the .key and .crt format
CNG-type certificates are not supported for use with NPrinting Server. See Requirements(help.q...
How to configure to use a new .pfx certificate for use with Qlik NPrinting Web Console and/or the NewsStand after converting it to the .key and .crt format
CNG-type certificates are not supported for use with NPrinting Server. See Requirements(help.qlik.com).
Items Needed:
- A certificate with the Private Key that can be extracted (PFX files are the easiest)
- Import the Password for the PFX certificate
- OpenSSL (3rd Party free software- see disclaimer at end of this article) to extract the certificate and gather the .crt and .key files. See Installing OpenSSL
Please review this information with your internal Certificate Authority or appropriate IT team that would provide the certificate and follow their guidelines if it differs from the steps here. If a new certificate cannot be issued for the Qlik NPrinting server, a workaround for the issue may be found under General: what does the certificate error(red cross) in browser mean and how to fix it.
All the steps below can be performed automatically with one click using a third-party tool called NPrinting Certificate Configurator, which can be downloaded from the Releases section. Keep in mind that Qlik does NOT support the 3rd party software mentioned and used in this documentation. Please use them at your own discretion and, if concerned, contact the proper IT team within your company to verify the ability to use non-Qlik related software in the environment.
Before proceeding to the following steps, you must first install Open SSL. See Installing OpenSSL.
Extract the .CRT and .KEY files
Three Steps:
- Extract the .crt file from the .pfx file. Using an administrative command prompt, navigate to the Open SSL/bin folder on your NPrinting computer and extract the .crt file from the .pfx file.
Test Command: openssl pkcs12 -in C:\NPCerts\QS3Cert.pfx -clcerts -nokeys -out C:\NPCerts\QS3.crt
Example Command: openssl pkcs12 -in [yourfile.pfx] -clcerts -nokeys -out [certificate.crt]
Note: The Import Password is determined by the CA when the certificate is exported/created. This is to help protect the Private Key. It should be supplied with the certificate from the 3rd Party SSL CA / Internal CA. If you do not have this password, you will not be able to use the certificate. - Extract the .key file from the .pfx file.
Test Command: openssl pkcs12 -in C:\NPCerts\QS3Cert.pfx -nocerts -out C:\NPCerts\QS3.key
Example Command: openssl pkcs12 -in [yourfile.pfx] -nocerts -out [keyfile-encrypted.key]
Note: The PEM passphrase is used to protect the new .key file you’ve created.
3. Decrypt the .key file. Qlik NPrinting cannot have a passphrase on the .key file. Follow steps below to remove/decrypt the .key file. This is REQUIRED.
Test Command: openssl rsa -in C:\NPCerts\QS3.key -out C:\NPCerts\QS3.key
Example Command: openssl rsa -in [keyfile-encrypted.key] -out [keyfile-decrypted.key]
Note: At this stage, we’re removing the pass phrase from the .key, unencrypting it for Qlik NPrinting to read it.
In the Test Command, we’re overwriting the same file in the command. This works, but if you want a separate copy of the encrypted and decrypted Key you’ll need to make them different file names or locations.
NPrinting Web Console
- Place the extracted .crt and .key files in the webconsoleproxy folder and update the app.conf file.
- Edit the Qlik NPrinting Web Console proxy configuration file: %ProgramData%\NPrinting\webconsoleproxy\app.conf.
- Uncomment by removing the # and change or add the following lines to:
- http.sslcert=${ProgramData}\NPrinting\webconsoleproxy\NPrinting.crt. Change the certificate file name if necessary.
- http.sslkey=${ProgramData}\NPrinting\webconsoleproxy\NPrinting.key. Change the private key file name if necessary.
- ${ProgramData} is the Windows ProgramData environment variable with the notation for the configuration file. As an alternative, you can insert your full path, for example, C:\ProgramData\NPrinting\webconsoleproxy\NPrinting.crt.
- SAVE the app.conf file to preserve the changes
Qlik NPrinting Newsstand
- Place the new .crt / .key files in the newsstandproxy folder and update the app.conf file.
- SAVE the app.conf file to preserve the changes
Finalize
Restart the Qlik NPrinting Web Engine and check the nprinting_webengine.log to verify there’s no issues with new certificate information.
Note: The above is an example of a clean start of the Web Engine. Default location for those logs are located: "C:\ProgramData\NPrinting\Logs"
Verify the Certificates
Verify that the certificate is being used in the browser.
Note: In this example, the certificate is correctly being presented to the browser under the URL of qlikserver3.domain.local. With this certificate, it’s the ONLY name that this certificate will trust.
Note: This is the result using the servername instead of the FQDN. You can access the URL, but it presents a “Not secure” message, but shows the correctly installed certificate. The reason for this is that the server recognizes the name, but the certificate only allows qlikserver3.domain.local. If you want multiple URL/Aliases, they need to be added in the certificate.
Related Content:
Securing the NPrinting Web Console with 3rd party certificates
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.
- Labels:
-
Configuration
Session Recovery allows users to resume their session in a QlikView document after they have terminated the previous session. It re-applies selections active when the session was closed. The feature is only available in the Full Browser/AJAX client.
...Session Recovery allows users to resume their session in a QlikView document after they have terminated the previous session. It re-applies selections active when the session was closed. The feature is only available in the Full Browser/AJAX client.
This feature is only available in QlikView.
Session recovery is not available for the QlikView Plugin or Desktop Client.
Environment:
Allow Session Recovery
Session recovery saves the current selection state for each user when a session ends. It then re-applies the selection state the next time that the same user reconnects to the same document. When using session recovery there will be a Server bookmark in the QlikView Management Console for each user that is using a document. These Server Bookmarks will reappear in the QMC even if deleted because they are generated by QlikView to handle session recovery.
Session Recovery should not be confused with an automated re-connect for an open AJAX session! Even with Session Recovery disabled, an AJAX session is not automatically closed if the browser is closed or the user navigates away from the Qlikview document. The actual Session timeout set in the Qlikview Server settings determines when the session is properly killed. In order to properly kill an AJAX session manually, the user has to close it using the Close (x) button in the top right corner of the AJAX client.
Session Recovery can be enabled/disabled in the QlikView Management Console.
Note! Session recovery affects all users and documents on a server.
To allow session recovery, tick this check box. To disallow session recovery, untick this check box.
The setting is found in System > Setup > QlikView Servers > QVS@yourserver > Documents
If you wish to disable Session Recovery, then please keep in mind that it will not automatically remove the old session recovery bookmarks for users.
How to clear a saved session
- Click view details on the document
- In the pop-up window, click Remove Last Document state
- Labels:
-
Configuration
-
How To
Information about app and storage size for Qlik Cloud for Qlik Sense Enterprise SaaS and Qlik Sense Business can be found in Qlik Sense capacity.
Note: An app on disk is typically 4-6 times bigger in memory, although this is a rule of thumb and exc
...Information about app and storage size for Qlik Cloud for Qlik Sense Enterprise SaaS and Qlik Sense Business can be found in Qlik Sense capacity.
Note: An app on disk is typically 4-6 times bigger in memory, although this is a rule of thumb and exceptions can and do occur, and an app within the "on-disk" size limit may balloon past the "in memory" limit.
App Objects have a memory limit of 10 GB, except when run on dedicated capacity.
If you are looking to compare other features between Qlik Sense Business and Qlik Sense Enterprise SaaS, see Compare product features
For more information about capacity, see:
Qlik Sense specifications and capacity
Pricing | Qlik Sense
- Labels:
-
Administration
-
Deployment
You can change or reset the password of your Qlik Account on either Qlik.com or MyQlik.
Choose your option:
Related Article: How to Register for a Qlik Account
...You can change or reset the password of your Qlik Account on either Qlik.com or MyQlik.
Choose your option:
Related Article: How to Register for a Qlik Account
Scenario 1: Reset Password from MyQlik portal
- Log in to https://myqlik.qlik.com/portal with your email address and current password
- Open Password & Security and Click Reset
- A message pops up. Click Reset Password
- Find the email sent by no.reply@qlik.com
Note: Check your spam folder if you cannot locate it. - Click Reset Password in the email
- Follow the on-screen instructions to choose a new password.
- You will now be able to log in with your new credentials (email and password combination)
Scenario 2: Forgot Password via Qlik Portals
- Hover over Login in the top right corner
- Select any of the portals you want to access.
- Click I forgot my password
- Confirm your email address
- Click Send email
- An email will be sent
- Find the email sent by no.reply@qlik.com
Note: Check your spam folder if you cannot locate it. - Click Reset Password in the email
- Follow the on-screen instructions to choose a new password.
- You will now be able to log in with your new credentials (email and password combination)
If at any point you do not receive a password or an email, see No Activation or Password Reset Email arrives or contact our support representatives.
- Labels:
-
Account Administration
A Qlik Account is required to access Qlik portals, software downloads and full access to Qlik.com site resources.
Registration Steps
- Go to register.myqlik.qlik.com
If you already have an account, please see How To Reset The Password of a Qlik Account
A Qlik Account is required to access Qlik portals, software downloads and full access to Qlik.com site resources.
Registration Steps
- Go to register.myqlik.qlik.com
If you already have an account, please see How To Reset The Password of a Qlik Account for help using your existing account. - Begin the registration process by providing your email address (a) and click Get Started (b)
To connect your account to your corporation (accessing product downloads, etc.) the email address domain must match the corporate domain.
The email address cannot be changed after account creation.
- Enter your eMail address and click Get Started
A confirmation code has been sent to your email address. You will need the code in the final step.
- Provide your First name, Last name, and Country and click Next
Depending on the Country selection, State/Province may be a required field. - Fill out your Job title (optional), Company name, and Telephone (optional), then click Next
- Provide the Verification Code (a) sent to your email address, Create a password (b), read the terms and conditions and then check the I have read and accept the terms of conditions (c) checkbox. Click Create account (d).
- Your account has been set up.
Tips for Registering
- If you are a licensed customer or a partner, make sure to provide your work e-mail. Entering a personal email address or incorrect information will cause the system to create a new contact in the system and access will not be granted. This includes entering a company name different from the name listed in the Qlik database.
- If you are a licensed Customer, do not attempt to log into the Partner Portal. Doing so will result in access issues.
- For non-licensed customers, please enter your company or personal information.
- Please note that the phone number should be entered with no characters or spacing. It should look like 1234567890 not 123-456-7890 or (123) 456 7890
- Labels:
-
Account Administration
To access your data stored on an Azure SQL database, you will need to know the server and database name that you want to connect to, and you must have access credentials. Once you have created a connection to an Azure SQL database, you can select dat
...To access your data stored on an Azure SQL database, you will need to know the server and database name that you want to connect to, and you must have access credentials. Once you have created a connection to an Azure SQL database, you can select data from the available tables and then load that data into your app or document. The Azure SQL Database Connector does not support NTLM authentication. For that reason, the Windows integrated security option is not available.
For more information, please see Create an Azure SQL database connection (Help.com).
- Labels:
-
App Development
-
Data Connection
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
This video demonstrates how to activate Qlik Sense Enterprise using Delayed Sync.
Here is a link to more information in the Support Kn
...This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
This video demonstrates how to activate Qlik Sense Enterprise using Delayed Sync.
Here is a link to more information in the Support Knowledge Base:
https://support.qlik.com/articles/000101148
Retrieve the Signed License Definition using Postman
Retrieve the Signed License Definition using PowerShell
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.
#QlikSupport
Create you very own offline map backgrounds like the examples above.
Follow the instructions provided in the attached PDF.
Create you very own offline map backgrounds like the examples above.
Follow the instructions provided in the attached PDF.
- Tags:
- geoanalytics
- Labels:
-
custom map
-
GeoAnalytics
-
geotab
-
offline
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
This video demonstrates how Qlik Sense Analyzer Capacity licensing works.
Here is a link to more information in the Support Know
...
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
This video demonstrates how Qlik Sense Analyzer Capacity licensing works.
Here is a link to more information in the Support Knowledge Base:
https://support.qlik.com/articles/000074685
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.
#QlikSupport
Qlik is proud to provide our global community with a set of downloadable Zoom backgrounds in celebration of June's Pride Month. We hope you use and enjoy them all the time - not just June!
Read a new blog post from one of our Qlik For All task members
...Qlik is proud to provide our global community with a set of downloadable Zoom backgrounds in celebration of June's Pride Month. We hope you use and enjoy them all the time - not just June!
Read a new blog post from one of our Qlik For All task members for more information on Qlik's strategic initiative to support and celebrate every passion, every difference, every heritage, every love.
#Qlik #Pride #AllofUs
(Two additional Zoom background images can be found here )
- Labels:
-
Resources