topic Qlik Sense Cluster 3.0.2 Error on RIM Nodes HUB - The service did not respond or could not process the request in Management & Governance

Qlik Sense Cluster 3.0.2 Error on RIM Nodes HUB - The service did not respond or could not process the request

hugo_andrade — Fri, 09 Sep 2016 20:24:03 GMT

Good day Community,

The RIM node's HUB doesn't work. It shows a message after I log in:

I have a fresh new install for a client on Qlik Sense SR 3.0.2 in a multi-node environment.

During the installation, I have specified the Service account to run the services on every server. It's the same domain account which has Admin rights to all the servers. All the servers are joined to the same domain.
Added Private IP, Public IP, Hostname, FQDN to the Virtual Proxy's white-list
ALL traffic is allowed internally between the nodes.
Only ports 443, 4244 and 4243 are publicly open to the world (that's a rule present in the Proxy node)
IPV6 is disabled in all nodes
User account used in the HUB does have access to a token (User Pass)
Applied a valid SSL Certificate (HTTP is not an option)
There's plenty of RAM, CPU, Disk space available (huge servers)
Windows Server 2012 R2 with all updates installed
.Net Framework is also updated

After reading some posts in the Community, I tried additional steps:

About the environment:

Servers	Notes
Central	HUB used for internal purposes. It's own Engine is used by the HUB.
Scheduler	All tasks run on this node since the Central server was configured as Master only.
Engine - Prod	Engine attached to the Proxy server for Production purposes.
Engine - Dev	Engine attached to the Proxy server for Development purposes.
Proxy	Public facing Proxy with Engines Prod and Dev in Load Balancing. QMC opens fine in this server. Central server is not an Engine option for this Proxy server.

ALL HELP is appreciated, but please read the specifications first before suggesting something. This is a 2000+ Qlik Sense Users environment.

peter_turner — Tue, 13 Sep 2016 16:03:02 GMT

Hi Hugo,

Not sure if this will help but does your implementation use Tags?

I've run into problems with multi node setup when using Tags, and the solution was to remove them.

Hopefully this will be fixed in later versions.

Fri, 16 Sep 2016 13:17:05 GMT

I had a similar issue but already solved, not sure if is the same problem. Look if this works for you

hugo_andrade — Fri, 14 Oct 2016 13:31:12 GMT

Peter, we didn't implement Tags yet. But this is good to know!

balexbyrd — Thu, 26 Oct 2017 01:51:28 GMT

Did you ever get this issue resolved? If so, do you remember how? I'm having the same issue