What is the QlikView License Service and Qlik Service Dispatcher?

[Chip_Matejowsky]

Information regarding the QlikView License Service and Qlik Service Dispatcher included in QlikView April 2019 version and up.

Environment

• QlikView, April 2019 and up

What is the QlikView License Service?

In QlikView April 2019 or later, a new License Service component is delivered together with QlikView.  This service is used when the signed key is used for product activations.  The License Service will connect to a License Backend Service, hosted by Qlik, for product activations and Entitlement Management.  This activation process is required for using a unified licensing solution.  The new activation process is currently optional for QlikView Server.  The use of this activation process is also required if you want to use the new Professional and Analyzer Users licenses (user-based) and Analyzer Capacity licenses (capacity-based) introduced with QlikView April 2019.  The License Service uses port 443 for accessing the end-point at https://license.qlikcloud.com and retrieving license information.

In a multi-node deployment, the Qlik License Service is installed on the machine running the QlikView Management Service (QMS).  You can manage the status of the Qlik License Service by starting and stopping the Qlik Service Dispatcher, listed in the list of services running in the Windows machine.

The QlikView License Service will not be in use if a QlikView Server/Publisher license and control number are used to license the product (LEF based) and Signed License Key (SLK) is not used .

What is the Qlik Service Dispatcher?

The Qlik Service Dispatcher is the Qlik service listed in the Windows Services applet that manages the QlikView License Service.  If a SLK is not used to license QlikView Server/Publisher and license/control number is used, the service can be disabled.

Related Content

• Qlik License Service 
• QlikView Server License 
• Licensing QlikView 
• Why does QlikView Connect to https://license.qlikcloud.com? 

[shravan]

HI Chip, 

1) WE have recently upgraded our env. from Nov 2017 to Apr 2020. Post upgrade, there was a red banner on the QMC mentioning " the LEF is not started or cannot be reached " message if i remember the exact words, 

we use NTLM auth and I dont think we need this service to be up and running as per your article. but this red banner is annoying. Ultimately, we had to start the QSD service to get red of this banner message in QMC. Do we have an option to overcome this ?

2) The QSD service runs with a local account whereas our QV services run with a specific service account. 

Is it necessary to also change the log on user of the QSD service to our service account as well or do you think it is not needed ?

[Sonja_Bauernfeind]

Hello @shravan 

Whether or not you need it depends on the license in use, really. If you are using a legacy license that still uses CALs, then the license service is not in use. It is not tied to what sort of authentication you use.

Here is a little more about the two different licenses: The Signed License Key (SLK) and the License Enabler File (LEF)

If you chose not to have the service running, we do not have a supported method to disable the warning.

As for your second question: All QlikView services should share an identical service account to ensure they can communicate and that there are no permission issues.