How to find the Script (Reload) logs in Qlik Sense Enterprise

Qlik Sense has Document logs / Script logs that get created on execution of a reload.

Dependent on where the reload is executed (through the Management Console / a Schedule or the Qlik Sense Hub), the location may differ.
 

Executed from the Management Console (QMC):

Location of the Script logs when run in the QMC via a Scheduled Task or through the manual run of the Task in the QMC.

Default: \\<sharedpath>\ArchivedLogs\<servername>\Script such as C:\ProgramData\Qlik\Sense\Repository\Archived Logs\Server Name\Script

Note: Binary ID is associated with the App Binary ID. 




Note: This folder is on the Engine/Scheduler node that ran the Reload task.  These logs are automatically sent to the Archived Logs after the completion of the reload attempt. They will be placed in the server name folder that executed the reload. IE: ArchivedLogs/qlikserver2.domain.local/Script
 

Executed from the Qlik Sense Hub:

Location of the Script logs when run in the Hub. Default:  C:\ProgramData\Qlik\Sense\Log\Script



Note: The folder is on the Engine node that loaded the Application/QVF into memory. This node does NOT need a Scheduler active and the Script log will always be saved on the Engine that did the reload. This log NEVER gets moved to the Archived Logs
 
Reload when successful in the QMC:
 

 
Reload that failed in the QMC:
 


Note: For both the successful and failed reloads notice the “Download script log” button that’s clickable. Click it to download the Script log of that reload to the local machine Downloads folder of the browser you’re connecting to the QMC with. IE: If you download it on the server, it will be in the Downloads of the server. If you do it on your local PC/Laptop, it will be in the local Downloads of that PC/Laptop.





Note: This is a failed reload with an Error. The task never gets to the point of starting the reload, so it errors out without generating the log. You can notice the “Download script log” button is greyed out because of the Error status. Examples that could trigger an Error include, but not always linked to issues with: Engine/Scheduler/App Binary/Access to the file location/Load Balancing Rules for Applications

 

Download and attach the script reload log(s) to the case, if you have an open ticket.

It's almost important to test reloading the application in both the Hub as well as the QMC. In the Hub, open the application and try a manual reload. If it fails, please attach the data/error to the case. In the QMC, open the application or task and reload it, and if it fails, attach it to the case. If it only fails in the QMC as a scheduled task, but reloads manually in the Hub just fine in the Data Load Editor, please let us know.