With the release of QlikView 12.10, Qlik has introduced new functionality to make QlikView easier to manage. One of those features is the capability for the QlikView Management Service to detect if there are any other QlikView Management services trying to manage the same set of servers, and if found inform the administrator about the issue.
If the QlikView Management service detects that there are conflicting instances of the Management Service trying to access servers it controls, a new informational banner will be displayed in the QlikView Management Console (QMC)
This message indicates that there are more than one QlikView Management Service trying to control the existing environment, which will lead to instability in the product as conflicting settings might be set by them. One of the design demands in QlikView is that there can only be one instance of QlikView Management Service running in the environment, regardless of size,.
By opening the QlikView Distribution Service Root log, we can see further indications of the different QlikView Management Services trying to set different values for the same service. This log file can be found in the QlikView Distribution Service Root folder, by default C:\ProgramData\QlikTech\DistributionService\1\Log
Further evidence of the QlikView Distribution service receiving multiple sets of instructions can be found in the log file labeled with date only in the same folder, C:\ProgramData\QlikTech\DistributionService\1\Log, you can see messages with "Warning Multiple caller detected. Current IP:xx.xx.xx.xx, Previous IP: xx.xx.xx.xx
The resolution to this issue is to find and disable the second QlikView Management Service using the information from the log files so that there is only one QlikView Management Service trying to control the services in the environment