Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Contact
Find Answers
Join Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Get Support
Have a Question?
Search Qlik's Support knowledge database or request assisted support for your highly complex issues.
Submit a Case
Talk with a Representative
Critical Issues
Experiencing a serious product issue? Please Contact us by phone. Click here to view phone numbers and hours by region.
Contact UsWelcome Guest
Installed Qlik Products
My Environments
Log your environments to ensure faster and more targeted troubleshooting.
View Available Licenses
My Licenses
Understand your licenses to help you maximize your experience.
- ALERT: Qlik Community Page Click here
Knowledge
QlikView 11.20 End of Life Upgrade: Known Issues and changes in product behavior
Article Number: 000047422 | Last Modified: 2019/07/22Description
Known issues experienced when performing an upgrade of QlikView 11.20 to QlikView 12.20 / November 2017 or 12.30 / November 2018 or up, complementary to What's New in QlikView November 2018. The linked information is not exclusive to problems, but also includes changes in behaviour.
For information regarding QlikView 11.20 and its End of Life ( EOL ) date, as well as Extended Support, see Extended Support for QlikView 11.20 and Qlik NPrinting 16, or the official Qlik Support Blog.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
Resolution
Intended Changes
| User / Administrator impact | Behaviour 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. |
| Resource consumption higher in QlikView 12.x | When the data in the document is loaded in QlikView 12, it is transposed from row wise (as it's stored in file) to column wise (as it's used in memory). While the transposing takes place, QlikView needs double the memory of the size of the data. Overall performance and stability improvements are expected with this change. |
| The list of distributed to users in QMC > Status > Tasks > Task Details is truncated in QlikView 12.10 and above | 11.20 displayed the distribution list in its entirety, potentially cluttering the task overview with a long list that required scrolling or moved out of the browser window. 12.10 and above truncates the list, giving a better overall summary. |
| 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 11.20 EOL Upgrade: QlikView Server upgrade fails with unspecified reason | Verify if the current ProgramData folder for the QlikView Server Service is fully accessible by the account used to execute the installation package. |
| QlikView: "Index out of range. must be non negative" in the QMC, when selecting tasks | After upgrading from QlikView 11.2 to QlikView November 2017 some of the tasks display a pop-up when you click on the task name saying: "Index was out of range. Must be non-negative and less than the size of the collection." |
| QlikView November / 12.20: Personal Edition warning when opening a .qvw document saved in QlikView 11.20 | The message "This QlikView document was created by another QlikView Personal Edition user. Since you are using a QlikView Personal Edition, ..." is displayed. This can be accepted or aborted. The document will then open. |
| QlikView 11.20 EOL Upgrade: Upgrade to 12.20 (November 2017 and up) leads to empty Accesspoint | A successfull QlikView upgrade to 12.20 (November 2017 and up) shows an empty AccessPoint. Services are running. |
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. |
| Performance degrade on Sheet change | After an upgrade to QlikView 12.10, switching between complex sheets results in a performance degrade, with all chart calculations taking longer to complete than in QlikView 11.20. |
| After upgrading 12.10 SharePoint task are failing | This results from an issue with login information, and it can be resolved by adding the following to the Settings.ini.file: “WebFileUserAgent="curl/7.51.0" |
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.