Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsThe reason why a user session got closed is visible in the logfile SERVERNAME_Audit_proxy.txt in path C:\ProgramData\Qlik\Sense\Log\Proxy\Trace.
Basically there are 2 reasons why a session could be closed:
1. User logged out
When a user actively logged out from the system the following string is visible in the logfile: "has logged out"
Example
20190416T162209.965+0200 INFO QlikServer1 Audit.Proxy.System.Reflection.RuntimeConstructorInfo 5 90770f69-9d28-421e-82fa-9658245a7465 DOMAIN\QvService User DOMAIN\user has logged out 296bf969-d8db-47f5-be53-b2c93bf70d94
2. Session timed out
When the session was closed by the system due to a session timeout the following string is visible in the logfile: "has been deleted due to inactivity"
Example
20190416T160754.387+0200 INFO QlikServer1 Audit.Proxy.Proxy.SessionEstablishment.Session.MetaSession 8 24b363f6-8e2f-4430-bf8a-b57a300ddacf DOMAIN\QvService Session 61f37493-f134-4aca-bc76-2f7c633c3028 has been deleted due to inactivity 61f37493-f134-4aca-bc76-2f7c633c3028 DOMAIN user
Note:
If the user closes the browser window without logging off, the session will be closed as soon as the session timeout (default 30 min) is reached.
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsSearch Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a caseExperiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us