Skip to main content

New to Qlik Sense

If you’re new to Qlik Sense, start with this Discussion Board and get up-to-speed quickly.

Announcements
Welcome to Qlik Community! Check out our new navigation! FIND OUT MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
psinhasq1
Partner - Contributor II
Partner - Contributor II

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
muhammadraza
Partner - Creator
Partner - Creator

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

muhammadraza
Partner - Creator
Partner - Creator

restarting machine solved my issue.

psinhasq1
Partner - Contributor II
Partner - Contributor II
Author

Same here, restarting the machine works.

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

Not applicable

Hello,

Restarting the machine doesn't work for me.

Any other options?

Thanks!

Not applicable

Hello,

Does someone know more about this error ?

Thibaut.

scw
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.

karthiks_dwbi
Creator III
Creator III

Yes Service dispatches is what creates new session !!!

mramachandran3
Partner - Contributor III
Partner - 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

morenoju
Partner - Specialist
Partner - Specialist

Manoj's suggestion worked for me. Thanks!