Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Our user do connect to our local network trough DirectAccess (http://technet.microsoft.com/en-us/network/dd420463.aspx)
but our Qlikview documents can not be opened. The connection to the server is not accessable. Anyone who has any experience from Qlikview and DirectAccess?
The summary of our problem by QlikSupport back then Mar 2015:
"The Problem mainly is related to the access of a QlikView Application from external with the Internet Explorer PlugIn through Direct Access.
- First point is the limitation of the PlugIn only supporting IPv4 and Direct Access using IPv6 what can cause issues in the Connection.
- Second Point is that the Tunnel Configuration for IIS only works with one QlikView Server and it is not possible to address a QlikView Cluster.
With the given requirements (Direct Access, IE PlugIn and IIS) the main issue is the first Point where the use of the PlugIn with Direct Access need a Tunneling Connection to work. This is working with the limitation of missing Cluster functionality as each IIS has a dedicated QlikView Server. For this issue we opened a Problem Investigation at our Development Department and waiting for a Response."
No idea if something changes since then. We moved to using only Ajax client since then.
Have you tried using the AJAX (Full Browser Version) to open documents?
Anything new to this topic? It seem, that we have the same issue.
Hi Samir,
Are you using NTFS or DMS mode ?
Is there any Firewall which could block ?
What is the error message ?
best regards
Chris
Hi christianj,
we are using NTFS,
Firewall is off on all servers in the cluster,
error message:
qvp://qvsserver//..../application.qvw?
iis_authenticate=longnumber&charcombinationBAD&tunneler=htttp://accesspoint&2Fscripts%2FQVSTunnel.dll%3Fhost%3Dqvsserver could not be opened
Best Regards
Rafael
Hum...
it seems you're using IIS
May be this doc from Sokkorn Cheav will help you about IIS and tunneling
Chris
Was this problem ever solved?
We have a similar problem.
We are not using IIS
The same problem with both full browser client and Open in Server
DirectAccess was working on old server (WS 2008, QV11) before upgrade (WS2012, QV12)
telnet <server> 4747 works over DirectAccess
The summary of our problem by QlikSupport back then Mar 2015:
"The Problem mainly is related to the access of a QlikView Application from external with the Internet Explorer PlugIn through Direct Access.
- First point is the limitation of the PlugIn only supporting IPv4 and Direct Access using IPv6 what can cause issues in the Connection.
- Second Point is that the Tunnel Configuration for IIS only works with one QlikView Server and it is not possible to address a QlikView Cluster.
With the given requirements (Direct Access, IE PlugIn and IIS) the main issue is the first Point where the use of the PlugIn with Direct Access need a Tunneling Connection to work. This is working with the limitation of missing Cluster functionality as each IIS has a dedicated QlikView Server. For this issue we opened a Problem Investigation at our Development Department and waiting for a Response."
No idea if something changes since then. We moved to using only Ajax client since then.
Hello,
We encountered similair problems and it took us a long time to get it working for us. Initially we were using IIS for the qlikview webserver and we couldn't use the IE plugin or the desktop client from remote locations through Microsoft Direct Access. The Ajax version worked just fine but we wanted to use either the IE plugin or the desktop client because of key functionality build with macro's (which are not working in the Ajax client). Eventually we got the IE plugin to work from remote sites through MS Direct Acces with help from qlik and our qlikview dealer. The solution was to switch to the Qlikview webserver instead of using IIS and also to select the "always tunnel" option (QMC -> System/Setup/QVW@hostname/Accespoint/Server connections) to force tunneling. The Desktop client still isn't working from remote sites though. I hope this solution helps someone in dealing with the same problems.
Kind Regards,
Timo