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 .
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.
Ensure the QlikView Server (QVS) license key and control number is readily available
Stop the QlikView Server service
Start QVS Service
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)