Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Qlikview sessions time out on our users

Friends,

Please help us resolve this problematic issue.   Our Qlikview sessions are timing out in under an hour, though our server settings are set much higher (at least we believe we did it correctly).   We are on Qv 11 SR1 and all seems like all is working fine.   We are not using IIS, we are using Qlikview's web server.   Users use the Ajax client to connect to the server and view documents.  

When the sessions time out, users lose their selections which causes problems in longer meetings where the QV document is only referred to intermittently. 

We've set the following in QVS:  System -> Setup->Qlikview Servers->Performance

  • Maximum Number of Concurrent Sessions: 5000
  • Maximum Inactive Session Time: seconds:  10800 seconds
  • Possible Session Timeout: seconds 10800 seconds
  • Maximum Total Session Time:  (blank)seconds

We've set the following in QVS on the Document in question:   Documents -> User Document -> select the document - >  Performance

  • Maximum Number of Concurrent Sessions: (blank)
  • Maximum Inactive Session Time:  14400 seconds
  • Document Timeout:  240 minutes

Can anyone recommend a setting where we might have overlooked something?   

Thank You,

David Fields

479-549-7764

29 Replies
chriscammers
Partner - Specialist
Partner - Specialist

I found something in the web server config file and I am wondering if it is causing the issue but I have not found any documentation that makes any reference to it.

under the AccessPoint threre is a parameter  listed as <StatusRecheckInterval>60</StatusRecheckInterval>

So I wonder if this has something to do with the authentication and the webserver forcing another pass at authentication which in turn causes the Session to disconnect from the QVS.

I guess the only way to test would be to set this to a low level and see...

Chris

chriscammers
Partner - Specialist
Partner - Specialist

Anybody have any thoughts on DirectoryServiceConnector\resources ?

There is a guid named xml file in c:\programdata\Qliktech\DirectoryServiceConnector\Resources

There is a line in there with this <Entry Key="CacheExpiryInMinutes" Value="15" />

Could the expiration of the DSC cache cause the user's authentication to drop?

chriscammers
Partner - Specialist
Partner - Specialist

Ok none of those (testing on a Local VM)

how about the Session Recovery checkbox on the server on the Documents tab "Allow Session Recovery"

Bill_Britt
Former Employee
Former Employee

No, <Entry Key="CacheExpiryInMinutes" Value="15" /> is how offen it updates the directory information.

The issue is more than likely an IIS setting causing the issue. What does the QVS session log show the reason for the disconnect?

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
Not applicable
Author

Was this issued resolved? We seem to be having the same problem in our environment.

Not applicable
Author

Hi Bill, we are having the same issue.  The session log shows 'disconnected by client'.

Parallel to this issue, is there a way for QV to remember the last session selections when the session is terminated either by timeout or a user closing the session?

Thanks,

Paul

alexpanjhc
Specialist
Specialist

my client has the same issue and i've checked the server setting and document setting . There was nothing strange.

But I think it maybe related to the frequency of the reload?

If the user opened a document and then when the reload kicks off, the data got refreshed so the user will lose their older version and qlikview does not know what to do so it makes itself out.

it is just my theory and I am waiting for anyone who can second it.

Not applicable
Author

It's definitely not related to reloads in our environment.  We reload 2x's daily, and this issue can be reproduced throughout the day.

chriscammers
Partner - Specialist
Partner - Specialist

This one has been identified as defect 47449, I am currently waiting for a patch.