Issue

Why do I get Incomplete Visualization or Invalid Visualization errors in my Qlik Apps

Environment

• Qlik Sense Enterprise on Windows 
• Qlik Sense Business 

Resolution

• Check for and fix incomplete chart dimensions or measures and also check for NULL values
• Update your visualization bundles.
  • These bundles must be the same version as the version of Qlik Sense that is installed. A bundle can be copied from a different Qlik Sense server so long as it is the same Qlik version and patch of the Target Qlik Server which needs its bundle updated
  • If supported 3rd party bundles, check with your vendor and upload a supported, current bundle version
• Use supported Native Qlik Bundles

Cause

• Incomplete Visualizations:
  • The chart may have invalid dimensions or measure due to recent changes by a developer
• Invalid Visualizations:
  • Wrong bundle version uploaded to the current Qlik Sense server, perhaps from an older Qlik Sense server
  • Unsupported or outdated 3rd party bundles
  • Incorrectly developed custom visualization bundle

Related Content

• Visualization bundles
• Dashboard bundles
• Installing, importing and exporting your visualizations
• Creating and editing visualizations
• Troubleshooting - Creating visualizations
• Null values in visualizations

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

This article describes how to resolve the OAUTH Error Status 400 error preventing successful configuration and download capability of the MS Office addin manifest necessary for Tabular Reporting.

{"errors":[{"title":"Invalid redirect_uri","detail":"redirect_uri is not registered","code":"OAUTH-1","status":"400"}],"traceId":"0000000000000000xxxxxxxxxxxxxxxx"}

Resolution

An OAuth client configuration is required to install the Qlik add-in for Microsoft Excel. The add-in is used by report developers to prepare report templates which control output of tabular reports  from the Qlik Sense app.

Review or re-do the steps documented in Creating an OAuth client for the Qlik add-in for Microsoft Excel. 

Verify you have included the user_default scope.

Example of a working OAUTH configuration:

Cause 

The OAUTH configuration was not set correctly, such as missing the user_default scope, or not setting up the redirect link.

Related Content

Preparing and obtaining the add-in manifest

Qlik Tabular Reporting General Troubleshooting and Best Practices

Tabular Reporting available in Qlik Cloud Enterprise and Premium editions. See for Product Description for Qlik Cloud® Subscriptions for details. *Not included Qlik Cloud Standard and  Government Editions.

Environment

Qlik Cloud 

When replicating a CDS View the Updates are being processed as Inserts not Updates. In SAP the CDS views delta with UPSERT and SAP capture INSERT and UPDATE both as one operation which is treated as INSERT.

If you have a SAP login you can look up SAP Note 3300238 for more information as shown below:

SAP Note 3300238 - ABAP CDS CDC: ODQ_CHANGEMODE not showing proper status forcreation
Component: BW-WHM-DBA-ODA (SAP Business Warehouse > Data Warehouse Management > Data Basis >Operational Data Provider for ABAP CDS, HANA & BW), Version: 4, Released On: 19.01.2024

Resolution

This is working as expected. It is the designed behavior of the CDC logic. For both insert and update, ODQ_CHANGEMODE = U and ODQ_ENTITYCNTR = 1.

The CDC-delta logic is designed as UPSERT-logic. This means a DB-INSERT (or create) or a DB-UPDATE both get the ODQ_CHANGEMODE = U and ODQ_ENTITYCNTR = 1. It's not possible to distinguish in CDC-delta between Create and Update.

Environment

Qlik Replicate 
SAP S/4HANA
SAP BW/4HANA

The problem occurs when running a reload from Data Gateway to a Cloudera DB (Cloudera Hive).
The reload is completed correctly, but the fields are imported with aliases. This means that the reload imports the fields as 'TableName.FieldName' instead of importing them as just 'FieldName'.
For example, with this script:

LOAD meter_id,
Field1,
Field2,
Field3;

[meter_attribute]:
SELECT "meter_id",
"Field1",
"Field2",
"Field3"
FROM internaldb."meter_attribute";

Fields are imported as: meter_attribute.Field1, meter_attribute.Field2, meter_attribute.Field3.

Resolution

The problem can be fixed adding this row
EnableUniqueColumnName=0
to the connection string, as shown in the image here below.

Notice that it is not necessary to select the  "Allow non-SELECT queries" option in the connector.

In order to make Data Preview work reliably with any new Cloudera connections, we recommend to add the snippet below to this file
C:\ProgramData\Qlik\Gateway\genericodbc_database_syntax.json
and restart the Data Gateway service.

  {
    "SyntaxId": "ClouderaHive",
    "DisplayName": "Cloudera Hive syntax",
    "DelimiterStart": "`",
    "DelimiterEnd": "`",
    "DataPreviewSelectTemplate": "SELECT ${COLUMN_LIST} FROM ${TABLE_NAME} ${FILTER} LIMIT ${LIMIT_VALUE}",
    "DatabaseTerm": "catalog",
    "OwnerTerm": "schema"
  }

This snippet re-configures all the custom syntax settings for the driver. 

Please, notice that the block must have a comma (,) either immediately before or after it as shown in the screenshot below.

Once restarted, open the data connection editor again and the "Cloudera Hive syntax" option should appear, as in this image.

Internal Investigation ID

QB-26342

Environment

• Qlik Cloud
• Qlik Data Gateway Direct Access all versions

Reload fails in QMC even though script part is successfull in Qlik Sense Enterprise on Windows November 2023 and above.

When you are using a NetApp based storage you might see an error when trying to publish and replace or reloading a published app.

In the QMC you will see that the script load itself finished successfully, but the task failed after that.

ERROR QlikServer1 System.Engine.Engine 228 43384f67-ce24-47b1-8d12-810fca589657
 Domain\serviceuser QF: CopyRename exception:
 Rename from \\fileserver\share\Apps\e8d5b2d8-cf7d-4406-903e-a249528b160c.new 
to \\fileserver\share\Apps\ae763791-8131-4118-b8df-35650f29e6f6 
failed: RenameFile failed in CopyRename

ExtendedException: Type '9010' thrown in file
 'C:\Jws\engine-common-ws\src\ServerPlugin\Plugins\PluginApiSupport\PluginHelpers.cpp'
 in function 'ServerPlugin::PluginHelpers::ConvertAndThrow'
 on line '149'. Message: 'Unknown error' and additional debug info:
 'Could not replace collection 
\\fileserver\share\Apps\8fa5536b-f45f-4262-842a-884936cf119c] with
[\\fileserver\share\Apps\Transactions\Qlikserver1\829A26D1-49D2-413B-AFB1-739261AA1A5E],
 (genericException)'

<<< {"jsonrpc":"2.0","id":1578431,"error":{"code":9010,"parameter":
"Object move failed.","message":"Unknown error"}}

ERROR  Qlikserver1  06c3ab76-226a-4e25-990f-6655a965c8f3
  20240218T040613.891-0500  12.1581.19.0  
Command=Doc::DoSave;Result=9010;ResultText=Error: Unknown error
  0  0  298317  INTERNAL&
emsp; sa_scheduler  b3712cae-ff20-4443-b15b-c3e4d33ec7b4
  9c1f1450-3341-4deb-bc9b-92bf9b6861cf  Taskname  Engine  Not available
  Doc::DoSave  Doc::DoSave  9010  Object move failed.
  06c3ab76-226a-4e25-990f-6655a965c8f3

Resolution

Potential workarounds

• Roll back your upgrade to a version earlier than November 2023
• Change the storage to a file share on a Windows server

Cause 

The most plausible cause currently is that the specific engine version has issues releasing File Lock operations. We are actively investigating the root cause, but there is no fix available yet.

An update will be provided as soon as there is more information to share.

Internal Investigation ID(s) 

QB-25096
QB-26125

Environment

• Qlik Sense Enterprise on Windows November 2023 and above

This article explains how the Amazon SNS connector in Qlik Application Automations can be used to set up webhooks that trigger when a object creation event occurs in Amazon S3. This connector only has webhooks available.

Content:

• How to connect
• Using this in an automation

How to connect

Search for the "Amazon SNS" connector in Qlik Application Automations. When you click connect, you will be prompted for the following input parameters:

• Aws_access_key_id: This is the access key you obtain from AWS.
• Aws_secret_access_key: This is the secret key you obtain from AWS.
• Region: Your AWS region where your resources are situated.

You must obtain the AWS Access Key from IAM in your AWS console. This can be obtained by going to the IAM section in AWS and in the left side panel choose users.

Here you can choose either for an already existing user or creating a new one by clicking the "Add Users" button in the topright.

When you create a new user, you must provide a user name and click next. You do not need to give this user access to the AWS console. In the next step, you will give permissions to do this IAM user.

The following policy needs to be created and attached to the IAM user, replace the account-id with your account ID:

Other permissions that are suggested to add are:

• s3:ListBucket
• s3:ListAllMyBuckets
• sns:ListTopics

Furthermore, the IAM user must be made an owner of a S3 bucket when creating a notification configuration.

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:PutBucketNotification",
                "iam:PassRole",
                "sns:Publish",
                "sns:CreateTopic",
                "sns:Subscribe"
            ],
            "Resource": [
                "arn:aws:s3:::*",
                "arn:aws:iam::account-id:role/*",
                "arn:aws:sns:*:account-id:*"
            ]
        },
        {
            "Sid": "VisualEditor1",
            "Effect": "Allow",
            "Action": "sns:Unsubscribe",
            "Resource": "*"
        }
    ]
}

You will have to create an access key for the IAM user.

This can be done in the (a) Users menu and in the (b) Security credentials tab. Click (c) Create access key.

Choose Third-party service and choose to understand the above recommendation, click next:

You will now have your access key and secret key and can finish creating the datasource in Qlik Application Automation:

Using this in an automation

You can use this in an automation, but only as a webhook. When you create a new automation, you will be presented with a blank canvas. Select the Start block and change the run mode to webhook.

Choose an event type next. These are currently limited to S3 object creation events. You will have lookup capabilities available to other parameters, such as bucket and topic selection:

After saving the automation, you can test the webhook by uploading objects in your S3 bucket and see in your automation run history that it is triggering this automation.

The use of this is that you can now trigger tasks after a object is uploaded to S3. Common tasks will be to reload a Qlik Sense app or trigger a data pipeline in any of our other connectors:

If a tenant previously had an incomplete SMTP configuration with their Qlik Cloud, an error message will now be shown to the Tenant Administrator:

• Your email providers is not working – Go to Settings 

Resolution

To resolve this error a Tenant Admin can enter valid SMTP credentials. 

At the moment, it is not possible to delete/clear the previous credential entry in the authentication.  An option to clear the credentials is being prepared to support a return to a default (non-configured/empty) state and is expected to be available in the coming weeks.

We will update this article when the ability to clear becomes available. 

Example SMTP Error

Cause 

With the release of the SMTP service connectivity for Microsoft O365 from the Management Console, more stringent error checking was added to the basic authentication configuration. 

Related Content 

If interested, Admins can still successfully connect to Microsoft 0365 SMTP with this error showing. More details on the new available 0Auth2 authentication can be found here: Qlik Cloud: Introducing OAuth2 authentication for ... - Qlik Community - 2444243

Internal Investigation ID

• QB-26792

Environment

• Qlik Cloud

Many of the GeoAnalytics can be executed with a split input of the indata table. This article explains which and how to modify the code that the connector produces. Operations that cannot be Splittable are mostly the aggregating and hence not Splittable. When loadable tables are used for input, inline tables are created in loops and can be used for a quick way to split. Of course it's possible to write custom code to do the splitting instead.

Making calls with large indata tables often causes time outs on the server side, splitting is a way around that. 

Environment:

Qlik GeoAnalytics 

 

Binning and SpatialIndex

Bining and SpatialIndex differs from other operations, they are not placing any call to the server if the indata are internal geometries, ie lat ,ong points. The operations als produce the same type of results so the resulting tables can be concatenated.
 

Resolution:

Example, a Within operation

Before the edit

The code as the connector produces it:

/* Generated by Idevio GeoAnalytics for operation Within ---------------------- */
Let [EnclosedInlineTable] = 'POSTCODE' & Chr(9) & 'Postal.Latitude' & Chr(9) & 'Postal.Longitude';
Let numRows = NoOfRows('PostalData');
Let chunkSize = 1000;
Let chunks = numRows/chunkSize;
For n = 0 to chunks
   Let chunkText = '';
   Let chunk = n*chunkSize;
   For i = 0 To chunkSize-1
      Let row = '';
      Let rowNr = chunk+i;
      Exit for when rowNr >= numRows;
      For Each f In 'POSTCODE', 'Postal.Latitude', 'Postal.Longitude'
         row = row & Chr(9) & Replace(Replace(Replace(Replace(Replace(Replace(Peek('$(f)', $(rowNr), 'PostalData'), Chr(39), '\u0027'), Chr(34), '\u0022'), Chr(91), '\u005b'), Chr(47), '\u002f'), Chr(42), '\u002a'), Chr(59), '\u003b');
      Next
      chunkText = chunkText & Chr(10) & Mid('$(row)', 2);
   Next
   [EnclosedInlineTable] = [EnclosedInlineTable] & chunkText;
Next
chunkText=''


Let [EnclosingInlineTable] = 'ClubCode' & Chr(9) & 'Car5mins_TravelArea';
Let numRows = NoOfRows('TravelAreas5');
Let chunkSize = 1000;
Let chunks = numRows/chunkSize;
For n = 0 to chunks
   Let chunkText = '';
   Let chunk = n*chunkSize;
   For i = 0 To chunkSize-1
      Let row = '';
      Let rowNr = chunk+i;
      Exit for when rowNr >= numRows;
      For Each f In 'ClubCode', 'Car5mins_TravelArea'
         row = row & Chr(9) & Replace(Replace(Replace(Replace(Replace(Replace(Peek('$(f)', $(rowNr), 'TravelAreas5'), Chr(39), '\u0027'), Chr(34), '\u0022'), Chr(91), '\u005b'), Chr(47), '\u002f'), Chr(42), '\u002a'), Chr(59), '\u003b');
      Next
      chunkText = chunkText & Chr(10) & Mid('$(row)', 2);
   Next
[EnclosingInlineTable] = [EnclosingInlineTable] & chunkText;
Next
chunkText=''


[WithinAssociations]:
SQL SELECT [POSTCODE], [ClubCode] FROM Within(enclosed='Enclosed', enclosing='Enclosing')
DATASOURCE Enclosed INLINE tableName='PostalData', tableFields='POSTCODE,Postal.Latitude,Postal.Longitude', geometryType='POINTLATLON', loadDistinct='NO', suffix='', crs='Auto' {$(EnclosedInlineTable)}
DATASOURCE Enclosing INLINE tableName='TravelAreas5', tableFields='ClubCode,Car5mins_TravelArea', geometryType='POLYGON', loadDistinct='NO', suffix='', crs='Auto' {$(EnclosingInlineTable)}
SELECT [POSTCODE], [Enclosed_Geometry] FROM Enclosed
SELECT [ClubCode], [Car5mins_TravelArea] FROM Enclosing;
[EnclosedInlineTable] = '';
[EnclosingInlineTable] = '';

/* End Idevio GeoAnalytics operation Within ----------------------------------- */

After edit

The header and the call is moved inside of the loop. chunkSize decides how big each split is.

Note that the first inline table now comes after the first one, this to get the call inside of the iteration.

/* Generated by Idevio GeoAnalytics for operation Within ---------------------- */

Let [EnclosingInlineTable] = 'ClubCode' & Chr(9) & 'Car5mins_TravelArea';
Let numRows = NoOfRows('TravelAreas5');
Let chunkSize = 1000;
Let chunks = numRows/chunkSize;
For n = 0 to chunks
   Let chunkText = '';
   Let chunk = n*chunkSize;
   For i = 0 To chunkSize-1
      Let row = '';
      Let rowNr = chunk+i;
      Exit for when rowNr >= numRows;
      For Each f In 'ClubCode', 'Car5mins_TravelArea'
         row = row & Chr(9) & Replace(Replace(Replace(Replace(Replace(Replace(Peek('$(f)', $(rowNr), 'TravelAreas5'), Chr(39), '\u0027'), Chr(34), '\u0022'), Chr(91), '\u005b'), Chr(47), '\u002f'), Chr(42), '\u002a'), Chr(59), '\u003b');
      Next
      chunkText = chunkText & Chr(10) & Mid('$(row)', 2);
   Next
   [EnclosingInlineTable] = [EnclosingInlineTable] & chunkText;
Next
chunkText=''

Let numRows = NoOfRows('PostalData');

Let chunkSize = 1000;
Let chunks = numRows/chunkSize;
For n = 0 to chunks

   Let [EnclosedInlineTable] = 'POSTCODE' & Chr(9) & 'Postal.Latitude' & Chr(9) & 'Postal.Longitude';

   Let chunkText = '';
   Let chunk = n*chunkSize;
   For i = 0 To chunkSize-1
      Let row = '';
      Let rowNr = chunk+i;
      Exit for when rowNr >= numRows;
      For Each f In 'POSTCODE', 'Postal.Latitude', 'Postal.Longitude'
         row = row & Chr(9) & Replace(Replace(Replace(Replace(Replace(Replace(Peek('$(f)', $(rowNr), 'PostalData'), Chr(39), '\u0027'), Chr(34), '\u0022'), Chr(91), '\u005b'), Chr(47), '\u002f'), Chr(42), '\u002a'), Chr(59), '\u003b');
      Next
      chunkText = chunkText & Chr(10) & Mid('$(row)', 2);
   Next
   [EnclosedInlineTable] = [EnclosedInlineTable] & chunkText;

   [WithinAssociations]:
   SQL SELECT [POSTCODE], [ClubCode] FROM Within(enclosed='Enclosed', enclosing='Enclosing')
   DATASOURCE Enclosed INLINE tableName='PostalData', tableFields='POSTCODE,Postal.Latitude,Postal.Longitude', geometryType='POINTLATLON', loadDistinct='NO', suffix='', crs='Auto' {$(EnclosedInlineTable)}
   DATASOURCE Enclosing INLINE tableName='TravelAreas5', tableFields='ClubCode,Car5mins_TravelArea', geometryType='POLYGON', loadDistinct='NO', suffix='', crs='Auto' {$(EnclosingInlineTable)}
   SELECT [POSTCODE], [Enclosed_Geometry] FROM Enclosed
   SELECT [ClubCode], [Car5mins_TravelArea] FROM Enclosing;
   [EnclosedInlineTable] = '';
   [EnclosingInlineTable] = '';

Next
chunkText=''
/* End Idevio GeoAnalytics operation Within ----------------------------------- */

Example, a AddressPointLookup operation

Before the edit

The code as the connector produces it:

/* Generated by GeoAnalytics for operation AddressPointLookup ---------------------- */
Let [DatasetInlineTable] = 'id' & Chr(9) & 'STREET_NAME' & Chr(9) & 'STREET_NUMBER';
Let numRows = NoOfRows('data');
Let chunkSize = 1000;
Let chunks = numRows/chunkSize;
For n = 0 to chunks
   Let chunkText = '';
   Let chunk = n*chunkSize;
   For i = 0 To chunkSize-1
      Let row = '';
      Let rowNr = chunk+i;
      Exit for when rowNr >= numRows;
      For Each f In 'id', 'STREET_NAME', 'STREET_NUMBER'
         row = row & Chr(9) & Replace(Replace(Replace(Replace(Replace(Replace(Peek('$(f)', $(rowNr), 'data'), Chr(39), '\u0027'), Chr(34), '\u0022'), Chr(91), '\u005b'), Chr(47), '\u002f'), Chr(42), '\u002a'), Chr(59), '\u003b');
      Next
      chunkText = chunkText & Chr(10) & Mid('$(row)', 2);
   Next 
   [DatasetInlineTable] = [DatasetInlineTable] & chunkText; 
Next
chunkText=''
[AddressPointLookupResult]:
SQL SELECT [id], [Dataset_Address], [Dataset_Geometry], [CountryIso2], [Dataset_Adm1Code], [Dataset_City], [Dataset_PostalCode], [Dataset_Street], [Dataset_HouseNumber], [Dataset_Match] 
FROM AddressPointLookup(searchTextField='', country='"Canada"', stateField='', cityField='"Toronto"', postalCodeField='', streetField='STREET_NAME', houseNumberField='STREET_NUMBER', matchThreshold='0.5', service='default', dataset='Dataset')
DATASOURCE Dataset INLINE tableName='data', tableFields='id,STREET_NAME,STREET_NUMBER', geometryType='NONE', loadDistinct='NO', suffix='', crs='Auto' {$(DatasetInlineTable)}
;
[DatasetInlineTable] = '';
/* End GeoAnalytics operation AddressPointLookup ----------------------------------- */

After edit

The header and the call is moved inside of the loop. chunkSize decides how big each split is.

/* Generated by GeoAnalytics for operation AddressPointLookup ---------------------- */
Let numRows = NoOfRows('data');
Let chunkSize = 1000;
Let chunks = numRows/chunkSize;
For n = 0 to chunks

   Let [DatasetInlineTable] = 'id' & Chr(9) & 'STREET_NAME' & Chr(9) & 'STREET_NUMBER';

   Let chunkText = '';
   Let chunk = n*chunkSize;
   For i = 0 To chunkSize-1
      Let row = '';
      Let rowNr = chunk+i;
      Exit for when rowNr >= numRows;
      For Each f In 'id', 'STREET_NAME', 'STREET_NUMBER'
         row = row & Chr(9) & Replace(Replace(Replace(Replace(Replace(Replace(Peek('$(f)', $(rowNr), 'data'), Chr(39), '\u0027'), Chr(34), '\u0022'), Chr(91), '\u005b'), Chr(47), '\u002f'), Chr(42), '\u002a'), Chr(59), '\u003b');
      Next
     chunkText = chunkText & Chr(10) & Mid('$(row)', 2);

   Next 
   [DatasetInlineTable] = [DatasetInlineTable] & chunkText;

   [AddressPointLookupResult]:
   SQL SELECT [id], [Dataset_Address], [Dataset_Geometry], [CountryIso2], [Dataset_Adm1Code], [Dataset_City], [Dataset_PostalCode], [Dataset_Street], [Dataset_HouseNumber], [Dataset_Match] 
   FROM AddressPointLookup(searchTextField='', country='"Canada"', stateField='', cityField='"Toronto"', postalCodeField='', streetField='STREET_NAME', houseNumberField='STREET_NUMBER', matchThreshold='0.5', service='default', dataset='Dataset')
   DATASOURCE Dataset INLINE tableName='data', tableFields='id,STREET_NAME,STREET_NUMBER', geometryType='NONE', loadDistinct='NO', suffix='', crs='Auto' {$(DatasetInlineTable)}
   ;
   [DatasetInlineTable] = '';

Next
chunkText=''
/* End GeoAnalytics operation AddressPointLookup ----------------------------------- */

Question

• It has become necessary to use an MS Excel Tabular Report in a different tenant.

Solution

1. Make a copy of the original MS Excel Tabular Report template file
2. Open the MS Excel Tabular Report template file
3. Click on the MS Excel Office Addin in the Excel Ribbon (Click on the 'alternate', 'new' tenant MS Office Excel Addin)
4. Log into the tenant (ensure all popup blockers are disabled)

5. In the add-in window, click the 'Home'  tab in the toolbar

6. Next to Source app,  click ... 

7. From the menu, select Change template connection

8. In the Set the new Qlik Sense app ID field, enter the new app ID

   (to find the new app ID, open the app in the 'alternate' or 'new' tenant hub and copy the app ID from the address bar

9. To change the tenant, enable the Change the Qlik Cloud tenant switch (disabled by default) and insert the new tenant address.

10. To save, click the Change Template Connection button
11. To use the changes, simply Click on the 'alternate', 'new' tenant MS Office Excel Addin again. This will re-log you in thus enabling the changes
12. Preview the report (select xlsx or pdf output format)

Environment

• Qlik Cloud 

Related Content

• Qlik Tabular Reporting General Troubleshooting and... - Qlik Community - 2160224
• Changing the connected Qlik Sense app

The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.

The Qlik Sense Hub connection times out faster / sooner than configured in the Virtual Proxy.

When working with an app in the hub, the connection to the app times out faster than configured in virtual proxy (for example, after 5 minutes), and the error message below is displayed:

Connection lost. Make sure that Qlik Sense is running properly. If your session has timed out due to inactivity, refresh to continue working.

This issue occurs when accessing Qlik Sense through a reverse proxy or load balance, but does not occur when accessing Qlik Sense on the same server (https://localhost/hub).
The user is also being active on the sheet, i.e. they are making selections etc. to interact with sheet objects.

Here is an example log line that may be seen in the AuditActivity_Proxy logs:

76 12.20.4.0 20200115T101930.708-0500 QLIKSERVER 8cd6aa7c-fab5-4e82-a2cd-0681943e7d58 Command=Close connection;Result=0;ResultText=Success d62cfb0a-3355-44a5-9e34-5eaada84be67 1ba723cc-e754-4e24-a42b-0732b24ad924 0 DOMAINNAME user.name 5c5e98cf-3f1f-45ed-96f0-8e76d7c44473 Not available Proxy AppAccess /app/5c5e98cf-3f1f-45ed-96f0-8e76d7c44473?reloaduri=https%3a%2f%2domain.com%2fsense%2fapp%2f5c5e98cf-3f1f-45ed-96f0-8e76d7c44473%2foverview Close connection 0 Backend web socket connection Closed for session 'd62cfb0a-3355-44a5-9e34-5eaada84be67'.

Environment:

• Qlik Sense Enterprise on Windows 
• Load balancer or Reverse Proxy in front of Qlik Sense

Resolution:

Qlik Sense should not terminate a session earlier than configured in the Virtual Proxy (default is 30 minutes), and when it does the error message would be different: 

Your session has timed out. Log back in to Qlik Sense to continue.

In this case, if the connection is being lost and it is occurring sooner than configured in the virtual proxy then this indicates that either:

1. The client is terminating the WebSocket connection prematurely, or
2. A network appliance acting on behalf of the client (load-balancer or reverse proxy) is terminating the WebSocket connection prematurely

Is WebSocket traffic possible?

Qlik Sense requires WebSockets. To verify WebSocket traffic, see Qlik Sense Websocket Connectivity Tester.

Enable TCP WebSocket Keep-Alive and HTTP keep-alive timeout.

Check to see if this issue occurs when using Internet Explorer. Internet Explorer by default adds additional unnecessary traffic to the WebSocket which can help in these situations. If you do not receive early timeouts when using IE, you can try Enabling TCP Keep Alive Functionality In Qlik Sense.

The HTTP keep-alive timeout may be increased here which helps in environments exhibiting the behavior mentioned above. See the Keep-alive timeout under the Proxy configuration. See Editing Proxies - Advanced > Keep-alive timeout (seconds)

If the above does not work, then you will need to make changes to your network infrastructure. Sniffing the network traffic to confirm things further can be performed. As sniffer, Wireshark can be installed on both Qlik Sense Proxy server and Hub client PC to run captures on both ends simultaneously. This may assist confirming the following:

1. Whether Qlik Sense is in fact receiving the TCP FIN packet, closing the TCP connection as expected.
2. Whether it was the client's PC or another network device who is sending the TCP FIN packet to terminate the session.
3. Whether the connection is becoming inactive and from which side (Sense / Client).

Qlik Support may assist in a best-effort basis with the above.  Please check out the video below for additional guidance. If further assistance is required correcting the environmental behavior, unfortunately the the task falls outside the scope of Qlik Support as this often is specific to the network involved. If further assistance is needed please reach out to your Account Owner to arrange Consulting Services (or see How to Contact the Consulting Team?)
 

Click here for video transcript

Cause:

Network appliances (e.g. Load balancers, reverse proxies, VPN solutions, firewalls, web accelerators, etc) may not see the websocket connection as an "alive" TCP connection, depending on the vendor, and therefore terminate the connection on behalf of the end-user.

The "Backend web socket connection Closed for session" string seen in the logs is registered when a WebSocket TCP layer connection is closed by the transmission of a TCP Packet containing the FIN flag set. This happens when either the browser window or tab is closed or when a network device in the environment drops the TCP connection sessions in a controlled fashion (sends the TCP FIN packet to the Sense server). This can also be sent by the client's computer if there is(are) any setting(s) preventing inactive TCP connections from staying open, as required by the Websocket protocol.

Windows Firewall blocking port 4747. Disable Firewall or apply all ports inbound and outbound

When working with Data Gateway - Direct Access, odbc drivers can have unexpected behaviors that can lead to crashes. 

Note: For more information about how to enable dump file creation and Isolation capability for Data Gateway - Direct Access, please review the links included in the "Related Content" at the end of this article. 

One known reason to cause crashes is the use of malformed SQL query statement.  

Resolution

After configuring the dump file generation and Process Isolation, dump files will be created under the folder configured during the setup. 

Once a crash occurs the file will include the process id associated to the reload:

dotnet.exe.XXXXX.dmp

Where XXXX will be the process id. 

With that process id and looking for the date and time when the file was created, in the odbc connector log, is possible to find the ProcessId associated to the Id of the dump file and get the reload ID.

Once the reload id was identified, from the QMC get the reload script associated to the reload id to verify the query that was triggered.

If the query is executed from a third party tool (outside of Qlik products) and doesn't work, the problem is a malformed SELECT statement. 

If the issue is not related to a malformed SELECT query, collect the dump file and contact Qlik Support for further analysis.

Cause 

Malformed SQL query statement.

Related Content 

Mitigating connector crashes during reload

How to collect dump files for the Qlik Data Gateway - Direct Access ODBC connector crashes.

Environment

• Data Gateway - Direct Access 

Qlik Sense allows for three settings that may influence the perceived connection and session timeout period. These are the "Session Inactivity Timeout", "Keep-Alive Timeout", and "TCP Websocket keep-alive"  settings. 

Note: Adjusting the below settings can help when working with slow internet connectivity or wanting to extend the session inactivity. However, session disconnect issues can be caused by other network connectivity issues and by system resource shortage as well and may require additional troubleshooting.  See Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly 

1.  The connection "Keep Alive" setting

This is the maximum timeout for a single HTTP request. The default value is 10 seconds. During the defined keep alive timeout value, the connection between end user and Qlik Sense will remain open.

It serves as protection against denial-of-service attacks. That is, if an ongoing request exceeds this period, Qlik Sense proxy will close the connection.

Increase this value if your users work over slow connections and experience closed connections for which no other workaround has been found. Make sure to take the mentioned DoS consideration above into account. 


 

2.  The "Session Inactivity Timeout"

This is the browser authentication session time out ( 30 minutes by default set under Virtual Proxy in QMC ). This sets a cookie on the client machine with the name X-Qlik-Session. This cookie can be traced in Fiddler or Developer tools under the  header tab. 

If the session cookie header value does not get passed, is destroyed, or modified between the end user client and the Qlik Sense server while 'in-flight' the user session is terminated and the user is logged out.

By default, it will be destroyed after 30 minutes of inactivity or when the browser is closed.

3. TCP Websocket keep-alive

This is another setting that may help keep the connection open in certain environments. See Enabling TCP Keep Alive Functionality In Qlik Sense. Note that customers who don't experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it may potentially cause Qlik Sense to send unnecessary traffic on the network towards the client.

Related Content:

• Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly 

Environment:

• Qlik Sense Enterprise on Windows, all versions

Opening an application to visualize charts through the hub, the visualization may fail and the error "Out of calculation memory" will be printed.

Environment:

• Qlik Sense Enterprise on Windows, all versions

Resolution

The issue is often related to having an app that is too large or requires a re-design or general optimization. A poorly designed application can lead to memory leaks.

Application optimization

Review the application and optimize as needed to prevent performance problems for the engine service.  

Verify resource availability

Verify that the servers hosting the Qlik Sense engine service have sufficient resources (CPU / Memory) to proceed with the calculation. It is highly recommended to have at least 16 cores and 64 GB of memory.

Modify the Hypercube memory limit 

You can otherwise change the timeout.

• Open the Qlik Sense Management Console. Default: https://<QPS server name>/qmc.
• Open Engines for each node
• Select the Engine to modify and click Modify 
• Open the Advanced menu in menu to the right
• Modify the Hypercube memory limits (bytes). This is by default set to 0, which allows the engine to apply a global heuristic ensuring that we do not run more than 1 big calculation in parallel. Setting this value to -1 will disable the limit. 
• Restart the Qlik Sense Engine and Qlik Sense Service Dispatcher on all nodes after the setting was changed. 

Cause:

The "Hypercube memory limits" limits how much memory a hypercube evaluation can allocate during a request. If multiple hypercubes are calculated during the request, the limit is applied to each hypercube calculation separately.

If it sets to 0, the engine applies a global heuristic which basically ensures that it doesn't run more than 1 "big" calculation in parallel. 
If you set this value to -1 then you will disable the limit and allow the Engine to keep trying to load the application.

The negative value disables the limit, but it wouldn't exceed the limit set under the Max memory usage (%) or Memory usage mode.

Related Content:

Qlik Sense: "Calculation timed out" while loading a chart into an application

This article explains how to import and export master items to and from a Qlik Sense app using the Microsoft Excel connector in Qlik Application Automation.

Content:

• Export master items to a Microsoft Excel sheet
• Import master items from a Microsoft Excel sheet
• Edge cases & next steps

The first part of this article will explain how to export all of your master items configured in your Qlik Sense App to a Microsoft Excel sheet. The second part will explain how to import those master items from the Microsoft Excel sheet back to a Qlik Sense App.

Export master items to a Microsoft Excel sheet

For this, you will need a Qlik Sense app in your tenant that contains measures, dimensions, and variables you want to export. You'll also need an empty Microsoft Excel file. The image below contains a basic example on exporting master items.

The following steps will guide you through recreating the above automation:

1. Add the Create Workbook Session block from the Microsoft Excel connector. Configure it with the following settings:
   1. Drive id -> use do lookup 
   2. Item id -> use do lookup to find the empty destination file, if you don't know the path of your file, you can do an empty search (if it isn't located in a folder)
      
      

       

2. Add the Add Worksheet block from the Microsoft Excel connector. Use the same Drive Id & Item Id from the previous step and configure the Name parameter to a string of your choice. In this example, we'll use Measures.
   
   

    

3. Add the Create Excel Table With Headers block from the Microsoft Excel connector. This block will create a table inside the sheet from the previous step. Specify the following in the block's configuration:
   1. Start Row -> 1
   2. Start Column -> A
   3. End Column -> E
   4. Headers -> Field,Name,Label Expression,Description,Tags,Measure Color, Segment Color, Number Format
   5. Name -> Measures
4. Add a List Measures block from the Qlik Cloud Services connector and also a Get Measure block inside the loop created by the List Measures block, configure it to get the current item in the loop. Add two variables to convert Gradient and NumFormat JSON objects to string.
   
   

    

5. Add an Add Row To Table block from the Microsoft Excel connector inside the loop after the Get Measure block. This will add every measure's information to the table one by one. Set the Drive Id, Item Id, Worksheet, and Table Id to the corresponding values from the previous blocks.
   The Row parameter should be an array of values for every header we specified in the Create Excel Table With Headers block (and in the same order). Title, Label expression, and Description should be encapsulated in double-quotes. Apply the JSON encode formula to the value for the Definition (qDef) and apply the Implode formula to the value for the Tags. 
   
   

    

6. Add a Close Workbook  Session block from the Microsoft Excel connector. Specify the same Drive Id & Item Id as in the previous blocks and configure the Session Id to the Id returned by the Create Workbook Session block.

An export of the above automation can be found at the end of this article as Export master items to a Microsoft Excel sheet.json

Import master items from a Microsoft Excel sheet

For this example, you'll first need a Microsoft Excel file with sheets configured for each master item type (dimensions, measures, and variables). Use the above example to generate this file. The image below contains a basic example on importing master items from Microsoft Excel to a Qlik Sense app.

1. Add the List Rows With Headers block from the Microsoft Excel connector to read master items from the Excel file. Configure the block with the following settings:
   1. Drive Id -> use do lookup
   2. Item Id -> use do lookup to find the empty destination file, if you don't know the path of your file, you can do an empty search (if it isn't located in a folder)
   3. Worksheet Name -> the name of the sheet that contains the measures. Feel free to use do lookup
   4. Start Cell -> the upper-left cell of the measures table, this should include the header row, for example, A1
   5. End Cell -> the bottom right cell of the measures table, for example, E23
      
      
      
      
2. Add a Condition block inside the loop created by the List Rows With Headers block. The condition will verify that every measure row has the required information to create a measure (name and expression).
   
   See the below image for an example:
   
   

    

3. Add the Create Or Update Measure block from the Qlik Cloud Services connector to create or update the measure in the destination app. Map each field from the row in the Excel table to the corresponding input field in the Create Or Update Measure block. Measure Id can be left empty since we're matching measures by Name (Measure Ids can be different across apps). See the below image for an example:
   
   

An export of the above automation can be found at the end of this article as Import master items from a Microsoft Excel Sheet.json

Follow the same steps to build automations that import/export dimensions and variables.

Edge cases & next steps

Let's go over some edge cases when exporting information to Microsoft Excel:

• Fields that start with an equals-sign '=' (for example, some variables' definitions) are treated as Excel functions and can be deemed invalid by the Excel API. You can resolve this by adding a single quote before the input field's mapping in the automation. 
  
  
  
  
• Fields that contain newlines (for example measure expressions that contain comments) are invalidated by the Excel API. The solution here is to use the JSON formula to encode the string.
  
  

   

Please check the following articles for more information about working with master items in Qlik Application Automation and also uploading data to Microsoft Excel.

• How to get started with Microsoft Excel
• Distribution of Master items using Qlik Application Automation
• Uploading data to Microsoft Excel

Follow the steps provided in this article How to import & export automations to import the automation from the shared JSON file.

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.

This article describes how to resolve the NPrinting connection verification error:

x Qlik NPrinting webrenderer can reach Qlik Sense hub error

Environment

• NPrinting: all versions
• Qlik Sense: all versions
  • multi-node QS proxy environment
  • NLB (Network Load Balancer or Alias URL) server address used in front of cluster of Qlik Sense proxy nodes (which are linked to a Virtual Proxy. Proxy nodes will not work with NPrinting unless they are linked to a QS virtual proxy)

Resolution

• Although it is possible to use an NLB address in front of your QS proxy nodes that are used by NPrinting, the error generated in the NP connection verification process will appear as described in the article title
• This error can safely be ignored as this does not affect generation of NPrinting connections
• To eliminate the 'error' message, you would need to update your NPrinting connection to use a virtual proxy node address/computer name behind the NLB address . It must be the computer name and not an alias url).
• The proxy node used must be linked to a virtual proxy with the following required attribute
  
  • Microsoft Windows NTML authentication on the Qlik Sense proxy. (SAML and JWT are not supported. If your virtual proxy uses SAML or JWT authentication, you need to add a new virtual proxy with NTLM enabled for Qlik NPrinting connections).
  • A link between the proxy node and virtual proxy.
  • For all NPrinting to Qlik Sense requirements visit https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#anchor-1

Related Content

• https://help.qlik.com/en-US/nprinting/Content/NPrinting/Troubleshooting/Verify-connection-to-Sense-errors.htm
• https://help.qlik.com/en-US/nprinting/Content/NPrinting/DeployingQVNprinting/NPrinting-with-Sense.htm#Requirem

Internal Investigation ID

• QB-2871

Qlik Sense URL(s) tested on SSLlabs (ssllabs.com) return the following weak Cipher suites:

TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x39) DH 1024 bits FS WEAK TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x33) DH 1024 bits FS WEAK
TLS_RSA_WITH_3DES_EDE_CBC_SHA (0xa) WEAK

The steps documented in this article are an example of how cipher suites can be disabled. All steps are to be performed by a Windows Administrator on Windows level and cannot be supported by Qlik Support. 

We recommend to consulting with your security or Windows administrator before proceeding as they may have automated practices in place. 

The security in Qlik Sense does not depend only on the Qlik Sense software. It also relies on the security of the environment that Qlik Sense operates in. This means that the security of, for example, the operating system and the cryptographic protocols (such as TLS/SSL) has to be set up and configured to provide the security needed for Qlik Sense. See Protecting the platform.

Configuring TLS Cipher Suite Order

You can review and configure the cipher suites order using a Group Policy. See Manage Transport Layer Security (TLS) | Microsoft Learn.

Please refer to fig 1:

Fig 1

This policy determines the cipher suites used by the Secure Socket Layer (SSL). If you enable the policy setting, SSL cipher suites are prioritized in the order specified.

If you disable or do not configure this policy setting, the factory default cipher suite order is used.

SSL2, SSL3, TLS 1.0 and TLS 1.1 cipher suites:

TLS_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_RC4_128_SHA TLS_RSA_WITH_3DES_EDE_CBC_SHA TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA TLS_RSA_WITH_RC4_128_MD5 SSL_CK_RC4_128_WITH_MD5 SSL_CK_DES_192_EDE3_CBC_WITH_MD5 TLS_RSA_WITH_NULL_SHA TLS_RSA_WITH_NULL_MD5

TLS 1.2 SHA256 and SHA384 cipher suites:

TLS_RSA_WITH_AES_128_CBC_SHA256 TLS_RSA_WITH_AES_256_CBC_SHA256 TLS_RSA_WITH_AES_128_GCM_SHA256 TLS_RSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P521 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384_P521 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_RSA_WITH_NULL_SHA256 TLS 1.2 ECC GCM cipher suites: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P256 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256_P521 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P384 TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384_P521

How to modify this setting:

1. Open a blank notepad document.
2. Copy and paste the list of available suites into it.
3. Arrange the suites in the correct order; remove any suites you don't want to use.
4. Place a comma at the end of every suite name except the last. Make sure there are NO embedded spaces.
5. Remove all the line breaks so that the cipher suite names are on a single, long line.
6. Copy the cipher-suite line to the clipboard, then paste it into the edit box. The maximum length is 1023 characters.

Related Content:

Configuring preferred cipher suites for Qlik License Service in Qlik Sense Enterprise on Windows

Environment:

Qlik Sense Enterprise on Windows any version

Note: This application only returns a limited subset of usage information. Qlik is in the process of developing a new "Automation Analyzer" application for the Qlik Cloud Monitoring Application suite, which will replace this app.

This article shows how to use the example Qlik Application Automation Monitoring App. It explains how to set up the load script and how to use the app for monitoring Qlik Application Automation usage statistics for a cloud tenant. 

Index:

• How to configure the load script
• Qlik Application Automation Monitoring app content
• Loading data
• Limitations

The app included is an example and not an official app.  The app is provided as-is.

How to configure the load script

There are four steps for the configuration of the load script:

1. Configure your tenant here by typing the name of your tenant and region here: 
   
   
   
   
2. Configure your data connection by typing the name of an existing data connection. The data connection must be configured in the pane to the right, see picture. If you do not have one, you must create one.
   
   
   
   
3. Configure your data folder location here:
   
   
   
   
4. Configure your time zone here, using deviation from GMT, for example, Central European time +1: 
   
   
   
   

Qlik Application Automation Monitoring app content

The monitoring app includes four sheets that present various information on the Qlik Application Automation usage in the current tenant.

Automations

Filtering is available based on Automation Name, Last Run Status, Run Mode, State & Status.

•  # Runs last 30 days
• Automation runs last week
• Automations in tenant
• Automations utilized last 30 days
• Average # of runs
• Average runs per day
• Successful runs last 30 days
• Successful runs last week

Failed vs successful automation runs

• # Runs total
• Average runs per day
• Days of data
• Failed runs
• Number of failed runs per automation
• Number of runs last 30 days per user
• Percentage failed
• Runs per automation
• Successful runs

Automation run history last 30 days and weekly respectively

• Number of runs last 30 days
• Number of runs per month

Total hourly distribution

• Hourly distribution last 30 days
• Total automation runtime last 30 days

Loading data

The Qlik Application Automation Monitoring app facilitates incremental load, that is, only added data is loaded into the app. 

Important: Qlik Application Automation runs are only stored for 30 days. When data is loaded into the app for the first time, only 30 days of history is loaded, thus only 30 days of history will be available in the app. After this initial data load, data older than 30 days will be available in the app thanks to the incremental data load. If data is loaded at least once every 30 days, continuous data will be available in the app. 

Limitations

1. At the initial load, only 30 days of history are loaded. This is because Qlik Application Automation history is only stored for 30 days. 
2. For continuous data in the app, data must be loaded at least every 30 days. 
3. The API can only return the last 5000 runs for every automation. Please keep this in mind when scheduling the reloads of this app. 

Environment

Qlik Cloud 
Qlik Application Automation 

The information in this article is provided as-is and is to be used at your 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.

Upgrading Qlik Sense running a standalone/remote PostgreSQL Database or a PostgreSQL Database upgraded with the Qlik PostgreSQL Installer fails with the following error:

Setup Requirements

The following information has been collected from your system:

This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities. Ensure that you have created a 'SenseService' database in your cluster before upgrading. For more information see Installing and configuring PostgreSQL. 

Resolution

1. Verify that the database is started.
   
   For stand-alone PostgreSQL installations, the database needs to run for the installer to be able to verify its requirements. 
   
   The requirement extends to Qlik Sense systems in which the PostgreSQL database has been upgraded with the Qlik PostgreSQL Installer.
   
   
2. Verify that all required databases are created before the upgrade. 
   
   See your version of Qlik Sense to verify what databases are required: Databases.
   
   For detailed instructions on how to install and configure PostgreSQL, see: Installing and Configuring PostgreSQL 
   
   For an example of the above with the Licenses database, see This version of Qlik Sense requires a 'Licenses' database for license capabilities. Ensure that you have created a 'Licenses' database in your cluster before upgrading. Is displayed when trying to upgrade Qlik Sense
   
   
3. Is traffic encryption enabled?
   
   Looking at the Connection String using the Qlik Sense Utility tool (stored under C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil) verify if the parameter Ssl Mode=Require is included.
   
   The Qlik Sense installer cannot use SSL encryption for establishing connection to PostgreSQL. When SSL encryption is enabled, the installer does not recognize any already installed PostgreSQL databases, and as a consequence, installation cannot be completed.
   
   Workaround: Temporarily disable traffic encryption for the connection to the Qlik Sense database(s) prior to upgrading Qlik Sense Enterprise. See Qlik Sense - Setting up database traffic encryption 
   
   Reference: Database traffic encryption
   
   
4. Is FIPS enabled?
   
   The next most common scenario is that the server which Qlik Sense is installed is configured to enforce FIPS policy. Due to a dependency in the install, additional steps are needed to allow the installer to operate in a FIPS environment. Reference article Unable to install Qlik Sense to a remote PostgreSQL database with FIPS enabled for more details on the resolution for this variant of blockers.
   
   
5. Incorrect Database ownership
   
   A previous upgrade failure or inconsistency can cause the QMSQ database ownership to be incorrect. Since the Qlik Sense installer tries to validate the connection to all underlying databases, a failure to do so against any of them will result in a failure to upgrade.
   
   For instructions on how to resolve this issue, see Qlik Sense Upgrade fails: Initializing 'QSMQ' database.