topic Re: Access issue with PlugIn not Ajax client in QlikView

Access issue with PlugIn not Ajax client

Mon, 26 Jan 2026 18:19:17 GMT

Hi.

We have a qv cluster setup (QV 11.2 SR8). WebServser = IIS.

Users comming in from outside is directed to the Access Point through a NetScaler setup.

When I logon with my user through the NetScaler everything works fine - that is: My user can open qvw files with both the Ajax and the IE PlugIn client.

Using the PlugIn gives me an URL like this:

https://qlikview.company.com/QvAJAXZfc/AccessPoint.aspx?open=&id=QVS%40qlikcluster%7CSales.qvw&client=Plugin

Now for some reason we have a user who also is comming through the Netscaler and the user can access/open the qvw files with the Ajax client without any problems but using the IE PlugIn the user gets this error:

qvp://qlikcluster2.company.com/Sales.qvw?iis_authenticate=CD9391F936384A8C23DD69DA80648E5C&tunneler=https%3A%2F%2Fqlikview.company.com%2Fscripts%2FQVSTunnel.dll%3Fhost%3Dqlikcluster2 could not be opened

What could be the reason for this? (if this has to do with the PlugIn communication on port 4747, then i guess my user also shouldn't be able to access/open the qvw file with the PlugIn client?)

Re: Access issue with PlugIn not Ajax client

Wed, 03 Dec 2014 14:02:37 GMT

Hi again
I have been testing with the user that has a problem getting access with PlugIn Client. And accessing the AccessPoint and the app there after with his user from my laptop is no problem. That points the problem to bee with his local machine.

His running IE 11 which is supported by the QV11.2.SR8 setup - so which settings in the IE browser could bee the reason for the "...could not be opened" error mentioned above?

Re: Access issue with PlugIn not Ajax client

Fri, 05 Dec 2014 08:57:28 GMT

Hi.

Looking at the IIS log - the error below could be seen. The "localhost" part looks strange to me. Any ideas why the user gets an: "Unable to connect"?

The error:

2014-12-02 11:11:16 172.20.110.104 POST /scripts/QVSTunnel.dll host=qlikcluster1+Unable+to+connect+to+localhost:4774+{10061} 80 - 5.179.85.37 QlikView+Client 200 0 0 1029

Re: Access issue with PlugIn not Ajax client

Fri, 05 Dec 2014 09:15:39 GMT

Hi CapHF,

the IEPlugin and Ajax clients do use different ports, if Ajax is working but the plugin is not then this would point to a tunnelling issue on port 4747. Does this second user have a different setup to yourself on NetScaler? Potentially blocking that port for them but not you?

Re: Access issue with PlugIn not Ajax client

Fri, 05 Dec 2014 09:22:40 GMT

Hi Joe.

I've asked the IT department the same - and the answer was: There is no difference in the communication once the user is logged into the Access Point.

When I login from my machine with his user - I don't get the error: "qvp:....could not be opened". And that for me points to the fact that it's not user related, but location or machine related.

Re: Access issue with PlugIn not Ajax client

jerrysvensson — Fri, 05 Dec 2014 09:25:36 GMT

Have you tried adding the full path to QVS in Link Machine Name? Not qvp:// as in the Url box.

QMC: System- Setup- QlikView Servers-General

We have seen similar problems before we did this.

Re: Access issue with PlugIn not Ajax client

Fri, 05 Dec 2014 09:33:55 GMT

Hi Jerry.

I'm not sure what you mean - could you please specify?

At the moment the setup in the QMC is:

URL:

qvp://qlikcluster1/

qvp://qlikcluster2/

Link Machine Name:

qlikcluster1.company.com

qlikcluster2.company.com

Re: Access issue with PlugIn not Ajax client

jerrysvensson — Fri, 05 Dec 2014 10:03:03 GMT

Exactly what I meant.

Link Machine Name is optional, so I thought you might not have used it.

To bad you already using it. 🙂

Re: Access issue with PlugIn not Ajax client

Thu, 11 Dec 2014 21:07:17 GMT

This was due to a setting on users firewall that blocked in and out bounce communication on port 4747. Once this blocking was disabled the user got access to the qvw document.

Re: Access issue with PlugIn not Ajax client

maksim_senin — Tue, 29 Mar 2016 00:32:19 GMT

Hi,

In my case it happened due to firewall on server side, the issue gone once I added exclusion for inbound port 4747.

Best regards,

Maxim