Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We have a new Qlikview Configuration where the Webserver is in the DMZ using IIS, and all other Qlikview Services are run on it's own server. All the ports have been opened between Web Server & App Server that are necessary. When looking at the firewall traffic for any blocked ports while attempting to access the application, there are none. IIS is siteminder protected DMS mode using LDAP.
After about 60 seconds, (roughly, not exactly) the client reports the connection has been lost, reconnecting. When it reconnects, there is no communication between the web server & app server. So it seems it's referring to the connection between the Browser (AJAX) and the webserver. We can't seem to determine the cause of this message, and how to prevent it from appearing. The entire document is loaded on my local browser, and it's not dynamically updated, but still this error seems to occur.
Any thoughts? There are plenty of licenses, and everyone is using different logins. Timeout settings are all well above 60 seconds. I've browsed these forums for days, and couldn't find anything that worked related to these symptoms.
FYI, this issue was being caused because of Siteminder.
We configured the web agent to disable the cookie provider in the LocalConfig.conf
cookieprovider=""
Try this
File C:\Documents and Settings\All Users\Application Data\QlikTech\QvWebServer\config.xml
contains a line <QVSTimeout>60</QVSTimeout>
hope this helps
Set that to 600, still same issue.
add your url to trusted site in Inernet Explorer prperties
Thanks. Have already tried this, and it's happening in all browsers and devices. It's protected by an SSL Certificate through VeriSign.
Do you have any Authentication layer like SSO which has a session time out and impacting the QlikView user session?
check the session timeout on the QEMC.
We're using siteminder, however, it's not timing out the session, we can refresh the page, and the session is still good.
Session timeout settings are way above normal. We increased this as the first troubleshooting step. Also increased the timeout in the document itself.
FYI, this issue was being caused because of Siteminder.
We configured the web agent to disable the cookie provider in the LocalConfig.conf
cookieprovider=""