Skip to main content
Announcements
Live today at 11 AM ET. Get your questions about Qlik Connect answered, or just listen in. SIGN UP NOW

Initialization of the Qlik Sense Management Console failed for the following reason: 500 - Internal server error - Qlik Sense

0% helpful (0/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Chip_Matejowsky
Support
Support

Initialization of the Qlik Sense Management Console failed for the following reason: 500 - Internal server error - Qlik Sense

Last Update:

Aug 24, 2020 9:59:08 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 25, 2019 4:31:01 PM

When attempting to access the Qlik Sense Management Console (QMC) using URL https:\\proxyservername\qmc or utilizing a configured load balancer URL the following error is returned:

Initialization of the Qlik Management Console failed for the following reason: 500 - Internal server error

Environment:

Qlik Sense November 2018 and up

 

 

Cause:


The existing certificate between the Central node and the Proxy node has become invalid.

 

Resolution:


On the proxy node server, review the Proxy > System_Proxy log to identify errors such as:

Error during stream authentication as Server    Authentication failed because the remote party has closed the transport stream.
Error during stream authentication as Client    Authentication failed because the remote party has closed the transport stream.


On the proxy node server, review the Repository > System_Repository log to identify error such as:

Result=500;ResultText=Error: -----System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

Utilize Windows CAPI2 logging to further troubleshoot issue as shown in Qlik Support article Using Windows CAPI2 logging to Diagnose Certificate Issues.

Remove the existing certificates from the Proxy rim nodes and redistribute the certificates to these nodes via the QMC > Nodes page using the Redistribute button as outlined in Qlik Support article Rim node not communicating with central node - certificates not installed correctly.

Labels (1)
Contributors
Version history
Last update:
‎2020-08-24 09:59 AM
Updated by: