topic Re: IE plugin + Qlikview 11.2 sr3 in QlikView

IE plugin + Qlikview 11.2 sr3

Thu, 05 Sep 2013 14:15:42 GMT

Hi all! I must to use my reports throught IE plugin, but i have the following issue:

if i try to pen it via full browser - it will be fine.

Could you help me please?

Re: IE plugin + Qlikview 11.2 sr3

Sat, 12 Oct 2013 19:16:54 GMT

Hi,

Did you find any solution for this issue? I am having the same problem with Qv 11.2 SR3 + IE plugin. Works fine with Ajax..

Re: IE plugin + Qlikview 11.2 sr3

giakoum — Sat, 12 Oct 2013 20:01:56 GMT

Have you updated your plugin to the latest version? try downloading and installing the latest version.

Re: IE plugin + Qlikview 11.2 sr3

Sat, 12 Oct 2013 20:08:56 GMT

Yes, we are using the latest version of the plugin..

Re: IE plugin + Qlikview 11.2 sr3

giakoum — Sat, 12 Oct 2013 21:35:38 GMT

this happened to our server also, and the problem was the shared objects file of the report on the server. We deleted the file and then it opened just fine. Of course all shared objects were lost. Try open it in web view and delete all unnecessary shared objects. Maybe this helps.

Re: IE plugin + Qlikview 11.2 sr3

Sun, 13 Oct 2013 07:59:08 GMT

Thanks for the reply,

Unfortunately that didn't help. Tried to remove the .shared file but still the same error. I am a bit confused about the "iis_authenticate" in the error message, becouse we are not using the iis..

Re: IE plugin + Qlikview 11.2 sr3

Mon, 25 Nov 2013 10:45:58 GMT

Hi,

we do have similar problem caused by IE 64bit.

If we connect to a report by using a direct link and IE9 64bit a message of the find you got is displayed.

But using the IE9 32bit all thinks are fine.

I just now investigate if a dual installation of 32bit and 64bit IE Plugin would work.

The smarter Way is to use AJAX link. IF this is possible, our users are not very happy with AJAX Client. Because the performance experience is not the same as with the Plugin.

Regards

Michael

Re: IE plugin + Qlikview 11.2 sr3

Fri, 09 Jan 2015 21:40:33 GMT

I was able to solve this problem in IE 11 by disabling Protected Mode in the zone in which the QlikView web page ran under.