Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Clients losing connection and object selections after server reload

Hi,

We have an issue where clients lose connection and have their selections cleared when a reload is initiated from our QV server. If there are frequent reloads scheduled then this would be a user experience issue. Is there a way to prevent users from having their selections wiped out?

Thanks!

14 Replies
vidyut
Partner - Creator II
Partner - Creator II

Hi,

Check the Document Properties -> Server Tab where you could change the Refresh mode. That should help.

Not applicable
Author

I believe the Refresh Mode specifies where the refresh is initiated from (client/server) but there is nothing about clients not being disconnected during a server reload.

I am sure there are environments out there that reload on a frequent basis. Is there a standard way to do that without affecting the user experience?

Thanks.

Not applicable
Author

We are still getting behavior where random selections are being dropped. The Refresh Mode is set to "Server performs refresh automatically without client action." The "Enable Push from Server" option is selected. My understanding is that these are the selections needed in the document to allow client refreshes without client action, and without the clients having their selections wiped out.

Not applicable
Author

This is the same problem we are encountering.

We noticed that at the exact time (as verfied by logs) when the server completes a reload cycle - users who are logged in will experience long hangups that the only option would be to open a new browser and rebuild the selections (imagine when this happens during a presentation meeting).

This is casting too many doubts on the system's performance - since we want our data to be reload very frequently (to catch more updated information).

We don't think that the Server tab on Documents Settings is able to address this, but it also seems that this is where the adjustment should be made - as listed in the Refresh mode field...

Anyone found a workable solution for this, except scheduling reloads less frequently?

Not applicable
Author

We've had success using batch files that call ....\QlikviewDistributionService.exe with the path of the QVW file to reload as a parameter.

E.g. QlikviewDistributionService.exe" -r="[Qvw Path].qvw]" -out="[Log File Path].txt"

Then we scheduled this in the Windows Task Scheduler, and the dropping of selections seems to have stopped.

Not applicable
Author

Scratch that. The batch file workaround described above is still killing some of the selections

Not applicable
Author

We have noticed that the problem is not consistent. Some machines never have selections wiped out on a reload; others experience the problem with varying frequency. The machines where we have observed the problem have a higher network latency because of their physical location relative to the server.

Any updates would be greatly appreciated.

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

In addition to the Refesh options in Document settings, you must also uncheck "Allow only one copy of document in Memory" in the QVS settings. If that option is checked (default), users will get disconnected on reload regardless of the document refresh setting.

-Rob

Not applicable
Author

We are experiencing the same issues, and I am interested in applying this suggestion. However, how will unchecking the "Allow only one copy..." setting affect other aspects of user experience or Server performance?

Will this possibly lead to multiple document sessions open by the same user (in error)?

Thanks Rob for your input.