topic Script log file not available in C:\ProgramData\Qlik\Sense\Log\Script folder or Archived folder in Management & Governance

Script log file not available in C:\ProgramData\Qlik\Sense\Log\Script folder or Archived folder

sudhakar_c — Tue, 19 Oct 2021 04:19:26 GMT

Hi,

We have few tasks which execute successfully on daily basis. These tasks are triggered using Control M via API integration. But after task completion log files are getting deleted. We are using Qlik Sense NOV2020 edition, a multinode setup and integration with Control M for tasks orchestration.

While task execution script log file for the app is created and information is written to it till the completion of task. But as soon as the task completes the log file is deleted from the ProgramData location. The file is not available in the Archived folder also. The file is deleted as soon as the execution is complete. I monitored the file using Windows Process Monitor attaching the screenshot to see which all processes are touching the file.

How do I debug this issue? Any specific log entries to be checked in the engine/repository to know why it is getting deleted?

Regards.

Re: Script log file not available in C:\ProgramData\Qlik\Sense\Log\Script folder or Archived folder

Alexis_Touet — Tue, 19 Oct 2021 06:27:27 GMT

Hi,

Have you checked on your nodes the value set for MinNumberOfExecutionResultsToKeepPerTask in %Program Files%\Qlik\Sense\Repository\Repository.exe.config ? Is it higher than 1 ?

Best regards

Re: Script log file not available in C:\ProgramData\Qlik\Sense\Log\Script folder or Archived folder

sudhakar_c — Tue, 19 Oct 2021 06:48:43 GMT

Hi Alexis,

Thanks for reply,

Yes it is more than 1.

The issue is not with all apps, it is for few apps only.

Re: Script log file not available in C:\ProgramData\Qlik\Sense\Log\Script folder or Archived folder

Maria_Halley — Wed, 20 Oct 2021 09:55:32 GMT

@sudhakar_c

The error you are getting seems to be QueryRemoteProtocolInformation invalid parameter.

This is a response from Windows that QlikSense can't access the file. So it is most likely environmental . But it is odd that you only get this on only a few apps.

I would recommend that you open a case on this.