Qliksense 3.0 Error:- No Engine server is available for the following app app:_hub

[ashishkalia]

Hi All,

I just installed my Qlik sense 3.0 on my machine and licensed it. Installation and licencing all went correct.

Connected to Directory and allowed a token to my ID. Now when I am trying to open hub I am getting error

Error:- No Engine server is available for the following app  app:_hub

Checked all services: Running fine

Checked Engine on QMC: Status is running.

Please look into the issue as I am not getting any workaround.

[#2]

Hi All

Is the above fixed . We are using Qliksense 3.0 Version and facing the same issue..While reloading the app we are getting the Internal Engine Failed Error.. After restating the dispatch services its working. Is there any patch available to fix this issue

Thanks

Ranga

[ToniKautto]

There is a known bug related to the error message in 3.0.0. The scenario was related to server having restricted interne access or IPv6 being set as preferred connection. This is fixed in 3.0.1.

Check the following items if you still experience this issue in 3.0.1:

• Multi-node environment. Qlik Sense Dispatcher is listening on the port TCP 4900 on the central node. Make sure this port is open for communicaiton between central node and all RIM nodes.
• Restart Qlik Sense dispatcher service
• If DHCP is used, release the IP address on the Qlik Sense server machine by using ipconfig /release
• Restart the Qlik Sense server machine

[#4]

Thanks for the reply Toni

We are using single node environment and using Reload button in our Hub.when ever we are hitting the reload button it will refresh the app but some times we are facing issue while Internal server Error after restarting the batch services the issue is fixed

Thanks

Ranga

[ToniKautto]

If you are not already on 3.0.1, I would suggest updating.

If you are on 3.0.1 and still see this issue, I would suggest that you reach out to Qlik Support for further evaluation on the issue.

[#6]

It worked here, thanks

[Anonymous]

hi,

I don't face this issue on one Windows 2012 R2 box, but on a 2008 R2 box it gives this error. I am going to try with the work-around mentioned in this thread https://community.qlik.com/thread/226621 before considering upgrading the OS.

My QS is at 3.1 on both boxes.

thanks,

Ajit

[Anonymous]

Resolved the error with the service dispatcher port clearance. Another site was having a binding with the port 4900, which is where the service dispatcher is listening on. So we removed that binding, made 4900 available to the service dispatcher and the hub is running fine.

[korsikov]

Description

After installed/upgrade Qlik Sense 3.0.0, facing situation: Qlik Sense Desktop not working and get error message  The service did not respond or could not process the request Qlik Sense Hub can't open and get error message:  The load balancing module did not...following app:_hub No engine service is available for the following app:app:_hub

Cause

The issue is caused by node services is not listening on IPv4 and IPv6 at the same time.The scenario could possible happen when: The client machine has no Internet connection The client machine switched between LAN (cable) and WIFI (wireless) connection

Resolution

This is a known defect QLIK-58979, and has been fixed in Qlik Sense 3.0.1Possible workaround to resolve this: Enable Internet connection Check if IPv6 set as preferred connection, change it to IPv4 In QlikSense 3.0.1 in a multi node environment the service QlikSense Dispatcher is listening on the port TCP 4900 on the central node. This problem can occurs when this port is blocked from the RIM Node to the central node. Restart Qlik Sense dispatcher service Use - ipconfig /release to refresh the IP on the machine (if using DHCP) Make sure all latest Windows update are installed (The issue may be caused by a Windows defect existing in a patch from Microsoft. The defect has been fixed by Microsoft already.) Make sure that TLS 1.0 is enabled in the Windows registry even if you are using TLS 1.2 (https://technet.microsoft.com/en-us/library/dn786418(v=ws.11).aspx#BKMK_SchannelTR_TLS10). Another defect in the product (QLIK-53914) prevents the Proxy service to work correctly if TLS 1.0 is disabled. Restart the machine If after upgraded 3.0.1 still facing the problem, try to:

[korsikov]

how check is ipv6 is prefer?

simple ping localhost - if you see ::1 - it's ipv6. if 172.0.0.1 - ipv4 is prefer

for disableipv6 use MS tools in attach

[#11]

Hello i still with the problem, qlik sense 3.1.2, done all your recommendations