Skip to main content

Announcements
Solving the Informatica Dilemma: On-Demand Briefing - Watch On Demand!

QlikView Management Server thinks new QlikView Server is also a Distribution Server (QDS did not respond error printed in QMS log)

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

QlikView Management Server thinks new QlikView Server is also a Distribution Server (QDS did not respond error printed in QMS log)

Last Update:

Aug 16, 2021 7:00:59 AM

Updated By:

Sonja_Bauernfeind

Created date:

Apr 27, 2017 9:26:09 AM

The following error has started appearing in the QlikView Management Service logs since adding a new QlikView Server:

Error Failed to retrieve QDS info: System.ServiceModel.CommunicationException: QDS did not respond to request. 
Last exception (for http://QLIKVIEWSERVER:4720/QDS/Service): ANY did not respond to request.

 

Environment:

QlikView  

 

The QlikView Management Server thinks that the new QlikView Server is also a Distribution server so tries to reach it on port 4720.

When you add a new QlikView Server, it automatically gets added to QDS Cluster table in QVPR. This behaviour has been raised as a bug however this cannot be changed in the code hence the resolution steps above.

 

Resolution:


You can remove the invalid QlikView Distribution Server reference via the Management Console. To remove the reference you must do the following:
 

  1. Stop the QlikView Management Service service
  2. Navigate to the configuration file for the QMS, by default located in C:\Program Files\QlikView\Management Service\QVManagementService.exe.config
  3. Locate the value:
        <!-- Possibility to make Reload Engines visible under Setup/System Distribution services  -->
        <add key="ShowReloadEngines" value="false"/>
  4. Change it from "false" to "true"
  5. Save the file in its original location
  6. Start the QlikView Management Service service again
  7. In the QMC, navigate to System - Setup - Distribution Services
  8. Locate the incorrect reference and delete it.

 This should resolve this issue and remove the error in the alert from the QMC.

Labels (1)