QlikView tasks fail with no document log

[chris_johnson]

Hi,

Does anyone know why a reload on QlikView Server would fail and NOT produce a document log?

This is a task that usually completes successfully and DOES create the document log.

Is there a point at which a task can fail before anything is written to the document log?

Thanks

[martinpohl · Accepted solution]

Since QlikView 12 SR1, the document reload log is generated locally on the QlikView Distribution Serrvice node handling the reload task inside C:\ProgramData\QlikTech\QlikViewBatch

Once the reload is done, the document log is then copied to the Source Document folder and QDS Application Data folder.
The purpose of this change is to avoid continuously writing log entries to remote folders.
This change is documented in the Release Notes for QlikView 12 SR1, which is available in our download site.

Accordingly, if a customer wants to monitor document logs during reload, they can find these logs at C:\ProgramData\QlikTech\QlikViewBatch.
Temporary logs in this folder will be erased when the reload is done.

Maybe the job wasn't finished so the file couldn't be copied.

Regards

[chris_johnson]

Ah ok, I'll keep track of that folder too. Good to know, thanks