Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
May 26, 2021 9:29:33 AM
Oct 2, 2018 7:59:59 AM
In QlikSense, Hub login page is accessible but issue happens after username and password is provided with the error message "Internal Server Error" displayed. Qlik Management Console (QMC) has no issues.
Qlik Sense Enterprise on Windows
This can have multiple root causes.
When looking into browser developer tool F12 it registers: (Save network web traffic (HAR/XML file) and console logs from the browser's developer tools)
"500 (Cannot get engine services from the load balancing module for the following app: __hub)"
Opening an app directly also says there is no engine available. Does not matter which user is login nor which app is opened.
Load balancing URI in virtual proxy used but not set up correctly
Remove/modify settings under QMC -> Virtual Proxies -> Edit virtual proxy -> Central -> Integration -> Load balancing module base URI
Settings depend on the 3rd party load balancer used.
Verify the [hub.parameters].
Cause:
Port 9028 was not listening because of the below two parameters present in C:\Program Files\Qlik\Sense\ServiceDispatcher\services.conf and under [hub.parameters] and save the confg file.
Reviewing the Proxy's Trace System_Proxy logs indicates an issue with connectivity on port 4900.
Reviewing the Proxy's Trace Audit_Proxy logs indicates an issue with WebSocket connectivity on port 4747.
These ports are used by Qlik Sense Engine and Blocking services. See Sense used Ports.
The result of the following commands indicate PIDs that are not of Qlik Sense services origin:
netstat -bano | findstr :4900
netstat -bano | findstr :4747
Cause
Third-party applications such as HFSQL / HyperFile use port 4900 which may cause conflicts.
Note: Only port 4900 is documented to be used by HFSQL publicly.
How to approach Qlik Sense Error 404 Not Found The following URL is unknown for Hub and QMC
Qlik Sense - How to troubleshoot issue to access QMC and HUB
How to approach Error 500 - Internal server error issue