topic Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon in QlikView

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Mon, 26 Jan 2026 18:19:17 GMT

The memory held by QVS keeps rising because QVS keeps loading already loaded docs into memory for two users.

Specs:

Qv Server 8.5
Server: 64bit, 256GB RAM, 4 8-Core hyperthread CPUs
Windows Server 2008 R2
IE Plugin Client 8.5 (latest release)

Here's the log seeing the following in the QVS EVENT.log:

EventID	Message	Severity	Timestamp
302	CAL usage: Named CAL "LEINTERNAL\TLWATER" unused - remaining count = 0.	Warning	2010-10-22 12:59:29
302	CAL usage: Named CAL "LEINTERNAL\TLWATER" unused - remaining count = 1.	Warning	2010-10-22 12:59:12
302	CAL usage: Named CAL "LEINTERNAL\ACJOHAN" unused - remaining count = 0.	Warning	2010-10-22 12:54:57
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.	Information	2010-10-22 12:47:40
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.	Information	2010-10-22 12:46:06
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.	Information	2010-10-22 12:44:30
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.	Information	2010-10-22 12:43:28
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.	Information	2010-10-22 12:42:08
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\LE@SEARS V2.QVW was loaded.	Information	2010-10-22 12:40:50
302	CAL usage: Named CAL "LEINTERNAL\ACJOHAN" unused - remaining count = 0.	Warning	2010-10-22 12:38:50
302	CAL usage: Named CAL "LEINTERNAL\ACJOHAN" unused - remaining count = 1.	Warning	2010-10-22 12:38:50
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\Z_QA RETURNS APPLICATION_024.QVW was loaded.	Information	2010-10-22 12:35:45
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\Z_QA RETURNS APPLICATION_024.QVW was loaded.	Information	2010-10-22 12:34:21
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\Z_QA RETURNS APPLICATION_024.QVW was loaded.	Information	2010-10-22 12:32:53
108	The document \\USAP024\SERVERMOUNTEDQVWFILES\Z_QA RETURNS APPLICATION_024.QVW was loaded.	Information	2010-10-22 12:28:59

We can't put users on this new server until we can resolve this. Any ideas?!

Thanks, Tyler

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Bill_Britt — Sun, 24 Oct 2010 00:18:25 GMT

I would question to start if this is a new server why are you installing 8.5. Support for this version will end next year. I have never seen this error before. You might want to contact support for help.

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 09:39:58 GMT

Hi bbt,

Can you please provide an official source for this? I was not aware of End of Support for 8.5 in 2011.

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 15:49:18 GMT

Tyler,

I have a similar problem on 9.0. I currently have 21 users, 31 sessions and 111 loaded docs. The loaded docs are using up all my memory which eventually leads to server crash.

I did uncheck "Allow only one copy of document in memory" (because we had a lot of delay in the user experience) and that is when the memory usage skyrocketed . So I'm wondering why the loaded docs never flush?

If "Allow only one copy of document in memory" is checked the problem goes away, but the user experience is degraded.

Did you get your issue resolved?

Thanks

Jim

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 16:02:07 GMT

Jim,

QlikView Server has a 'feature' in which the memory does not flush -- it keeps growing and growing as you republish documents. This is especially the case when you do not prevent 'only one doc in memory' by unchecking that option.

This is a separate issue than what my original post was about. This memory 'leak' has been around in our environment from the beginning, and we were encouraged to restart the QlikView Service regularly to 'reset' the memory level. So, we setup a windows scheduled task on each of our production servers to restart the QVS Service every morning at 2am.

The problem I am facing is a different issue in which one document keeps getting loaded again and again and again until the memory maxes out. This happens in a matter of minutes, not over days like the 'normal' memory leak does.

Hope this helps.

Tyler

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Anonymous — Wed, 02 Mar 2011 16:07:35 GMT

What is you "Document Timeout:" set to? You may want to shorten this up to get rid of unused loaded analytics.

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 16:18:22 GMT

480 minutes. However, the other timeout settings are set to 3 or 4 hours, which would accomplish the same thing, correct?

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 16:25:32 GMT

My document timeout was 60 mins I just changed it to 30 mins - I have a 5 min reload time however.

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Anonymous — Wed, 02 Mar 2011 16:31:39 GMT

I have our Document Timeout set to 15 minutes. I would say the shorter the better if you have unchecked 'Allow only one copy of document in memory'.

Tyler, I am not sure this will fix your issue.

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 16:31:55 GMT

Forgive my ignorance, but what does the Document Timeout setting actually do?

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 16:32:58 GMT

Hi Tyler,

Document Timeout (minutes): "30" preserves the document in the memory for 30 minutes from the time the user is not (!) using it anymore. So if this user reopens it within the next 30 mins (lets say 28 minutes) it opens quicker, as it does not require to be reloaded into memory. Thus it was "wasting" RAM Memory for 28 minutes for the benefit oft reopening faster, if the user needs it again. If it is not reopened, it was wasting the ram for 30 minutes for nothing.

At least that is the way I understand this option.

I have set the Document Timeout (minutes) value to 2 minutes.

The other timeout options should rather not be set to such short periods like 2 minutes as this will kick users, when they do their coffe break!

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 17:15:34 GMT

So if document timeout is 30 mins - in my case - why are my loadedDocs rising every time a reload is done? Is this timeout for "LoadedDocs" ? I am getting 12 LoadedDocs added every hour (60/5= 12 on a 5 minute reload) I have gone from 111 to 123 in past hour for instance - why wont they time out?

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Anonymous — Wed, 02 Mar 2011 17:25:39 GMT

Have you restarted the QV Services after making the "Document Timeout" changes? If not, I believe you will need to restart to make the new value live.

Also, the document must be idle for 30 minutes. If they are in use they will not go away.

Server 8.5 keeps loading already loaded docs (ID 108); Memory keeps climbing; Will crash soon

Wed, 02 Mar 2011 18:37:58 GMT

Thanks - I have just restarted it - so I will see how it progresses for the day.