Qlik Sense QMC not working correctly failed reloads

[lanlizgu]

I have noticed lately that the Qlik Sense QMC is not working as expected.

I have a daily scheduled task to reload an app and that later reloads other two more apps on task event.

The thing is that although the QMC says that the app has not been correctly reloaded, If I go to the app and to the log it shows that it has been correctly reloaded

Moreover, as I have another task event, the last app is not reloaded because of this error.

This use to happen like once per week.

Thank you.

[lanlizgu]

It seems that the reload tasks of the Apps can have issues when uploading the file. In this case the app trying to be reloaded has a size of 1 GB and the tasks used to fail frequently.

By changing the "max retries" (it was set to 0 retries) of the App the issue is solved.

However, I can't understand how the QMC is not able to reload the app at first and needs up to 6 retries...

[lanlizgu]

I get the following error:

Sequence# ProductVersion Timestamp Severity Hostname Id EngineTimestamp EngineVersion Description ProxySessionId ProxyPackageId RequestSequenceId UserDirectory UserId SessionId ObjectId ObjectName Service Origin Context Command Result Message Id2

66 20.4.2.0 20180723T081838.450+0200 ERROR SES000A106688 8d86e6b8-01aa-4752-8f20-d9963727a30c 20180723T081838.459+0200 12.145.2.0 Command=Doc::DoSave;Result=9001;ResultText=Error: Read Failed 0 0 34797 INTERNAL sa_scheduler 1585f367-6507-4e8c-988e-f7acaab0202e 0 Not available Engine Not available Doc::DoSave Doc::DoSave 9001 Could not read app 8d86e6b8-01aa-4752-8f20-d9963727a30c

[lanlizgu]

The solution of Qlik for this issue was:

The warning to which you are referring - QVGeneral: when AAALR(1.293973) is greater than 1.000000, we suggest using new row applicator to improve time and mem effeciency. AAALR" is a very low level concept deep in the QlikView engine. Generally speaking it means the average length of aggregation array. The longer this array is, the more RAM usage and CPU power are to be consumed by the engine to get aggregation result for every hypercube node and can thus effect performance.

When AAALR is greater than 1.0, normally the customer has a large data set and suffers slow responses and high memory usage in their app.

To mitigate this, you can add the below setting to the Settings.ini file located in the QlikTech\QlikViewServer:

DisableNewRowApplicator=0

By setting this parameter to “0”, QlikView will use an new algorithm which is optimized for large data set to do the aggregation, and will consume much less RAM and CPU power.

[lanlizgu · Accepted solution]

I used the ProcMon over the folder where the .qvf are and notice that the antivirus real time protection was reading the files when the QMC was trying to save them, causing the error.

By adding the path to the antivirus real time protection exclusion folders it was fixed.

[Ranjanac]

How to check, that the antivirus real time protection was reading the files ?