On the QV9 SR4 AccessPoint, using the IE Plugin 9SR4 (Windows XP / IE8), our users often get the attached dialog box ("Connect to server") when they try to open a QV document.
They just have to confirm the default authentication mode ("Use NT Identity") and clik on OPEN, and everything runs fine.
If they wait long enough on the Accesspoint before actually opening a QV document (10-15 sec.), this dialog box does not even show up.
Seems related to a protocol switching during the client-server authentication process, after a time-out is reached.
Is there any way we could configure our QV web server to get rid of this useless dialog box ?
We suspect this annoying dialog box ("Connect to server") does only appear if the user tries to open a document before this automatic switch to HTTP tunneling (less than 10 sec).
Any idea on how to force the QV web server to immediately switch to HTTP tunneling ? A delay parameter to modify somewhere in the config files ?
Thanks for your help,
You can go into the config.xlm file (located at C:\ProgramData\QlikTech\QvWebServer) and set <alwaystunnel> to true. However, first setup the Webserver in the QEMC because changing anything there after you change the above will set it back to false.
Thanks for your answer, Bill.
However, after checking with our It dept, looks like we are using IIS as web server.
-> In which config file can we find this "alwaystunnel" parameter for a IIS setup ?
This is going to take a little more work. That setting will work with IIS, but you have to setup IIS to support it.
This document will should you how to do it in IIS 7.
Everything is running as described in the doc you sent : I can see the "Qlikweb Service HTTP Tunnel Available".
However, this doc still refers to the file "config.xml" to alter the <alwaystunnel> parameter, but this config.xml file is nowhere to be found in an IIS setup.
Any idea ?
I read in the QVS 11SR2 Reference Manual that "Tunneling is used by Windows native clients (Qlikview Desktop, OEM OCX, Internet Explorer Plugin)" (page 35)
Is it also true in QV9SR4 ?
Is tunneling the only way to connect the IE Plugin to a QVServer ?
I thought the Plugin could get a direct QVP connection to the QV Server, with no Web server involved (except the Access Point home page, of course)
Thanks for your help,
Tunneling is used if the OCX or Plugin can't talk to the QVS on port 4747. However, Tunneling has to be setup if you are using IIS.
The plugin can talk to QVS on port 4747.
However, you must be right regarding IIS : the frame source behind any QV document on the Access Point shows that a tunneled connection is forced between the plugin and QVS :
-> as tunneling is forced, I can't see why the plugin still has to negociate with the server (see attached Qlikviewerror file).
I suspect this negociation step to be the cause of the initial message box we want to get rid of. (see this line in the log : Server did not respond inside timeout: "")