Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
i get this error when using IE plugin:
qvp://SERVER/file.qvw?iis_authenticate=FDFSREWEWR43232FSDFSDFS343&tunneler=http%3A/scripts/QVSTunnel.dll%3Fhost%3DLocalhost could not be opened.
i tried to use opendoc_fix, added localhost and servername to the host file. doesn't solve the problem. any one else see this error?
seems like it is a specific tunnel issue?
Hello Amien,
It seems that your QlikView server has somewhere a wrong value to point out to "localhost", since you are getting
http:/scripts/QVSTunnel.dll
after the tunneler part in the URL in your post, instead of showing http://SERVER/scripts/QVSTunnel.dll. Which server (IIS, QVWS) and version are you using? Is the test dll reachable at
http://Server/scripts/qvstunnel.dll?test
Does that work in the local computer?
Regards.
Hi,
Thank for your reply (again) . my bad .. i missed typing the url there. the domainname is before /scripts/
i'm using QVWS. why is there iis_authenticate in the url? i'm not using iis.
http://Server/scripts/qvstunnel.dll?test gives me back:
IE: empty screen
FF : <HTML><HEAD></HEAD></HTML>
using 10 SR1
Hi,
Is there any IIS in the network that can be catching QlikView Web Server traffic or proxies or firewalls that don't allow the port 4747 to work?
If you need to tunnel (because of restrictions in the use of 4747 port), is the C:\ProgramData\QlikTech\Config.xml file set up properly?
<qvshost>HostNameHere</qvshost><tunnelhost>HostNameHere</tunnelhost<
Hope that helps
IIS is installed (but not used in QVS). We use IIS just to forward root to /qlikview (should be changed to a simpel html script)
i have checked config.xml file .. but i dont see the nodes that you mentioned. should i add them? if so, under what node should i add them?
btw .. i have disabled IIS and the error was still there
Hello Amien,
Pasted from the Server Ref Manual (v10 pp. 163):
For Tunneling using QlikView Web Server:
Edit the Config.xml file to specify the location of the <QvsHost> and <TunnelHost>. <QvsHost> is used
in all non-tunnel-cases and <TunnelHost> when tunnelling is requested. It is thus possible to have one
Qvs handling all non-tunneling and another handling tunnelling. Note that if you omit <TunnelHost> the
QlikView Web Server will NOT support QVS tunnel.
<Config>
<QvsHost>HIC-HP</QvsHost>
<TunnelHost>HIC-HP</TunnelHost>
You may need to check that, and that the port 80 (default by QlikView WebServer) is getting the expected result (I assuming it is, since the Accesspoint is returning documents), so my guess is again something related to port 4747 either in proxies or firewalls, since tunneling happens when this port is not available between Client and Server.
Hope that makes sense.
i will check that.
btw it could be that the client doenst have 4747 open, but in that case it will switch to tunneling (as mentioned in the error message) .. but tunneling is always using port 80 .. and that port is open (AJAX is working). why do you think this is a 4747 issue while tunneling?
Hi,
If Server is tunneling, it means it cannot access 4747 so indeed is falling back to 80, that dhould be opened. That may mean the "scripts" is not reachable by the user.
Although you've probably done already, check this post. When IIS is down, is the error returned the same (iis_authenticate etc)?
Regards.
Do you have a solution for this.If yes please share because we are having the same problem .Thanks