Qlik Sense 3 not working in embedded browser

[ichimiike]

Hi there,

We're currently in the final(ish) stages of getting out BI solution together and have encountered a strange problem,

Over the the last few months, we've created what will be our customer facing BI Server (hosted in Azure) which runs Qlik Sense 2.2... this works fine when accessed either directly through a browser or via our existing application (which is how our customers will be accessing the server).

This week, we've created a development server and have upgraded the version of Sense on this to v3... again, accessing the new dev server works fine using a browser... but NOT when going via our product.

Basically, the hub loads as expected and everything looks OK... but  when we try to click on anything, we get a flicker of the control (so the embedded browser DOES appear to be getting the click event) but nothing else happens.

One of our developers has tried this with breakpoints set throughout the code (our application code) and nothing appears to be getting sent back.  In addition to this, I've created a basic c# application which simply has a browser control... this does exactly the same.

Within our application, we're using the standard Microsoft CHTML control (again, the c# test was the standard MS object) so there's nothing weird and wonderful going on.

Can anyone confirm if this is a known issue / if there's something we can do to get around it.

Cheers in advance for any help you can offer,

Mat

[ichimiike · Accepted solution]

So... it turns out that the issue was down to registry settings (or lack of them)...  I've listed the entries we've had to make in order to get Qlik working embedded in our app...

In addition to the issue listed in the original post, we also had problems with javascript errors and 'Unable to create connection' messages...  these also get resolved ('IntranetCompatabilityMode' for the JS error... 'MaxConnectionsPerServer' for the 'Unable to create connection' message... note: the 128 (80 in hex) value for this is the maximum allowed)/

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\BrowserEmulation]

"IntranetCompatibilityMode"=dword:00000000

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION]

"Primo.exe"=dword:00002af8

"Tharstern.exe"=dword:00002af8

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WEBSOCKET_MAXCONNECTIONSPERSERVER]

"Primo.exe"=dword:00000080

"Tharstern.exe"=dword:00000080

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_CLIPCHILDREN_OPTIMIZATION]

"Primo.exe"=dword:00000001

"Tharstern.exe"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_AJAX_CONNECTIONEVENTS]

"Primo.exe"=dword:00000001

"Tharstern.exe"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_GPU_RENDERING]

"Primo.exe"=dword:00000001

"Tharstern.exe"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_WEBOC_DOCUMENT_ZOOM]

"Primo.exe"=dword:00000001

"Tharstern.exe"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_NINPUT_LEGACYMODE]

"Primo.exe"=dword:00000000

"Tharstern.exe"=dword:0000000

[Anonymous]

Hello,

we have the same problem.

Has anyone a solution for this Problem?

Regards

J.Groß

[ichimiike]

Hi Jurgen,

Try copying the above registry keys into a .reg file and then applying it to the registry of the machine you're having a problem with,,, It should sort the problem out for you.

Mat

[#5]

Hi Mat,

Thanks for the post. It worked for me.

Where did you find the information about these registry settings? I'd like to learn more about them.

Craig

[ichimiike]

Hi Craig,

To be perfectly honest, it wasn't me that found the solution.. it was my developer bud across the desk.

Essentially, he realised that the it wasn't a case of the page actually not working since when we clicked on buttons, you could see the animation of them being clicked... it was simply as though the click event was being triggered...

This, combined with the fact that we'd run into registry problems previously, led to some googling / trial and error until we finally had a working solution.

Mat