Qlik Community

New to Qlik Sense

Discussion board where members can get started with Qlik Sense.

Announcements
BI & Data Trends 2021. Discover the top 10 trends emerging in today. Join us on Dec. 8th REGISTER
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Partner
Partner

QlikSense Hub Error

Hi,

I am having QlikSense Server 3.1 installed and running. Earlier both QMC and Hub were working fine.

Today I try to login on the Hub, I am getting following error.

" The Proxy is waiting for a new session"

The QMC is working fine, I can see the user and the applications on that, but the Hub is not opening.

All the services are running fine and I have restarted all the services.

Any suggestions.

9 Replies
Highlighted
Partner
Partner

facing the same issue any clue how to solve it? thanks.

Highlighted
Partner
Partner

restarting machine solved my issue.

Highlighted
Partner
Partner

Same here, restarting the machine works.

But I think there is a Service , QlikSense Service Dispatcher, which if not running throws the same error.

Highlighted
Not applicable

Hello,

Restarting the machine doesn't work for me.

Any other options?

Thanks!

Highlighted
Not applicable

Hello,

Does someone know more about this error ?

Thibaut.

Highlighted
Employee
Employee

Ran into the same issue today. Restart the 'QlikSense Service Dispatcher' and that should fix it for you. Essentially proxy is not able to find a new session if the service dispatcher is not running. Please mark answer as correct if this fixes it for you.

Highlighted
Creator III
Creator III

Yes Service dispatches is what creates new session !!!

Highlighted
Contributor III
Contributor III

We had the same problem. Infrastructure installed few security updates. But then, over the weekend the services stopped working and hub started throwing the error. Just restarting the dispatched didn't fix the problem. It will work for a minute and then revert back to the error.


I had to stop all Qlik services and start with QRD as stated here - QRD should be the first service to be started/stopped when restoring the central node. Then, it all started working just fine!


Services ‒ Qlik Sense

Highlighted
Partner
Partner

Manoj's suggestion worked for me. Thanks!