This article explains how to work around the 20 characters limit in the windows account name in ADFS when using SAML.
This article assumes you have already set up ADFS correctly with Qlik Sense.

Resolution:

In order to work around this issue, you will need to create a custom claim description.
Windows account name is limited to 20 characters length. UPN holds the full user name but also the domain name (Example: xbxpoufaloiacsvignhv.ekevezajzktyfzccvhzl@domain.local).
So, the simplest is to create a custom claim and extract the string before @ from the UPN claim description.

In ADFS, in claim descriptions, choose "Add Claim Description"

Create a new claim with a name and claim type of your choice. Claim type must have the below format.

In Relying Party Trusts, choose the Reying party trust created for Qlik Sense and in the right pane, choose "Edit Claim Rules"

In the existing claim rule, create a second rule based on template "Send Claims Using a Custom Rule" with the following rule:

c:[Type == "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn", Value =~ "^.*(@).*$"]
 => issue(Type = "http://temp.org/20charname", Value = RegexReplace(c.Value, "@.*", ""));

On the Qlik Sense side, in virtual proxy settings, including the newly created claim description as the SAML attribute for user ID

You should now be able to log in to the hub, the user name will be registered correctly in Qlik Sense even if it is more than 20 characters long.
 

By default, the QlikView AccessPoint does not display a Login or Logout button.

To enable a manual log in or log out process:

1. Open the QlikView Management Console
2. Navigate to System
3. Open the Setup tab
4. Click on the QlikView Web Servers folder
5. Select your Web Server (QVWS@QlikServerName)
6. Select Login 
   
   
   
   
7. Confirm your selection by clicking Apply

The QlikView AccessPoint now has a Sign In option.

Environment:

QlikView 

QvConnect64.exe and QvConnect32.exe are not digitally signed and cannot launch in restricted environments only allowing digitally signed software. 

The EXE created in the APPDATA\Roaming directory is not digitally signed. 


Environments:

Resolution:

This is working as intended. However, a feature was introduced that allows for the configuration of a different temporary path.

Open the settings.ini file of the QlikView Desktop client. 

• This is located in C:\Users\USER\AppData\Roaming\QlikTech\QlikView
• Add the following line:

  QVConnectFolderTmpPath=C:\YourFolder\

• The line should be added between the [Settings 7] section and the [Authentication] section.
• Save the file.

After this, the qvconnect32.exe or qvconnect64.exe will be copied to the specified folder.

This functionality is available beginning with:

QlikView November 2017 (12.20 SR 7)
QlikView November 2018 (12.30 IR)
QlikView April 2019 (12.40 IR)

Cause:

Each time that QlikView is executed it overwrites the "QvConnect" files in the folder C:\Users\ <USER>\AppData\Local\Temp\QVConnect\ 
QlikView use the QvConnect files located in the folder C:\Users\ <USER>\AppData\Local\Temp\QVConnect\to configure the db connection.
This .exe is not signed. 
 

When adding users to NPrinting via the Web Console, it will require the administrator to provide a password for the user.  The administrator may not want to have knowledge of the password and wish that the user's Active Directory credentials be used for accessing NewsStand.

Environment:

• Qlik NPrinting , 17 and newer

Cause:

NPrinting Local user Authentication and Windows Authentication are both local as NPrinting does not pass authentication to Active Directory.

Users are created and kept locally in the repository. When clicking on "Windows Login", authentication is performed by matching the Client's NT user ID+Domain with the local user's configured "Domain Account" string. This string is optional and not required when creating the local user.

Resolution:

To resolve the issue where the administrator knows the user's password, when creating a user, you may provide the password and notify the account user to type in the email address and click on 'Forgot Password' in order to receive an email that will assist with changing the current password. However, for this to work an email server needs to be configured under Email Settings.

As an alternative, the "Domain Account" configuration field for the newly created user can be populated to allow for the "Windows Login" option to be used. The new user may then change the password manually via the Web Console. Note: The user needs to be on the same domain as NPrinting and currently logged on the Windows PC to use this option.
 

 

Upgrading Qlik Sense fails during the PostgreSQL upgrade.

Environment:

• Qlik Sense Enterprise on Windows 

From the installation logs, it is failing just after trying to uninstall a patch:

MSI (s) (58:14) [10:17:25:316]: Executing op: ActionStart(Name=CA_UninstallPatch,Description=Uninstalling patch,Template=Uninstalling patch)
Action 10:17:24 76 All Sense services were stopped: True
MSI (s) (58:14) [10:17:25:319]: Executing op: CustomActionSchedule(Action=CA_UninstallPatch,ActionType=3073,Source=BinaryData,Target=UninstallPatch,)
MSI (s) (58:C4) [10:17:25:354]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIA1A5.tmp, Entrypoint: UninstallPatch
SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSIA1A5.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action Qlik.QustomActions64!Qlik.QustomActions64.PatchCustomActions.UninstallPatch
Action 10:17:25 93 Uninstalling patch
Action 10:17:26 25 Patch was uninstalled with exit code: 1

Resolution:

A previous Qlik Sense Patch is still installed.

Follow Installing and uninstalling Qlik Sense Patches  to uninstall accordingly. 

Qlik Sense cannot connect to a Pivotal Greenplum database, even if a number of new ODBC drivers can be found in the ODBC Data Source Administration.

Examples:

Qlik-apache-hive
Qlik2-greenplum

However, the listed Qlik2-greenplum driver cannot be used to create User/ System DSNs. Such an attempt returns an error similar to the following:

The setup routines for the Qlik2-greenplum ODBC driver could not be found. Please reinstall the driver. 

Resolution:

To connect Qlik Sense to Pivotal Greenplum database, the Pivotal ODBC driver needs to be installed and used with the generic ODBC connection via a DSN.  You can obtain the driver here: https://gpdb.docs.pivotal.io/43330/datadirect/datadirect_ODBC_71.html

Cause:

Greenplum driver is part of the installation package of drivers ( DataDirect Connect64) provided by Progress Software, which is utilized in Qlik ODBC Connector Package. However, it is not a supported driver, and therefore there is no UI associated with it in Qlik ODBC Connector Package. More information regarding third-party software installed along with Qlik Sense can be found in the document Qlik Sense® Third Party Software Attributions, Copyrights, Licenses and Disclosures, which is available at http://www.qlik.com/us/-/media/files/legal/license%20agreements/qlik%20sense/qlik-sense-third-party-license-terms.pdf?la=en

Connectors of Qlik ODBC Connector Package should be added in Data Load Editor > Create new connection > Qlik ODBC Connector Package > select provider. The Package is not meant to be used with generic ODBC connections. Due to license constraints, it is not possible to invoke the driver DLL files directly or create DSN over these drivers.

Content

• Background
• Qlik Licensing Service (QLS)
• Signed License Key (JWT)
• What is a JSON Web Token?
• What’s in this for me as a Customer?
• Activation Using the Signed License Key
• Frequency in which license information is updated
• Data Transmitted by an Activation Request
• Activation Reply
• Analyzer Capacity License Report Process
• Data Transmitted
• Sync Reply
• User Assignment Sync Process
• Data Transmitted
• Reply fromLicense Backend

Background

Qlik Products have generally utilized license keys to enforce license entitlements and use rights.  During activation, the licensed entitlement is downloaded to the product in the format of a Licensing Enabler File (LEF). Activation requires internet connectivity to the deployment and is triggered by entering a 16-digit serial number and a corresponding control number. Offline activation is also supported using a manual LEF by copying and pasting a text file into the activation user dialog. Communication is through an http protocol.

Qlik Licensing Service (QLS)

Introduced with the February 2019 release[GM1]  of Qlik Sense Enterprise, Qlik has developed an alternative process for product activation. There have been several drivers for this change, including a move to an https protocol for a more secure connection between the Customer deployment and Qlik infrastructure. More information follows below. 
 
To allow for Customers to make the decision when to move, Qlik has introduced the use of a Signed License Key to determine which activation method to use. Over time Qlik Licensing Service will replace the current activation process, but for now both methods of activations will work.

Signed License Key (JWT)

As mentioned above, Qlik has added one additional way to activate Qlik products. 

What is a JSON Web Token?

JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWT’s can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA.
 
Although JWT’s can be encrypted to also provide secrecy between parties, we will focus on signed tokens. Signed tokens can verify the integrity of the claims contained within it, while encrypted tokens hide those claims from other parties. When tokens are signed using public/private key pairs, the signature also certifies that only the party holding the private key is the one that signed it. That is why we refer to this as the Signed License Key.

What’s in this for me as a Customer?

With the use of a Signed License Key, there are more Product and deployment offers to use.

• Use of 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.
• Use of multi-geo deployments, such as having Qlik Sense Enterprise sites in different locations using the same list of users.
• Use of the consumption-based license, Qlik Sense Enterprise Analyzer Capacity. This additional user license is possible to use in a single or multi-cloud scenario.

All of the above is enabled by the use of the Signed License Key. This made possible as the local deployment will sync entitlement data with all deployment’s using the same Signed License Key through an online database, License Backend, hosted by Qlik within Qlik Cloud.

Activation Using the Signed License Key

This is initiated by entering a Signed License Key to the Control Panel. The request is performed by the service Licenses using port 443 (https protocol procedures applies).

Frequency in which license information is updated

Assignment information (what user has what type of access assigned) is synchronized from the license service to license.qlikcloud.com every 10 minutes. 
Changes to a license (such as adding additional analyzer capacity) can take up to 24 hours to be retrieved.

Data Transmitted by an Activation Request

Activation Reply

Analyzer Capacity License Report Process

(Time schedule is not disclosed and includes grace time to support outages in the internet connection, a/k/a Optimistic Delegation.)

Data Transmitted

Sync Reply

User Assignment Sync Process

Data Transmitted

Reply from License Backend 

 
This Reference Guide is intended solely for general informational purposes and its contents do not form part of the product documentation.  The information in this guide is subject to change without notice.  ALL INFORMATION IN THIS GUIDE IS BELIEVED TO BE ACCURATE BUT IS PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED.  Qlik makes no commitment to deliver any future functionality and purchasing decisions should not be based upon any future expectation.

Map extension gets data from Qlik Sense in a way that is different from other charts. In other charts only a portions of the data is requested and shown on the screen, if the overall data amount is bigger than a threashold. This is so called paging in those charts. But in the Map extension, there is no paging and it will try to get and show all the data in one attampt.

If the data in the areas is too big, e.g. too many polygons, it is possible that it exceedes the maximum limit of the HyperCube for Engine, which is around 200,000,000. Then the error message will appear.
 

Environment:

Qlik GeoAnalytics 

There are several things that can be considered to make optimization:

1. Reduce the density from the geometric data file so that the precision level is adjusted according to the need.
2. Or using the Simplify operation in the GeoAnalytics Connector to lower the details.
   3. In the object level, aggregate the data using the cluster, binning or within function so that not all the objects are shown at the same time.
3. Or set a limit on the layer under 'Layer Options'->'Calculation Conditions'. Thereby only showing things on the map if they have a smaller selection than a certain limit.
    

Scenario:

1. Have Qlik-Cli installed and configured (see How to install Qlik-CLI for Qlik Sense on Windows) for more insight on how to install and configure Qlik-Cli)
2. Create a PowerShell script using the following code as a base:

! Note that the code is provided as is and will need to be modified to suit specific needs. For assistance, please contact the original creators of Qlik-Cli.

Connect-Qlik -computername "QlikSenseServer.company.com"
# This will export the custom security rules and output them as secrules.json
Get-QlikRule -filter "type eq 'Custom' and category eq 'security'" -full -raw  | ConvertTo-Json  | Out-File secrules.json
# This will import secrules.json into a Sense site
# The ideal use case would be to move the developedsecurity rules from one environment to another, so connecting to another Sense site would likely be needed here
Get-Content -raw .\secrules.json |% {$_ -replace '.*"id":.*','' } | ConvertFrom-Json | Import-QlikObject

Environment:

Qlik Sense Enterprise on Windows , all versions

How to create a custom rule for Qlik Sense Management Console access using custom properties.

Example Scenario: Development Team with 2 users User1 and User2 need access to QMC Sections like App, AppObjects, Stream, Tasks, Data Connection, Users, Audit, Security Rule, Tag. They should have Read, Create and edit Access for these resources. Also, they should be restricted with the selected app and streams.
 

Resolution:

This is just a basic rule to achieve the scenarios. any additional changes on it should be implemented with proper validations. Since creating custom rules are competently based on individual requirements. For any further details please refer Help.qlik.com

Note: Security Rules can be implemented in different methods based on business requirement. There is no standard steps followed, however when working with the rule we need to ensure how the resource and filters are affecting the existing default and custom rules.

Refer to the Attached Document

When attempting to set the availability and preload options for QlikView documents, the settings do not apply as expected for the QlikView Server Cluster. 

You are unable to individually change the Document Available settings for your User Documents between your cluster nodes.

When you change the setting for one of the cluster nodes, a different cluster node's Document Available setting also changes.

Environment:

QlikView 

There is an inconsistency within the QVPR, more specifically the QVSCluster.xml file which needs to be fixed.

Although we are unable to determine exactly why/how this happens. You should be able to locate a duplicate QvsInternalID value and modify it as explained in the example.

 

Resolution:

In this example, when we change the Document Available setting for qlikserver3 node to qlikserver2, the Document Available node setting also changes when we click apply. 

To resolve this:

1. First, locate the Qlikview QVPR folder. The default location is: C:\ProgramData\QlikTech\ManagementService\QVPR\
2. Locate the QVSCluster.xml file and open it for editing with a text editor e.g Notepad or Wordpad.
3. Locate the tags starting with <QVSCluster (the end of this tag is defined by />) there will be one of these complete tags for each node in the cluster. Each QVSCluster tag will contain a value for QVSAdress and a value for QvsInternalID
4. Check the QvsInternalID for each and check it's value corresponds to it's QVSAdress value.
5. For example in the tag extract below you'll see an inconsistency in the values QVSAdress="qvp://qlikserver3/" ExternalName="" QvsInternalID="QLIKSERVER2" 
6. QvsInternalID should match the QVSAdress within that cluster tag. If it doesn't, then you've located the root of the problem.
7. As you can see in the extract below, we have two instances of QLIKSERVER2 but for two different QVS servers in the cluster (which are identified in blue).
   
   Example:
   
     <QVSCluster QlikviewServerID="7fa821d7-16a7-4b50-b796-5b5f7d30ee98" QVSAdress="qvp://qlikserver1/" ExternalName="" QvsInternalID="QLIKSERVER1" ModifiedByUser="domain\User1" ModifiedTime="2017-09-26T07:15:36.2290388+02:00" ID="a7afa1c5-1a2e-433c-9dc0-994e3a54e641" />
   
     <QVSCluster QlikviewServerID="7fa821d7-16a7-4b50-b796-5b5f7d30ee98" QVSAdress="qvp://qlikserver2/" ExternalName="" QvsInternalID="QLIKSERVER2" ModifiedByUser="domain\User1" ModifiedTime="2017-09-26T07:15:36.2290388+02:00" ID="189e9661-4dea-4868-8b60-3d485e6842de" />
   
     <QVSCluster QlikviewServerID="7fa821d7-16a7-4b50-b796-5b5f7d30ee98" QVSAdress="qvp://qlikserver3/" ExternalName="" QvsInternalID="QLIKSERVER2" ModifiedByUser="domain\User1" ModifiedTime="2017-09-26T07:15:36.2290388+02:00" ID="19ada5a7-1e06-462b-b135-6316ad381a2a" />
   
   
8. In this server example we can now safely change the QvsInternalID value for the QVSCluster  (which is related to QVSAdress="qvp://qlikserver3/" )
9. We locate the value QvsInternalID="QLIKSERVER2" and change to QvsInternalID="QLIKSERVER3"
10. Save the XML file.
11. Restart the:
    • QlikView Management Service
    • QlikView Distribution Service
12. Test the Document Available setting now works independently.

How to find the version number of your installed Qlik product: 

The fastest way to locate the version number of your installed Qlik products(s) is to open up the “Programs and Features” section in the Control Panel of your operating system.

1. Go to the Windows Start menu
2. Type Programs and locate either Programs and Features or Add and Remove Programs
3. All installed programs will be listed. 
4. The column “Version”  displays the version of your installed Qlik product(s).

Scenario:

Stream A has application 1, application 2, application 3. User 1 can only see application 1, cannot see application 2 and application 3 of stream A. User 2 can only see application 2, cannot see application 1 and application 3 of stream A.

Resolution:

This is just a basic rule to achieve the scenarios. Any additional changes will not be supported. Since creating custom rules are competently based on individual requirements. For any further details please refer Help.qlik.com

In this example, we are disabling the default rule and creating Custom Rule to achieve the scenario.

Note: When disabling default rule always ensure it doesn't break existing functionality.

Refer to the Attached Document

Qlik Sense is unavailable. The Management Console and Hub fail to load with the message The page can't be displayed or The page can't be reached (Browser dependent). 

The Qlik Sense Repository logs read: Fatal exception Operation is not supported on this platform 

20170921T151627.957+0700    ERROR    UTSE-QSENSE    System.Repository.Repository.QRSMain    11    33d038ef-eb73-4ae1-95fe-8fc5a38829f9    UNITHAI\senseadmin    
Fatal exception    Operation is not supported on this platform.
An exception was thrown while invoking the constructor 'Void .ctor()' on type 'HttpListenerWrapper'. --->
Operation is not supported on this platform. (See inner exception for details.)       at System.Net.HttpListener..ctor()
   at Qlik.Sense.Common.Communication.Server.HttpListenerWrapper..ctor()
   at lambda_method(Closure , Object[] )
   at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()
   at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()
   at Autofac.Core.Activators.Reflection.ReflectionActivator.ActivateInstance(IComponentContext context, IEnumerable`1 parameters)
   at Autofac.Core.Resolving.InstanceLookup.Activate(IEnumerable`1 parameters)
   at Autofac.Core.Resolving.InstanceLookup.Execute()

Cause:

Corruption of underlying registry keys used in netsh commands

Note: Make sure no changes has been made to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP
Start  REG_DWORD  0x00000003(3) should be enable
Start  REG_DWORD  0x00000004(4) is disable. This is the wrong setting. 

 

Resolution:

1. Open Registry Editor on Windows OS

      Go to Windows Start menu >> Run >> regedit

2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\SslBindingInfo

     Delete all the entries under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters\SslBindingInfo

      Please make a backup before deleting all of the keys.

3. Restart all Qlik Sense services (especially Qlik Sense repository service )

4. Try to access log into the QMC / HUB.

Related Content:

Qlik Sense - How to troubleshoot issue to access QMC and HUB 

Partners who resell subscription licenses will not be able to see them in the Support Portal. This is working as designed as Subscription Licenses by default are supported by Qlik. 

There are two ways of retrieving the license details

1. To request the "Control Number" and similar, the Partner should always provide details of a contact person from the Customer company
2. Customer can always get the licenses details in the Support Portal and can retrieve them there. (If not the Customer should contact Qlik directly).

Connecting with an Odata connector in the Web Connector Package against Sharepoint may fail with:

HTTP error 403 (forbidden)

Environment:

Qlik Web Connectors 

If both Windows and Forms authentication is enabled in Sharepoint the OData connection attempt is redirected to the Form, and windows authentication fails. The workaround for this is to either disable forms authentication or to use a REST or Web File connection instead to get your data.

In addition, review Administrator approval and consent for Web Connectors (Azure storage, Office 365 Sharepoint, Dynamics365 CRM, Onedrive, Outlook 365)  for Sharepoint Connector requirements.

This article provides steps on how to ensure your partner profile is available on the Qlik Partner Directory at  Find a Partner.

1. Verify your account is not listed in the Partner Directory.
2. Follow the attached quick guide to ensure your partner account is listed
3. Check the Partner Directory to ensure your listing is now visible.
   If a listing is not in the directory, inform your Partner Manager to further troubleshoot.
4. If you are unable to get in touch with your Partner Manager or run into additional issues with this, please contact Customer Support for further assistance.

Storing a table containing NULL value to a txt or qvd file fails with error General Script Error in statement handling

For example, the following piece of the script fails with the above error when executed:

DataTable: 
LOAD * INLINE [ 
NP 
1 
]; 

LEFT JOIN
LOAD  * INLINE [ 
NP, AD 
2, test 
]; 

STORE AD FROM DataTable INTO [lib://Temp/test.csv] (txt); 

Environment:

• Qlik Sense Enterprise on Windows , November 2018 IR to Patch 4 versions

Resolution:

• Verify if there are extra and unintended characters in any of the column names (blank spaces, extra letters). Remove them and run the script again. In addition, see IsNull - script and chart function which may help with troubleshooting.
• Verify that sufficient disk space is available. 
• This issue was reproduced in lab only in the November 2018 releases and not on newer builds. There was no fix officially produced for the problem found on November 2018. Note that November 2018 is no longer a supported version, so upgrading to a newer release to check if issue is resolved would be required. See Qlik Sense, QlikView, NPrinting, Qlik Insight Bot End of Support Date 

If you experience the issue in an up to date Sense environment, connect with our active Qlik Community for creative application development assistance and ideas.

Alert emails from the QlikView Management Console are relayed to smtp-relay.gmail.com.

Emails are not delivered, and the sender address gets a "Mailbox unavailable. The server response was: 5.7.1 Invalid credentials for relay [IPADDRESS]." 

Environment:

QlikView 

Resolution:

This is not an issue with QlikView, but with Gmail's server configuration: https://support.google.com/a/answer/6140680?hl=en

"Invalid Credentials for relay: 

The IP address you registered in the G Suite SMTP relay service setting doesn’t match domain of the account this email is being sent from. If you are trying to relay mail from a domain that isn’t registered in your Googles Apps account, you must configure your mail server either to use SMTP AUTH to identify the sending domain or to present one of your domain names in the HELO or EHLO command. See SMTP Relay service setting for more information."

This needs to be sorted out with Google's support.

The Qlik Sense Engine Service stops but engine.exe remains running.

This is usually due to a high memory consumption, so when you stop the Qlik Sense Engine Service, the engine.exe will keep running it has released the memory. This can take a long time. 

Possible error message in Windows events log:

Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: Engine.exe (77404) consumed 66804117504 bytes, dotnet.exe (29264) consumed 581591040 bytes, and dotnet.exe (49860) consumed 523714560 bytes.

Resolution:

The engine.exe can be manually stopped.

Related Content:

Windows successfully diagnosed a low virtual memory condition