Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all,
I tried opening https://sense-demo.qlik.com/hub/ with Internet Explorer 11 and I get the following error:
I get the same error when I try to open Desktop Client Qlik Sense 3.0.1 using http://localhost:4848/hub/my/work
My Internet Explorer 11 version:
I thought Internet Explorer 11 should be supported with all Qlik Sense versions?
Many thanks,
Martin
Hi,
Did you tried with changing the Default browser to Google Chrome?
I want to be able to use Qlik Sense with IE11 which is supported according to the documentation:
I can not replicate this issue. My IE11 is however on a slightly later version than yours. Is it possible for you to upgrade IE?
Unfortunately, not.
Qlik Sense 3.0 documentation does not specify any particular sub-version of IE 11 so I expect it work on all versions.
Maybe it's a client or network setting that needs to be updated on my side?
Did you reset IE and add the hub to the trusted sites?
Does it work in other browsers?
Also, are you using any custom extensions?
Yep, Chrome works fine for example.
In regards to your other question, I don't know if https://sense-demo.qlik.com/hub/ has any extensions. Either way, it's Qlik's demo site so it should work, shouldn't it?
I see, I thought this was something you made, the reason I asked about the extensions is because the only times I've encountered the "Object doesn't support this..." error is when I was making a custom extension and used their API incorrectly. But then it wouldn't work on any browser.
It is not uncommon that issues occur in IE and not in other browsers. The main reason for this is that Group Policies have been applied in IE, which then interfere with functionality. Symptomatically this issue would look more like a system side issue rather than Qlik Sense issue.
In this case I wonder if the websocket communication work from your IE. Can you test https://www.websocket.org/echo.html to see if websocket work in general?
For further troubleshooting, Fiddler traces could reveal where the communication breaks and help identify the root cause. Ideally the Fiddler analysis would be done by comparing a successful access with a failed one.