Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Aug 31, 2021 3:38:55 AM
Sep 12, 2017 5:21:49 PM
Opening or navigating a QlikView application with the Full Browser client leads to Lost Connection, Reconnecting. or Session Lost. This is often caused by large documents or complex calculations that take longer then the configured timeout.
Reviewing the QlikView WebServer log files located in %ProgramData%\QlikTech\WebServer\Log shows
The same behaviour is not seen when using the Internet Explorer plugin. The problem can occur for both the QlikView WebServer and Microsoft IIS.
Environment:
This issue may happen if the document contains complex formulas/calculations, or the data set is too large for the standard timeout.
The Internet Explorer plugin communicates directly with the QlikView Server, while the Full Browser Client (AJAX) communicates with the webserver first. Different timeout values apply.
QlikView WebServer, as well as Microsoft IIS, have a timeout value at a default of 60 seconds.
There are different timeout values that can be adjusted to allow the webserver to wait for a return from the QlikView server longer, as well as to allow calculations more time to complete. Keep in mind that it is recommended to tune these settings to an appropriate level based on your environment. The settings used in the examples below are based on very large applications.
(November 2017 and later)
Increase SocketTimeOutInSeconds value.
If using QlikView Web Server:
If using IIS:
The configuration file that shows the current value can be found in C:\inetpub\wwwroot\web.config on a default installation.
(All previous versions of QlikView)
Increase QvsTimeout value.
Increase Object Calculation Time Limit in the QlikView Management Console (QMC). Default is 60 seconds.
In the QlikView Mananagement Console, navigate to System > Setup > QVS@node > Performance tab
Modify the Object Calculation Time Limit.
This will prevent the Full Browser Client to reconnect to a previous session and may help with stability. It will not adjust any timeout values, however.
In the QlikView Mananagement Console, navigate to System > Setup > QVS@node > Documents tab
Uncheck the Allow Session Recovery box.
Increase execution timeout in the Configuration Editor of IIS Manager.
Navigate to the WebSite which has QlikView installed and open the Configuration editor.
All the above is tried several times, with many alteration on the server config, QMC and even Qlikdesktop, and nothing worked!! The weird part is the connection issue is appearing from the Accesspoint from the same server, and maybe we should check other attributes that are causing this issue and not the network or the session timeout?
if you have any updates on this topic, I would appreciate if you can share cz this is getting stressfull
Hello @Jihad
The steps provided in this article may not cover all possible root causes, as this behaviour can be caused by a number of issues, such as:
Here are some other articles that may help you identify the issue, but I would begin with reviewing the log files when you see the issue. You may also want to post about the problem for further investigation in the appropriate forum: QlikView Administration.
Troubleshooting QlikView Server resource problems
QlikView: Organized way to troubleshoot "No Server" error
All the best,
Sonja
i am facing this issue mainly when i log with the same user logged on on a different browser on a different pc to the same dashboard . Iknow it is logical but do you know why it's clearing out filters once the warning tab is gone ?
Hello @grgabj
The warning comes from you kicking your user out with the second session and is expected. In this case, the loss of the filter can be down to the session not being recoverable or you picking up the previous session. Generally speaking, QlikView will attempt to continue the existing session or fall back onto a session recovery bookmark.
All the best,
Sonja