'Reload Engines' are automatically added to an environment any time a new QlikView Server resource is added into the environment via the QlikView Management Console (QMC) -> System -> Setup -> QlikView Servers area.
Environment:
QlikView all versions
Resolution:
Beginning with QlikView 11.20 SR15, and including QlikView 12.XX, it is possible to remove the Reload Engine via the QMC.
The same resolution posted below also resolves QlikView Server allows for Max concurrent reloads to be configured in the QlikView Server Settings, ...
- Stop the QlikView Management Service service via Windows Services applet
- Navigate to the configuration file for the QlikView Management Service, by default located in C:\Program Files\QlikView\Management Service\QVManagementService.exe.config
- Locate the value
<!-- Possibility to make Reload Engines visible under Setup/System Distribution services -->
<add key="ShowReloadEngines" value="false"/>
- Change it from "false" to "true" in the value= area
- Save the file in its original location
- Restart the QlikView Management Service service
- In the QMC, navigate to System -> Setup -> Distribution Services (ensure the Distribution Services folder is highlighted)
- Look to the right of the screen to see if the Reload Engine is listed along with the "QDS@SERVERNAME" resource; locate the "ReloadEngine@SERVERNAME" reference in the Reload Engines area and delete it.
This should remove the Reload Engine from the environment and stop the QMC from displaying the orange banner message that the service is down.
Should the above not work, a manual clean-up of the QVPR will be necessary, and Qlik Support can assist with it.
Cause:
When you add a new QlikView Server resource to an environment, it automatically adds a new 'Reload Engine' entry to the DistributionService.xml file in the QVPR. There are also other entries in the QVPR that are done as well, but using the above solution will clean everything up and repoint things to the proper GUIDs.
