A QlikView administrator may want to determine if a QlikView Distribution Service(QDS) or Reload Engine task was manually triggered or triggered via schedule. This information is not provided in either the QDS task log or the document log of the QVW associated with the task. However, the information is contained in the QDS Root log.
Environment
As an example, a task named Reload and Distribution of Test reload was created. The task was manually run then run via a scheduled trigger.
QDS Root log
From the manually run task from the QMC:
20210730T085815.082-0400 Information Manual start for task "Reload and Distribution of Test reload" (c203c0ff-3b53-486c-915e-736e05da044d) requested.
20210730T085815.090-0400 Information ManualStartTrigger[00000001-0002-0003-0405-0607080a0b0c]: PlanToGoOff - Adding new TriggerState planned for 2021-07-30 08:58:15.089, Task="Reload and Distribution of Test reload", ExecID=0b06d4d5-e96d-4651-b50a-dbae5ee6ea54
From the scheduled task:
20210730T090000.149-0400 Information ScheduleTrigger[f85e0413-5625-4ea2-af33-ae63535427fc]: PlanToGoOff - Adding new TriggerState planned for 2021-08-06 09:00:00.000, Task="Reload and Distribution of Test reload", ExecID=3bf88496-6c64-41a4-90ca-9a24b5a7cd6b
In the QDS Root log, both manually triggered and schedule triggered tasks are noted as such.
Root log location
The QDS Root log is by default in the %ProgramData%\QlikTech\DistributionService\1\Log directory and has a naming convention of Root_yyyymmdd.txt. If you have configured the QDS logs to be written in a different location, you can check QMC > System > Setup > Distribution Services > QDS@ > General tab > Application Data Folder, then look for the 1\Log directory. If you have a QDS cluster you will have 1\ 2\ 3\ etc. directories depending upon the number of QDS nodes.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
Related Content
