This is not a bug. It is default behavior.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
Refer KBA : 000030238
QlikView 12: Distribution Service apparently not generating document log until reload completion
That's a reasonable question. It's quite possible to be a document admin who can run tasks but may not have access to c:\ProgramData. There is an option to use the old behavior. It's documented in the QV12 SR1 Release Notes. Since I don't see it documented anywhere else, I thought I would reproduce it here.
Document log optimization for QlikView Publisher
An increase in app reload times was observed in QlikView 12 when document logging is enabled in the document settings. This increase is most significant when using QlikView Publisher, because log files are often written to a remote folder. To mitigate against this increase in reload times, logs are now saved locally, by default, before they are copied to the remote app folder
Local script logging can be controlled using the LocalScriptLogging= and the ScriptLogFolder= parameters. These parameters can be added to the settings.ini file located by default in C:\Windows\System32\config\systemprofile\AppData\Roaming\QlikTech\QlikViewBatch. If these parameters are not included in the settings.ini file, local script logging is enabled.
By default, logs are written locally to C:\ProgramData\QlikTech\QlikViewBatch before the are moved to the remote app folder. If a reload crashes, the logs may be retrieved from this folder. The ScriptLogFolder= parameter can be defined to set the folder logs are written to. You can also disable local script logging by setting LocalScriptLogging= to 0. With this setting disabled, logs are written directly to the remote app folder. The default local logging behavior can also be achieved by adding the two parameter and setting LocalScriptLogging= to 1 and leaving ScriptLogFolder= empty.