Qlik Community

Ask a Question

Knowledge

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Our next Qlik Insider session will cover new key capabilities. Join us August 11th REGISTER TODAY

Cannot open QMC or Hub "InternalServerError" and "Could not connect to the license service"

Benoit_C
Support
Support

Cannot open QMC or Hub "InternalServerError" and "Could not connect to the license service"

After a migration, Qlik Sense, may not be accessible. The Qlik Sense Management Console (QMC) and/or HUB do not open.

If the Qlik Sense Repository Database and Services starts correctly you need to to check the Qlik Sense Repository logs stored by default in C:\Programdata\Qlik\Sense\Log\Repository\Trace\Servername_System_Repository_date.log

In this log you might see errors at the end saying:

There was an error contacting the license service. Keep retrying... (1 failed requests) GET /v1/licenses/overview StatusCode: InternalServerError Response: .    Could not connect to the license service.    NO-STACKTRACE

If you have this error, you might have the below error in the Windows Application Event viewer:

Source Qlik Sense Service Dispatcher :

The description for Event ID 300 from source Qlik Sense Service Dispatcher cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Unexpected termination (0) for process 0
Facility = Licenses service
ExePath = ..\Licenses\licenses.exe
Script = 



You might also see the below PostgreSQL error in the Event viewer :

The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 

FATAL:  database "Licenses" does not exist

Environment:

  • Qlik Sense Enterprise April 2019

 

Resolution:


1. It is likely that the issue is related to what is documented under Node offline - GET /v1/licenses/overview StatusCode: InternalServerError Response Could not connect ...

2. See also: Qliksenserepository password error in the event logs after changing the database service user passw...

3. If the above is proven not to be applicable the following may be attempted. Before proceeding with below steps, check if the FQDN server name is correctly registered on the DNS server and the name is correctly resolved; refine the DNS configuration of the server accordingly with your IT. 

WARNING: Always have a backup of the underlying PostgreSQL database prior to performing any direct modifications of the database. Refer to the pg_dump portion on Qlik Help for the commands to perform a backup.

WARNING: Manual modification of Qlik Sense Repository Database is not supported and can cause product failure. Direct modification should be done in consultation with Qlik Support and only as a last resort. The database within Qlik Central node is for use by the Qlik Application alone.

To solve the issue you'll need to connect to the PostgreSql database with pgAdmin see How To Connect To And Modify The PostgreSQL Database Used For Qlik Sense Repository.

And the run the below Query :
 

GRANT TEMPORARY, CONNECT ON DATABASE "Licenses" TO PUBLIC; GRANT ALL ON DATABASE "Licenses" TO postgres; GRANT CREATE ON DATABASE "Licenses" TO qliksenserepository;


If you have an error saying the database License doesn't exist, you'll have to run the below :
 

CREATE DATABASE "Licenses" ENCODING = 'UTF8';


After this creation you'll be able to run the Grant query.

At the end you'll have to stop/restart all Qlik Sense services.


 

Labels (2)
Version history
Revision #:
5 of 5
Last update:
‎2021-02-11 10:24 AM
Updated by: