Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
We recently upgraded to QV12 SR4 and have been having a couple of issues ever since.
1) After a server refresh of the document each user is losing their filter selections.
2) When selecting "Remove last document state" from the AccessPoint this session doesn't remove from memory and the document retains your selections when you go back into it.
This is affecting all models on the server.
I'm not sure if these issues are connected but they would both appear to be related to the way in which Qlikview is holding the session detail at server level.
Has anybody else had this issue and come up with a workaround. QV11 had none of these problems?
Any advice?
Hi Darren, we're having the same problem with remove last document state. Did you ever find the solution?
Hi Darren,
For 2nd point (When selecting "Remove last document state" from the AccessPoint this session doesn't remove from memory and the document retains your selections when you go back into it)
I think you have to change the timed out settings on the IIS Server or Web Server.
Can you please navigate to the mentioned path and change the timeout settings accordingly with respect to your project.
C:\ProgramData\QlikTech\Webserver\config.xml
<QvsTimeOut> </QvsTimeout>
Thanks & Regards
Anand Sai
Hi Darren,
I've just noticed the same problem on an 11>12 upgrade, did you get anywhere with it? Feels like a bug introduced in 12 to me but keen to know if you got any further with it
Thanks
Joe
Hello,
This issue was reported to Qlik Support in the past as a potential defect and the issue was referred to Qlik R&D. The below is a statement from RD regarding the changed functionality of Remove Last Document from the v11.20 track to the 12/12.10 track:
|
Of course, while this sounds perfectly logical from a software design point-of-view, most users still get the impression that "it simply doesn't work". Moreover, the design and nature of www connections make the situation only more bewildering as there is no real "connection" concept during communications between a QlikView Server and a QlikView Client. Whenever a QlikView AccessPoint visitor closes the browser without pressing that famous small icon in the top right corner, everything on the client-side disappears without the QlikView Server having a clue about what is going on. The QlikView Server still thinks that a user session is active, and as long as the session timeout hasn't been exceeded, the session will stay alive.
There is no real escape from this situation (Server doesn't know that the client has disappeared, and the Client doesn't know that his/her session is still active), or is there?
Fortunately, there may be one. A long time ago, one of the bright Qlik minds devised a QlikView extension specifically targetted at handling this pseado-deadlock. The extension installs but shows no visible parts, and the only useful thing it attempts is to close the current session with the QlikView Server whenever the running browser gets a message to close down.
Document Extension to Terminate an AJAX Session
Only one thing: as it is quite old, I'm not entirely sure that it still works with QV 12.xx. Please post back if you get good results. Thanks
Thanks Peter, agreed from a user perspective this isn't good, I'll have a look at that extension as a work around
Joe