Today I had a report of the above message from a user, they had opened a QlikView document and had made three selections when they got a big cross over the object. They hit the refresh button that always comes with those big cross errors and then they got a server communication lost message.
When checking on the server stats immediately afterwards, we find that we are running critically low on memory and that the server is making extensive use of the paging file. We have 8 GB Ram on the Server and 2 processors.
We then found that a number of users are stated on the server as having multiple documents open, but when checking physically on their machines, they have only 1 open.
I cannot understand, in an installation where there are a maximum of 20 users logged onto QVW documents, that we are running out of memory, this must be a small installation compared to most.
Also, I don't understand why we are using 8GB of Ram when there are only 6 distinct QVW apps open at one time (even when all 20 users are logged on, they will still only be using the 6 apps).
The quick answer of course is going to be....... get 16GB of Ram on board, but actually, I'd really like to back up the request with some numbers to show why we need it, how much we need, when we might need more.
If anybody has any clues to help I would really appreciate it.
Will the mentioned setting (point 1 and 2) make any impact on the core problem. Or did you find any other solution. I am facing the same issue since long and not able to solve it.
Battling same problems on servers with 256 GM memory. Simplest solution is to put a script that will kill and restart the QVS service if using more than 95% of physical memory. Why? Because it is less downtime than waiting for users to complain and restarting it manually.
Sometimes Service Packs help, so it happens less often since upgrading to QV9. But there are hundreds of QVW files, and it is extremely difficult to identify unknown formulas causing this behavior
