Troubleshooting - Managing QMC resources
This section describes problems that can occur when managing QMC resources.
Error message: 400 Bad request
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.
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:
SSL/TLS communication problems after you install KB 931125
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
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
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
Do the following:
-
Type an arbitrary name as the attribute name.
-
Make an authentication attempt.
The attempt will fail because the attribute name is incorrect.
-
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.
-
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='john.davidson@domain.com']
Reload is not working
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.
A task is not executed
Possible cause
The task status is not Success.
Proposed action
On the tasks overview page in the QMC, click 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.
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.
See: 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.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 no value.
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
Do the following:
-
Delete the node in the QMC.
-
Uninstall the software from the node.
-
Reinstall the software on the node.
-
Create the node again in the QMC.
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.
-
Edit the extension so that it is not a duplicate.
See: Extension names
I cannot migrate an app
I cannot migrate an app despite several attempts.
Possible cause
The app is corrupted.
Proposed action
Check the app migration log files for information that could explain the failure. The log files are available at this location: %ProgramData%\Qlik\Sense\Log\.
I want to change the default user account
I want to change the default Windows user account, that is used to run Qlik Sense.
Proposed action
Modify the Qlik Sense installation.
Do the following:
- Open the Control Panel and select Uninstall a program.
-
Select Qlik Sense from the list of programs and click Change.
-
Select Modify in the Qlik Sense setup dialog.
The Windows user account can also be changed manually. This is done by modifying the user account that is used to run the Qlik Sense services and the user account that is used to access the folder where the Qlik Sense logs are stored. The default path to the Qlik Sense log folder is %ProgramData%\Qlik\Sense\Log\<Service>.
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!