"No engine service available for the following app: app:__hub" on Qlik Sense 3.0 Proxy Rim

[#1]

I am attempting to move a client's setup from a single-node installation of Qlik Sense 2.2 to a multi-node installation of Qlik Sense 3.0

I have the central node up and running, and a proxy node talking to the central node fine.  The central node sees the proxy node running properly (2 of 2 services running).  Going to the Hub works fine on the central node, showing the apps that we migrated across to the new (fresh) central node install.  The proxy node is a new install as well, however when I go to the hub on the proxy node I am met with this error:

An error occurred

No engine service is available for the following app:

app:__hub

I thought this may be fixed by going to 3.0 SR1 (as I saw in some other posts here).  However this has not fixed my problem.  I have also tried restarting the Service Dispatcher on the proxy node.  I am not sure where else to look here as the logs on the proxy appear to be fine.  Where else can I look to find what is causing this problem?

[madsgrathe]

I'm having the same issue but on a single-node installation of 3.0.1.

[korsikov]

i'm have same issue. and new one. I'm can't install QS Cluster on 3.0.1. in Resository log see line "Http Error 400" and that is all.

[gandalfgray]

Hi guys!

Did any of you find a fix?

I get the same error on a fresh installed multinode 3.0.1 installation.

I have tried restarting all QS services on central node but that did not help

[korsikov]

i'm found one way to create multinode site QS 3.0.1

install QS 3.0 on Central and Rim node. Then upgrade to 3.0.1 And Works fine

On clean instalation 3.0.1 i'm can't attach Services on rim node to QMC

[gandalfgray]

Hi

There may be more than one cause of this error.

But in our case it was a problem with an undocumented port the central node is using.

The central node is listening on tcp port 4900, so this port needs to be open from the proxy nodes to the central node.

This is confirmed with Qlik Support, they are going to update the documentation.

[korsikov]

this advice is not solve my problem. I'm disable any Firewall in all nodes cluster

[gandalfgray]

Yes I see, guess there may be other causes too...

[#9]

Is this a dynamically generated port?  I added TCP/4900 to my firewall and I am getting a different error, it just says 'An error occurred".

When I disable the firewall between the Central and Rim node it works fine.  Obviously this is not an acceptable solution for a production environment.

Do I need to enable more ports?  I currently have open on the Central Node:

TCP 80, 443, 4241, 4242, 4243, 4244, 4248, 4444, 4747, 4900, 5050, 5151

[madsgrathe]

‌What worked for us was to run Windows Update on the server.

This hadn't been done so there were a lot of updates to the .NET framework, among others.

After this, the service has been running without issues.