topic Re: qlikview unresponsive. in QlikView

qlikview unresponsive.

Anonymous — Mon, 26 Jan 2026 18:19:17 GMT

Hi experts,

4.39am qlikview goes unresponsive. I see the below:

4.39am: goes unresponsive… we see from the browser the "no connection" message.

Before that this happened

4.38am…

WorkingSet: Virtual Memory is growing CRITICALLY beyond parameters - 87.035(60.000) GB

WorkingSet: Virtual Memory is growing beyond parameters - 68.233(60.000) GB

WorkingSet: Virtual Memory is growing beyond parameters - 65.268(60.000) GB

WorkingSet: Virtual Memory is growing beyond parameters - 63.234(60.000) GB

WorkingSet: Virtual Memory is growing beyond parameters - 60.291(60.000) GB

Extensions: Failed to load extension EnglishtownColor. Make sure it is available at the correct location

4.37am…

QVGeneral: Error Extensions: Failed to load extension EnglishtownColor. Make sure it is available at the correct location.

Extensions: Failed to load extension EnglishtownColor. Make sure it is available at the correct location

QVGeneral: Error Extensions: Failed to load extension EnglishtownColor. Make sure it is available at the correct location.

QVGeneral: Shared - ApplyBM: Could not update the Recall time on bookmark with id: Document\BM07

Extensions: Failed to load extension EnglishtownColor. Make sure it is available at the correct location

4.36am…

QVGeneral: Error Extensions: Failed to load extension EnglishtownColor. Make sure it is available at the correct location.

Extensions: Failed to load extension EnglishtownColor. Make sure it is available at the correct location

CAL usage: Using CAL of type "Document" for user "BOSTON\FEDERICA.TTTT". Document cals in use: 1

QVGeneral: when AAALR(20.136368) is greater than 1.000000, we suggest using new row applicator to improve time and mem effeciency.

4.35am…

QVGeneral: when AAALR(20.136368) is greater than 1.000000, we suggest using new row applicator to improve time and mem effeciency.

4.32am…

QVGeneral: Shared - ApplyBM: Could not update the Recall time on bookmark with id: User\BM12

License: License leased to user DIR\PTUNE.ADMIN

A device or program has requested attention. Device or application: C:\Windows\SYSTEM32\ntdll.dll. Message title: QlikView x64.

How can I prevent this happening again? This is production; shouldn’t be happening; if this is caused by one report, how can I know which report is that?

Re: qlikview unresponsive.

marcus_sommer — Thu, 01 Dec 2016 14:41:19 GMT

It looked that something consumed all your RAM which then led to errors and unresponsiveness. I think you should take a look within the qlikview logs: QlikView Governance Dashboard and in the windows eventlog.

- Marcus

Re: qlikview unresponsive.

Anonymous — Thu, 01 Dec 2016 15:09:52 GMT

I restarted the server... are the logs still available?

all the above is from windows eventlog; where can I find Qlikview logs? (can you provide the default windows path for the qlikview logs?)

thanks!!

Re: qlikview unresponsive.

marcus_sommer — Thu, 01 Dec 2016 15:17:57 GMT

You could find those logs: \\YourServer\D\QlikViewServer\ProgramData\QlikViewServer and replace the bolded part with your server and path to the program data.

- Marcus

Re: qlikview unresponsive.

Anonymous — Thu, 01 Dec 2016 16:55:57 GMT

can't find them... I do not see any folder named QlikViewServer

Re: qlikview unresponsive.

marcus_sommer — Thu, 01 Dec 2016 20:10:37 GMT

The logs aren't within the Program Files else within the ProgramData.

- Marcus

Re: qlikview unresponsive.

Anonymous — Fri, 02 Dec 2016 14:40:06 GMT

You specified this windows path

YourServer\D\QlikViewServer\ProgramData\QlikViewServer

as you can see there is neither QlikViewServer nor ProgramData

Re: qlikview unresponsive.

marcus_sommer — Fri, 02 Dec 2016 15:39:53 GMT

Take a look here C:\ProgramData for the ProgramData folder.

- Marcus

Re: qlikview unresponsive.

Chip_Matejowsky — Fri, 09 Dec 2016 21:09:26 GMT

The WorkingSet: Virtual Memory is growing CRITICALLY beyond parameters and WorkingSet: Virtual Memory is growing beyond parameters errors indicate that your server is running out of memory.

You'll want to ensure that you set your QlikView Server logging to High Verbosity and split the log files daily, ensuring that you have most information in the logs and they are easily digestible. In QMC, navigate to System > Setup > QlikView Servers > QVS@ > Logging tab to apply the settings.

Suggest you use the Systems Monitor application QlikView Application: System Monitor v5.1.23 to collate these logs and review them to assist in providing some insight into what is causing the high memory consumption.

If this issue began to occur "out of the blue," then you may have an end user created object causing the issue. Suggest you contact Qlik Support for assistance with this issue.