Skip to main content

Official Support Articles

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
CUSTOMERS ONLY: Now accepting customer applications for the 2023 Luminary Program: SUBMIT NOW

Unable to start QlikView Server Service - Status Message: Off Duty

cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Unable to start QlikView Server Service - Status Message: Off Duty

The QlikView Server service will not start after applying a license. The QlikView Management Console displayed "Off Duty" status. 

Environment:

QlikView 

 

There are multiple possible causes and resolutions:

1. Multiple QlikView server licensed with the same LEF:

Verify that the license is only used once in the environment. If the license is applied twice, one QlikView server will shut down with the following message logged in the QlikView Server event log:

Warning    Init: The initialization process failed. Cluster Count Exceeded, going off duty

The same issue may be caused by a network card loopback causing the QlikView server to respond on two IP addresses.

This only applies to servers licensed with a license key and control number and not with a unified license using a signed license key.

2. Nodes in the cluster exceed the allowed amount:

If setting up a clustered environment, make sure that the license is setup for clustering and has the correct number of nodes in the LEF.
The entry in the LEF that determines cluster count is: NUMBER_OF_CLUSTER_NODES;X where X is 2 or higher. This number cannot be exceeded. 

3. Invalid Root folder:

Verify that the QlikView Server document root folder is accessible and correctly configured. In a cluster, all nodes need to share the same root folder.  
The root folder can be read from the settings.ini stored in C:\ProgramData\QlikTech\QlikViewServer.

The chose shared root folder must not point to the the local C:\ProgramData\QlikTech\QlikViewServer of Qlik View Servers .

Locate: DocumentDirectory=\\STORAGE\folder

4. Service Account identical across all nodes

If the QlikView Administrators Group is used for Service authentication, verify that all services use the identical domain user. See QlikView: Am I using Certificate Trust or Windows Groups between the services? on how to verify what method is used.

5. QlikView Server Folder corruption 

In rare instances, a required file (settings file, pgo file, etc..) is damaged on disk and the QlikView Server is unable to read it upon startup. This folder can be recreated for troubleshooting purpose.
Note! All previous license allocations and CAL assignments will be lost. This should only be used as a troubleshooting step.

  1. Ensure the QlikView Server (QVS) license key and control number is readily available
  2. Stop the QlikView Server service
  3. Rename* the C:\ProgramData\QlikTech\QlikViewServer
  4. Start QVS Service
  5. Re-license QVS under Qlik Management Console (QMC) > System > Licenses > QlikView Server > QlikView Server License

*Renaming the folder ensures that the data is saved and can be copied over again after the folder was recreated. 

6. LEF timelimit date has passed:

The date mentioned on the LEF as Timelimit has been passed.

Please, update the LEF within the new information and a valid timelimit value and afterwards restart the QVS service.

On the QVS Event logs you might see: System: CQvXmlInterfaceRequestHandler - Catch: errId(-500). Ino(-1). Fno(90)


 

Labels (1)
Version history
Last update:
‎2021-12-22 05:51 AM
Updated by: