topic Clients losing connection and object selections after server reload in QlikView

Clients losing connection and object selections after server reload

Mon, 26 Jan 2026 18:19:17 GMT

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!

Clients losing connection and object selections after server reload

vidyut — Thu, 04 Feb 2010 18:47:31 GMT

Hi,

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

Clients losing connection and object selections after server reload

Thu, 04 Feb 2010 19:02:06 GMT

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.

Clients losing connection and object selections after server reload

Mon, 22 Mar 2010 13:35:49 GMT

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.

Clients losing connection and object selections after server reload

Mon, 22 Mar 2010 14:01:55 GMT

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?

Clients losing connection and object selections after server reload

Mon, 22 Mar 2010 14:33:20 GMT

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.

Clients losing connection and object selections after server reload

Mon, 22 Mar 2010 14:49:42 GMT

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

Clients losing connection and object selections after server reload

Wed, 31 Mar 2010 14:54:54 GMT

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.

Clients losing connection and object selections after server reload

rwunderlich — Wed, 31 Mar 2010 16:04:23 GMT

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

Clients losing connection and object selections after server reload

Mon, 05 Apr 2010 22:52:01 GMT

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.

Clients losing connection and object selections after server reload

rwunderlich — Tue, 06 Apr 2010 01:52:11 GMT

Tyler,

Unchecking the option can increase the RAM usage of the server. WIth the option checked, there can only be one version of a qvw ("Sales.qvw") in server memory. With the option unchecked, you can wind up with multiple versions of Sales.qvw loaded into memory.

UserA - opens Sales.qvw (call this version 1).
Scheduled Reload for Sales.qvw runs creating a "new version 2".
UserB opens Sales.qvw -- will get current version which is now Version 2.

Both version 1 and version 2 are in RAM, occupying twice the RAM of a single copy.

Is it possible that a single user could have both versions open on different screens? It's possible, depending on which client is used and how the open is done. However, the screen containing the first version should get an automatic refresh or refresh notifcation --depending on document option.

-Rob

Clients losing connection and object selections after server reload

Tue, 06 Apr 2010 19:14:18 GMT

Hi guys,

We've tried out Rob's suggestion for a week now. In my view, the combination of keeping more than one copy in memory and prompting the user to refresh the data when they are logged in - is a passable workaround. At the least, it keeps them from being surprised rather.

Although, we have a working recommendation to always select "No' once the refresh prompt is encountered, since the refresh time takes too long.

We could also afford this since we are using a single document (but really big) to consolidate our data... we may change settings if we decide to have more documents.

It's too bad that there seems to be no way not to refresh the data at all (or is there?).

Also, thanks Rob, for the insight about the effect on RAM usage of multiple versions of the file - this really helps us learn and monitor system performance in relation to usage loads.

Re. :Re: Clients losing connection and object selections after server reload

Fri, 18 Jun 2010 17:27:55 GMT

Hi Rob, I am trying to put in place a process that let the user decide to refresh the data while he is performing selections.

I tried to use the prompt dialog and have the one version unchecked , but it does not seem to work using Aajx .

Is there any other solution ?

Thanks

Philippe

Re: Clients losing connection and object selections after server reload

Thu, 23 Aug 2012 20:19:17 GMT

What happens to the in server memory if a new document is added to the server? I have noticed that it does update the access page, but was curious about how it effect the RAM.

Re: Clients losing connection and object selections after server reload

p_verkooijen — Fri, 25 Oct 2013 17:19:21 GMT

If user 1 with the "old" data closes his session the "new" document will not be loaded into RAM untill someone opens it.

If user 1 is still analyzing, and a user 2 opens the document both documents will be loaded into memory.

depending on the number of users and reload schedule, there could be even more than 2 documents in memory.

if the refresh takes to long, maybe you could set the document as preloaded. However I'm not sure this works in combination with allowing multiple versions in memory.