QlikView Server goes Down Error

[Manish_Kumar_]

Hi Community,

Currently I am using both QlikView and Qlik Sense on separate physical servers.

My issue is that QlikView Server hangs most often when memory goes high and whereas Qlik Sense Server retains its position evn if RAM is high say above 90. it never hangs or stops..

Now Can i do something to avoid QlikView Server hangs like It should manage the operations in such way that the Qlik Sense does!!.

Any kind of suggestion will be appreciated..as it is major headache for our organization!

[Bill_Britt]

Hi,

Without seeing the logs it would be hard to say. Adding resources is an option.

[Chip_Matejowsky]

Hi @Manish_Kumar_

Both QlikView and Qlik Sense are "in-memory" based analytical tools. So the amount of RAM a server has that's running these applications is of vital importance. You can check the QlikView system requirements to ensure your QV server meets these requirements. Keep in mind that the data sets you are working with can necessitate that you have more RAM than the system requirements specify.

Suggest that you start by reviewing the following Qlik Support articles:

• QlikView AccessPoint shows No Server and Virtual Memory warnings are logged 
• QlikView: Organized way to troubleshoot "No Server" error 

If you need assistance in deciphering the logs, please let us know here.

Best Regards

[Manish_Kumar_]

Hi @Chip_Matejowsky 
I have gone through the links you have provided thanks for them, but that's not the concern here..

The links you have provided have information when the access point of qlikview server goes down..but my requirement is the physical server on which qlikview is installed has around 756 GB of RAM which goes down and requires a restart when its memory goes high..whereas in Qlik Sense it has same RAM 756 GB but it never goes down as no matter how much it is loaded, It peaks at 90% and retains its position by slowing down its processes..Same i want in Qlik View Server ..as if there is any settings file where i can set thresholds for memory usage or do something else which can provide server hangs!!!! 

[Manish_Kumar_]

hi @Bill_Britt ,

Please specify what logs should i provide you to get this solved!!

Would like to mention that it's a major issue in our organization and I'm sure it would be helpful enough for others too who are using the Qlik View tool as their BI Reporting tool...

Also, RAM specs are good enough to handle the data in our organization but whenever there is a code fault or too much load on the server, a large enough RAM will also go to the peak. So there should be an option to  set the threshold to provide server hangs

[Chip_Matejowsky · Accepted solution]

@Manish_Kumar_,

There are dozens of potential root causes for these issues, so suggest you start by reviewing the QlikView Server Event logs for errors and warnings pertaining to restart and/or RAM consumption (step 13 in article provided).  You have to first understand the potential causes. QlikView and Qlik Sense both utilize the QIX engine but are different products and environmental architecture is certainly a concern. 

Best Regards

[Bill_Britt]

Hi,

The QVS event logs are the ones to look at.  Default location is C:\ProgramData\QlikTech\QlikViewServer.


https://community.qlik.com/t5/Knowledge/Qlik-Engine-Memory-Management/ta-p/1710559

[marcus_sommer · Accepted solution]

The QlikView server services has with the working set configuration a possibility to restrict the RAM consumption. Each other QlikView service has not such setting and will compete for the available RAM. It's especially relevant for the distribution service but also for each third party tool as well as the OS. Beside this there are various settings for timeouts, keeping multiple versions of an application within the RAM, pre-loading applications and so on ...

As far as your running tools hit the RAM consumption of 90% - 95% of the available RAM you will risk to get an unstable system because the OS needs also some resources. Not quite so risky is the CPU consumption - frequently peaks of 100% are intended and no issue but a long term consumption of 100% of dozens of minutes could also prevent that QlikView and OS services are working properly and running into any errors or timeouts.

Quite often you could monitore this already within the task-manager and getting a lot of hints which tools/processes are responsible. To dive deeper you could then investigate the above mentioned various log-files - especially the event/performance-logs from QlikView and OS.

If you then know some of the potential causes - probably there is more as a single one - you could decide to adjust any configuration and/or optimizing the applications and/or removing third-party tools and/or distributing the QlikView services to several nodes and/or adding more hardware resources (RAM + CPU but also network/storage performance because a RAM swapping is always bad but it's a huge difference if the swapping happens against a ssd or a hd).

- Marcus