Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

felcar2013
Contributor II

QvPlugIn not working: Is the plugin with https compatible?

Hi

our QV customers access the Access Point via https (extranet). Web Server is IIS7 and we have a machine with the QVS and another machine for the web server. Our customers access the web portal of the second machine. Our customers can see the documents for the ajax version, but when trying to open with plugin, they get an error message like

qvp://<intranet server name>iis_authenticate=xxxx&tunneler=https%3A//<Extranet (FQDN)>/QVSTunnel.dll%3Fhost%3D<intranet server name> could not be opened

URL

https://<Extranet>/QvAjax../AccessPoint.aspx?open=id=QVS<intranet server name>

I have tested using the link machine name = the domain name that customers access, but they still receive the same error message.

For users inside our intranet (using the same URL and custom accounts from QMC), the plugin works fine.

i have two questions:

1. Why our external customers get this error and cannot use the IE plug in? (all off them with IE 9 or less)

2. Does QvPlugIn work with https? Initial connection not necessarily via http, but https. It seems there is a problem between the qvp and the external client

3. what shall i change in the QMC so that it works? Ports are open

many thands

felipe

1 Solution

Accepted Solutions
Employee
Employee

Re: QvPlugIn not working: Is the plugin with https compatible?

That is the reason I put this "also, in the firewall port 4747 needs to point to QVS server" in. The client has to be able to get to the QVS server on port 4747.

Bill

6 Replies
Employee
Employee

Re: QvPlugIn not working: Is the plugin with https compatible?

The plugin talks to the server on port 4747 and nothing to do with ssl. Your issue maybe the linkmachine name. The attached document may help you. Look at the troubleshooting at the end.

felcar2013
Contributor II

Re: QvPlugIn not working: Is the plugin with https compatible?

Hi, thanks for the answer

i already had the document and everything was done like that. Port 4747 is open. We have two machines. One containing the QVS and the other the web server IIS7.

I had a similar issue before, adapted the settings and included the link machine name as it is showed in the URL for our external customers, which access the qv portal via internet. In that setting we created user accounts locally on the windows server and it worked fine.

Now, I included the link machine name as it is showed in the domain for external customers, but still got the same error. the QVS is in another machine.

I imagine i need to change the QVS and QVWS names and set the names as the link machine name (the URL for external customers). We have under the QVWS option two web servers, the one for the intranet and the other for the extranet. Is this correct?

thanks

Employee
Employee

Re: QvPlugIn not working: Is the plugin with https compatible?

Hi,

I have been looking for this in the new server manual, but it isn't in it. On the server that is running IIS you will need to but this in the registry.

Microsoft IIS:

Two entries are required in the registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\QlikTech\QlikTunnel]

"QVSPort"=dword:000012a6

"QVSServer"="QvsHost"

QVSHost is the name of the QVS server.

also, in the firewall port 4747 needs to point to QVS server.

Bill

felcar2013
Contributor II

Re: QvPlugIn not working: Is the plugin with https compatible?

hi Bill

we tried the changes you proposed. It did not work. the web server IIS became unstabel and stopped services, like 5 o 6 times in an hour. We needed to restart manually.

We made the configuration back, so that the web server works like before.

i realized that the Server Manual for QV11 is much smaller than the ones from old versions. Why is this? QV10 explains better.

we still have the problem and external clients cannot use the plugin

a comment from a Qliktech consultant refers to the following

"If the QVS servers do not have a forward facing IP address, this will not work. The only solution is to evoke tunneling with the Plugin Client." I do not quite understand this statement. this was forwarded by another consultant who is on holidays now

thakns

felipe

Employee
Employee

Re: QvPlugIn not working: Is the plugin with https compatible?

That is the reason I put this "also, in the firewall port 4747 needs to point to QVS server" in. The client has to be able to get to the QVS server on port 4747.

Bill

felcar2013
Contributor II

Re: QvPlugIn not working: Is the plugin with https compatible?

we did the changes and it worked!

port 4747 did not point to the QVS,

Thanks

felipe

Community Browser