Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
After the upgrade to November2024 we are experiencing issues opening Qlik Sense hub, since it hangs showing a blank page. Sometimes it gets stuck showing the message "Opening Qlik Sense Hub" with the bubble animation undefinitely trying to open the dashboard. Any errors are displayed, the page simply does not populate with contents. The issue is resolved clearing the browser cache, but we have to repeat the operation many times a day.
No change was done to configuration during upgrade and the strange thing is that this issues arose only after upgrading to this version.
Any help would be appreciated
Thanks!
Hi, it is recommended to apply patch 8.
we have the same problem also with patch 8 .
The admin user that we updated with the patch is get blanck page..but the others users can watch perfect..
We have this November 2024 on the server.
clearing browser cache, cookies worked for only few users. but not for others. bubbles on hub continues. Our customers impacted heavily on this.
we don't know what still to be done further.
any permanent solution for this???
Hello! Have same problem after updating. Try to increase MaxHttpHeaderSize by this post.
But problem solved on few days, and now users catch error 500
I would suggest including this article:
https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-HTTP-Header-size-restriction/ta-p...
For sure this will help, we upgraded recently and had the same issue when using virtual proxy for SAML
hope this helps.
help users find answers! Don't forget to mark a solution that worked for you & to smash the like button!
Hello everyone! We tried to update to the latest SR for Nov 2024 ( SR8 if I remember correctly ) but without success. The customers affected by this problem enabled the cache auto-clearing option on their browser everytime they close the window as workaround. We didn't try to increase the MaxHttpHeaderSize basically for three reasons : 1) any authentication protocols ( SAML, ecc ) had been enabled for the affected virtual proxies 2) any errors are displayed ( neither error 400, nor 431 ) 3) beside that, we saw contrasting feedbacks about this kind of solution ( e.g. @Dustver 's reply ). We hope to get a permanent solution for this problem soon.
Thanks everyone for the kind support!