The QlikView Server Session log logs Exit Reasons for Sessions being closed or unexpectedly terminated.
Environment:
QlikView any version
Session expired after idle time
Maximum inactive session time has expired after last user click.
The session timeout is configured in the QlikView Management Console > System > Setup > QlikView Server > QVS@SERVER > Performance
Session expired after elapsed time
Maximum allowed session time has expired.
This can be configured in the QlikView Management Console > System > Setup > QlikView Server > QVS@SERVER > Performance
As well as the .qvw document directly: Document properties > Server > Maximum Total Session Time.
The shortest timeout will always apply.
Socket closed by the client
User clicks "Close" button in the top right of AJAX page OR the webserver disconnects the session.
Killed because Named User Cal was needed from another client
Another user session is being opened against an already active Named User CAL, but from a different client or machine.
For more information, please refer to A QlikView Session is terminated and the Session log reads "Killed because Named User Cal was needed...
.png "Former Employee"){kind=icon}
