Troubleshooting

 

Troubleshooting mashups

This section describes problems that can occur when creating mashups for Qlik Sense, as well as suggestion for resolving them.

Mashup is empty in Qlik Sense environment

Your mashup is empty when you try to access it in a server environment.

Scenario 1

Possible cause  

The Qlik Sense app does not exist or the app ID is incorrectly referenced in the mashup.

Proposed action  

Add the app to the repository or update the mashup's reference to the app ID.

Scenario 2

Possible cause  

Your environment is set up with a virtual proxy and the prefix has not been added to your mashup files.

Proposed action  

Make sure the host, including the prefix, is included in the three link references in the HTML file. Also, make sure you adjust the HTML configuration in the JavaScript file.

Mashup is empty after copying to Extensions folder

After having copied a mashup to the Extensions folder it do not render, the mashup is empty.

This problem can only occur on Qlik Sense Desktop.

Possible cause  

The Qlik Associative Engine has not been refreshed since copying the mashup to the Extensions folder and therefore, the mashup is not yet available.

Proposed action  

  1. Re-start the Qlik Associative Engine.
  2. Close Qlik Sense Desktop.
  3. Launch Qlik Sense Desktop again.

Create new button is unavailable

The Create new button in Dev Hub is unavailable and therefore, no new extensions or mashups can be created from Dev Hub.

Possible cause  

You may not have sufficient privileges to create extensions and mashups.

Proposed action  

Add the correct privileges by creating a security rule in Qlik Management Console.

  1. Open Qlik Management Console.
  2. Select Security rules on the QMC start page or from the StartS drop-down menu to display the overview.

  3. Click PCreate new in the action bar.

    This opens the Security rule edit page.

  4. In the Identification view, select Extension access rule from the Create from template drop-down list.

  5. In the Basic section, select the Create, Read, Update, and Delete check-boxes as applicable.

    Then, select a user condition that specifies which users the rule will apply to.

  6. In the Identification view, give the security rule a name in the Name text box.
  7. Click Apply in the action bar to create and save the rule, or click Cancel to discard changes.

    Successfully added is displayed at the bottom of the page.

WebSocket limit reached

Mashups containing more than six iframes generate several error messages on the page when using Microsoft Internet Explorer.

Possible cause  

Microsoft Internet Explorer supports a maximum of six WebSocket connections. Because each iframe is considered as a new WebSocket connection, even when it is calling objects from the same Qlik Sense app, this limitation will apply for mashups containing more than six iframes.

Proposed action  

  • Use div integration (using Capability APIs) instead of iframe integration (using Single integration) and make sure not to call objects from more than six different Qlik Sense apps.
  • Modify the number of server connections allowed, see http://msdn.microsoft.com.

    This proposed action is only applicable if you are working in a controlled environment, for example an Intranet.

Extension does not work in a mashup on an external web server

An extension used in a mashup hosted on a web server that is different from the one on which Qlik Sense is running.

Possible cause  

The extension is trying to avoid cross-scripting issues by using JSONP.

Example:  

The file in the extension is "styles.css", which will work in a non-cross-site scenario. In a cross-site scenario, RequireJS will look for a "style.css.js" file instead, which typically is not available.

Proposed action  

If you have access to the QMC and can update the extension, wrap the file inside a corresponding js-file. The format required by RequireJS is:

define([], function () { return "the text from the original file";});

You must re-install the extension, just putting the file in the folder will not work.

Troubleshooting visualization extensions

This section describes problems that can occur when creating extensions for Qlik Sense, as well as suggestion for resolving them.

I cannot export my visualization extension

I tried to export data from my visualization extension but it is not possible.

Possible cause  

Export functionality has not been enabled for the visualization extension.

Qlik Sense did not support exporting or printing of visualization extensions before version 3.0.

Proposed action  

Enable export functionality for your visualization extension.

Enabling export of your visualization extension

I cannot export data

I have enabled the exportData setting for my visualization extension but I still cannot see the export data alternative in the context menu.

Possible cause  

You may not have permission to export the object.

Proposed action  

Change the access rights in the Qlik Management Console (QMC).

My visualization extension exports incorrectly

My visualization extension works in the client but it exports incorrectly.

Possible cause  

You may have used an undocumented Asynchronous Module Definition (AMD) or you may have used external resources from the internet (for example JavaScript files or images).

Proposed action  

Do not use internal requireJS modules in the visualization extension.

My visualization extension is not rendering

My visualization extension is not rendering in the client.

Possible cause  

Since Qlik Sense June 2018, the client is only exposing a limited set of AMD modules. The list includes, but is not limited to:

  • jQuery
  • angular
  • qvangular
  • underscore
  • enigma

Proposed action  

Extensions using non-exposed modules will not render and an error message is logged in the console. The code of the extension should be updated and should not use the non-exposed module.

Troubleshooting Dev Hub

This section describes problems that can occur when using Dev Hub, as well as suggestions for resolving them.

I cannot create extensions, mashups, or widgets in Dev Hub

I wanted to create an extension, mashup, or widget using Dev Hub but the options for creating were unavailable.

Possible cause  

You do not have sufficient access rights to create content in Dev Hub.

Proposed action  

Contact your system administrator to get sufficient access rights.

Access rights and Dev Hub

I cannot access Dev Hub

I opened Dev Hub but there is no content. Browser network traffic shows a 401 error.

Possible cause  

Qlik Sense site is not listed as a trusted site.

Proposed action  

Add the FQDN (Fully Qualified Domain Name) of the host to the trusted sites.

  1. In Internet Explorer, open Tools > Internet options.
  2. Select the Security tab.
  3. Click on Trusted sites.
  4. Click on Sites.
  5. Click Add.
  6. Enter the FQDN of the host in the text field and click Add.
  7. Click Close
  8. Click OK.
  9. Refresh the browser window.

I cannot access Dev Hub from the host machine

I am trying to access the Dev Hub from the same machine that hosts the Qlik Sense site, but I receive a 401.1 Access Denied error from the browser.

Possible cause  

Loopback security settings in Windows Server may prevent access using a fully qualified domain name (FQDN), from the same machine that hosts the Qlik Sense site.

Proposed action  

Access the Dev Hub using a localhost address: https://localhost/dev-hub.

It is also possible to disable loop checking. For more infomation about this, refer to Microsoft support knowledge base article.

I cannot convert assets with QlikView converter

I am trying to convert a QlikView document using the QlikView converter but creation of a new QlikView converter project fails.

Possible cause  

The data in the QlikView document cannot be read into Qlik Sense.

Proposed action  

  1. Open the QlikView document with no data, save it and then import it to QlikView converter.

    To open the QlikView document with no data, open a Command Prompt window and execute the following command:

    C:\Program Files\QlikView\qv.exe /nodata C:\<MyFolder>\<MyDoc>.qvw

    where C:\Program Files\ is your installation location.

  2. Save the document.

  3. Import the document into QlikView converter.

Troubleshooting .NET SDK

This section describes problems that can occur when connecting to the Qlik Sense .NET SDK, as well as suggestion for resolving them.

Troubleshooting connection

Scenario 1

You can not connect to Qlik Sense.

Possible cause  

  • The Qlik Sense installation is improperly.
  • The WebSocket origin white list is not configured.
  • Windows authentication patterns is not configured for Windows.
  • The QMC is not configured with static header.
  • The URI entered during the installation of Qlik Sense does not match the location specified.

  • The credentials entered during the installation of Qlik Sense is not the user making the connection.

Proposed action for Qlik Sense Server

Choose one of the following solutions:

  • Open a browser and navigate to https://server.domain.com. If you do not get the hub on page check your installation.
  • Configure the WebSocket origin white list in the QMC.

    Websocket origin white list is configured

  • Configure Windows authentication patterns by adding Http in the QMC.
  • Configure the static header in the QMC.

    Static header

Proposed action for Qlik Sense Desktop

Verify your Qlik Sense installation by opening a browser and navigate to http://127.0.0.1:4848. The hub should be visualized on page, if not, choose one of the following solutions:

  • Change the location specification to ILocation location = Qlik.Engine.Location.FromUri(new Uri("http://localhost:4848"));

  • Check if the firewall settings are correct for the port numbers.
  • Make sure no IIS (or anything else) is running on default port 80 or 443, since this will conflict with Qlik Sense. In order to run http this has to be enabled in the proxy, through the QMC. Https is the default setting.
  • Check that your local host name or domain wild card is added to the WebSocket origin white list in the remote QMC.

    Websocket origin white list is configured

Open a browser and navigate to http://127.0.0.1:4848. If you still do not get the hub on page reinstall Qlik Sense.

Scenario 2

Exception message contains the following, The remote certificate is invalid according to the validation procedure.

Possible cause  

There is a problem with the website’s security certificate.

Proposed action  

Choose one of the following solutions:

  • Reinstall the Qlik Sense server so that you get a correct certificate.

  • Use a valid certificate.

    Export certificate

  • Install the certificate on your local machine.

  • For testing purpose, set ignore certificate: false to true. Supported from Qlik Sense .NET SDK Version 3.0.

  • Run without encryption by allowing http.

    Set Allow http in the QMC

Scenario 3

Could not connect using non-encrypted authentication. Exception message, Connection failed after 4 attempts. Unable to keep connection open: Failed to ensure open connection: One or more errors occurred.

Possible cause  

Http is not set in the QMC.

Proposed action