Skip to main content Skip to complementary content

Troubleshooting - Managing QMC resources

This section describes problems that can occur when managing QMC resources.

Error message: 400 Bad Request

There is more than one possible cause when the error message 400 Bad Request is displayed.

Importing an app in the QMC fails

The logs show an error message: Server:ImportApp_impl caught extended exception 400: Bad Request

Possible cause  

The app contains a web connection that makes the URL exceed 1024 characters.

Proposed action  

  1. Open the app in Qlik Sense Desktop to see if the app contains a web connection that makes the URL longer than 1024 characters.
  2. Use a service such as to shorten the URL.

The REST HTTP request incorrect

Possible cause  

The REST HTTP request to the proxy or the repository is incorrectly formatted.

Proposed action  

Correct the formatting of the REST HTTP request.

Information noteA complete request must contain ?XrfKey=<minimum 16 characters> in the URL, and also, in the same request, include the header X-Qlik-XrfKey with exactly the same string as a value (to resist cross-site scripting attacks).

Error message: 401 Unauthorized

Authentication of the connector fails when the password contains special characters.

Possible cause  

While in the QMC, you have edited the connector password and added one or more of the following special characters:

  • %

  • =

  • ;

Proposed action  

Use the data load editor to edit the password.

Error message: 403 Forbidden

Possible cause  

  • There are too many root certificates on the computer (> ~300), and as a consequence, the Qlik Sense services are not allowed to communicate.
  • You are trying to access a resource that you are not granted access to, according to the rule engine in the repository.

Proposed action  

Remove any unused root certificates. See also the following Microsoft help documentation:

Error message: 405 Method not allowed

Possible cause  

The URL refers to a non-existent REST function.

Proposed action  

Modify the URL.

Error message: Internal server error 500

There is more than one possible cause when you get error 500.

App import was unsuccessful

Possible cause  

You have attempted to import an app with a name longer than 2500 characters.

Proposed action  

Reduce the app name to maximum 2500 characters.

Unidentified error

Possible cause  

An unidentified error has occurred.

Proposed action  

Check the system log files at the following locations:

  • %ProgramData%\Qlik\Sense\Log\Proxy
  • %ProgramData%\Qlik\Sense\Log\Repository
Information noteIf the error message is displayed repeatedly, please contact your Qlik Sense representative and provide the system log files.

Error message: Connection lost is displayed when I try to connect to the Qlik Sense hub

Possible cause  

The address being used when accessing the Qlik Sense hub is not present in the host allowlist in the Qlik Sense Proxy Service.

The Connection lost error message commonly occurs in the following cases:

  • The Qlik Sense hub is accessed using the IP address, for example,, instead of the host name, https://myhost/hub, or the fully qualified name (FQN),
  • The Qlik Sense hub is accessed using a different address than the one registered as the default Domain Name System (DNS) name or FQN of the machine. As an example, when using Amazon Web Services, or similar environments, the internally registered DNS name is not the same as the externally facing address.

Proposed action  

  1. From the QMC, open Virtual proxies.

  2. Select the virtual proxy and click Edit.

  3. In the Properties list, select Advanced.

  4. Locate Host allow list.

  5. Click Add new value and add the address used to connect to the Qlik Sense hub from a client.

    IP address:, FQN:

  6. Click Apply.

    A proxy restart message is displayed.

  7. Click OK.
Information noteAn entire domain can be added the allowlist by adding This will add all other addresses within that domain to the allowlist, such as,, and so on.

Error message: ODBC connection failed

A scheduled reload failed with the error message ODBC connection failed.

Possible cause  

The data connection uses single sign-on (SSO), which requires that the connection is used by an actual user, and the app uses "SQL SELECT…" to load data.

There is more than one possible solution to this problem:

Proposed action (change data connection not to use SSO)

Specify which user name and password that should be used.

Proposed action (perform the reload manually)

If you do not want to make any changes to the data connection, you can perform manual reloads, instead of using a task.

Proposed action (change from SQL to Direct Discovery tables)

When you use SSO together with Direct Discovery tables, you will be able to reload the app with a task.

User locked out when a REST data connection is used with a user account

Possible cause  

If you set up your REST data connections with a regular user account and not a service account available in your AD/LDAP/user directory, the maximum number of parallel sessions for a single user account (5) will be consumed, and the user will be temporarily locked out.

Proposed action  

Use a service account instead of a user account, and do not allocate any user/professional/analyzer access to that account.

A task is not executed

Possible cause  

The task status is not Success.

Proposed action  

On the tasks overview page in the QMC, click Info in the status column to display a summary of the execution steps.

You can also check the log file at this location: %ProgramData%\Qlik\Sense\Log\Scheduler.

Reload is not working

There is more than one possible cause when the reload does not work.

Reload was unsuccessful

I clicked Reload now on an app but the reload is not working.

Possible cause  

The task status is not Success.

Proposed action  

Check the log file at this location: %ProgramData%\Qlik\Sense\Log\Script.

Reload failed in a multi-node environment

In a multi-node environment, I selected an app and clicked More actions > Reload now, but the reload failed with the following message: No worker-nodes found to execute Task.

Possible cause  

The Central scheduler is set to Manager only.

Proposed action  

Re-trigger the task execution.

On the Edit scheduler page, under Advanced, change Type to Manager and worker.

The start page displays a number next to Engine, Repository, Proxy, or Scheduler

Possible cause  

The service is down.

Proposed action  

Check the log file at this location: %ProgramData%\Qlik\Sense\Log\<Service>.

I do not know the name of a mandatory SAML attribute

Possible cause  

The name of a mandatory attribute, (userID, userDirectory, or an added mandatory attribute) is not available.

Proposed action  

  1. Type an arbitrary name as the attribute name.

  2. Make an authentication attempt.

    The attempt will fail because the attribute name is incorrect.

  3. In the Proxy Audit log, find the row that contains "Existing SAML attributes:".

    You will find the name or friendlyName and Value of all available attributes.

  4. Find the name of attribute that you want to use and use that name instead of the arbitrary name that you originally entered.

The following are examples of what you can find in the log:

Existing SAML attributes: [Name='uid', Value='jod'] [Name='givenName', Value='John'] [Name='sn', Value='Davidson'] [Name='cn', Value='John Davidson'] [Name='mail', Value='']

I cannot change the properties of a user

Possible cause  

User properties imported from Active Directory (AD) cannot be changed in the QMC.

Proposed action  

Change the property in AD and sync again.

Synchronizing with user directories

The user sync is not working

  • I cannot synchronize users when clicking Sync all selected user directories in the User directory connectors overview.
  • A scheduled user synchronization task is unsuccessful.

The UDC is not configured

Possible cause  

The user directory connector is not Configured.

Proposed action  

Make sure that the User directory name is unique and not blank.

The UDC is not operational

Possible cause  

The user directory connector is not Operational.

Proposed action  

Check the UserManagement_Repository log at this location: %ProgramData%\Qlik\Sense\Log\Repository\Trace. If you remove the source file that a user directory connector is based on, it will not be operational.

The UDC property Page size of search value is incorrect

Possible cause  

The user directory connector property Page size of search is incorrect.

Proposed action  

Set the user directory connector property Page size of search to '0' (zero).

Table names with capital letters are not recognized in a PostgreSQL database

Possible cause  

Table names with capital letters or special characters, such as "." in a PostgreSQL database will generate an error when validated.

Proposed action  

Use quotation marks for tables containing capital letters or special characters.


"table.Name", public."Table" (or "Table"), testschema."Table"

I cannot import an extension

Possible cause  

  • The extension is not zipped.
  • The compressed file has the wrong format.
  • The zip file contains invalid files.
  • The extension password is incorrect.
  • The extension is a duplicate of an already existing extension.

Proposed action  

  • Make sure the extension file is correctly zipped. You cannot use any other file format for compression than .zip.

  • Make sure that the zip file only contains relevant extension files.

  • Warning noteIf you import an extension that already exists in QMC, when prompted, replace the existing file with the new one by clicking Replace, or click Cancel to cancel.
    Extension names

I have deleted a .lock file and can no longer open my app

Possible cause  

Each app in the ...\Sense\Apps folder has a .lock file, and if that file is deleted, the app cannot be opened.

Proposed action  

Restart the Qlik Sense Repository Service. A new .lock file is generated for the app.

Information noteThe lock files are used for coordinating the locking of the qvf files. A thread that wants to read from a qvf file must wait until the thread that is writing (and holds the exclusive lock) has finished. Similarly, if a thread wants to have an exclusive lock, it must wait until the threads that are reading from the file are finished.

A node in a multi-node environment is not getting online

I have recreated a node in the QMC (created, deleted, and then created it again) but the node is not getting online. There is a warning message in the log: “Node disabled (most probable cause is having been unregistered from a cluster). Aborting startup...”.

Possible cause  

Deleted nodes are not allowed to be restarted and reused in a multi-node environment.

Proposed action  

  1. Delete the node in the QMC.

  2. Uninstall the software from the node.

    Uninstalling Qlik Sense

  3. Reinstall the software on the node.

  4. Create the node again in the QMC.

Multi-node site: Cannot communicate with a rim node that is outside of the domain

Possible cause  

Normally, all nodes in a Qlik Sense multi-node site are within the same Windows domain. If one of the rim nodes is outside of the domain with no DNS available for hostname lookup, the nodes within the domain cannot communicate with the node outside the domain unless the Windows host file on each node is updated.

Proposed action  

Do the following:

  • All nodes within the domain: Update the Windows host file (typically C:\Windows\System32\drivers\etc\hosts) with information on how to find the rim node outside the domain.
  • Example: <IP address of the rim node outside the domain> <hostname of the rim node>

  • Rim node outside the domain:
    • Update the Windows host file with information on how to find all the nodes within the domain.
    • Example:  

      <IP address of node 1 within the domain> <fully qualified domain name of node 1>

      <IP address of node 2 within the domain> <fully qualified domain name of node 2>

    • Update the Windows host file with information on the host name of the rim node itself so that the Qlik Sense services on the rim node can communicate with each other.
    • Example: <IP address of the rim node outside the domain> <hostname of the rim node>


Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!