Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hey Qlikers,
We are experiencing an issue with Qlikview 12SR4. When we disable session recovery in QMC, our AJAX sessions retain the users last selections. This happens when we use Chrome. Has anyone else experienced this issue? IE plugin has no issue with session recovery but AJAX seems to retain these "Sticky" sessions.
P.S. We are unable to upgrade and have a few ideas for a workaround. We are looking for solutions or whether or not this is a known issue in this version. Thanks in advance.
Hello!
This might not be Session Recovery, but a not yet closed session.
Maybe a little more background helps:
Session Recovery functions by creating a bookmark when the user closes their session or when the session times out. This bookmark is called a LastKnownState bookmark. The End User and Admin cannot access this through the QMC. It is only visible in the .shared/.tshared file. This bookmark grabs all the currently active selections after a session is terminated properly (this bit is important).
A session for AJAX is closed in one of two ways:
Closing the browser window or hitting the back button does not close the session.
Afterwards, it might still be necessary to Remove last document state so that the currently saved LastKnownStateBookmark is discarded.
That is done in the AccessPoint by clicking on View details.
And that was Session Recovery.
If you aren't sure if it was disabled correctly (for example if you have a Cluster and the settings are not correctly saved to all nodes), you can check the settings.ini file of the individual Qlikview servers.
Locate the settings.ini file in c:\programdata\qliktech\qlikviewserver and verify if the settings.ini file includes ProhibitQvpxSessionRecovery=1
What AJAX also does though is that it resumes a currently active session. That is not Session Recovery, as no bookmark is created. So, a document is closed by hitting the back button on the browser or the browser/tab is closed. The session is still active until it times out. Until then, whenever the user opens the document again, they'll pick up where they left off since the server still has all their data cached.
Another possibility would be that the document was saved with those selections, but that does not apply in your case, since you are not seeing the behaviour in the Plugin (just noting that here in case someone else needs this information).
I hope that this is able to help a little.
Hello!
This might not be Session Recovery, but a not yet closed session.
Maybe a little more background helps:
Session Recovery functions by creating a bookmark when the user closes their session or when the session times out. This bookmark is called a LastKnownState bookmark. The End User and Admin cannot access this through the QMC. It is only visible in the .shared/.tshared file. This bookmark grabs all the currently active selections after a session is terminated properly (this bit is important).
A session for AJAX is closed in one of two ways:
Closing the browser window or hitting the back button does not close the session.
Afterwards, it might still be necessary to Remove last document state so that the currently saved LastKnownStateBookmark is discarded.
That is done in the AccessPoint by clicking on View details.
And that was Session Recovery.
If you aren't sure if it was disabled correctly (for example if you have a Cluster and the settings are not correctly saved to all nodes), you can check the settings.ini file of the individual Qlikview servers.
Locate the settings.ini file in c:\programdata\qliktech\qlikviewserver and verify if the settings.ini file includes ProhibitQvpxSessionRecovery=1
What AJAX also does though is that it resumes a currently active session. That is not Session Recovery, as no bookmark is created. So, a document is closed by hitting the back button on the browser or the browser/tab is closed. The session is still active until it times out. Until then, whenever the user opens the document again, they'll pick up where they left off since the server still has all their data cached.
Another possibility would be that the document was saved with those selections, but that does not apply in your case, since you are not seeing the behaviour in the Plugin (just noting that here in case someone else needs this information).
I hope that this is able to help a little.
... and I forgot to ask: You specifically mentioned Chrome. Has this been tested with another browser?
This is exactly what we were looking for! Your explanation was excellent. Thank you for your help.
Glad to be of help 🙂
If the information was useful and helped answer your question, please mark it as resolved once you're confident it's sufficient. This will help other users later on reuse this with confidence!
/Sonja