Ok, you may or may not know but in most cases the TaskLog is simply useless to find the cause of a failed reload. Especially if you take out a small piece of gibberish that only Qlik Developers understand.
Can you post the full TaskLog, and if possible (or relevant) the DocumentLog as well? If logging hasn't been enabled in your QlikView document, please enable it and rerun your task.
To reiterate Peter's above comment, the Task log wouldn't provide the necessary information in order to troubleshoot the reload failure. In the Task log snippet you posted, we can see the first entry indicates that the issue is occurring at the Document level
28/04/2017 06:10:05 Error The Source Document was NOT reloaded successfully. DocumentPath=D:\QLIKVIEW REPORTS\XYZ.qvw.
So to proceed, you'll want to review the Document log of the QVW associated with the failed task. If document logging is enabled, it will be stored in the same directory in which the QVW file is housed. If document logging is not enabled, you will need to open the QVW file in QlikView Developer, click Settings > Document Properties > General tab and ensure the Generate Logfile checkbox is ticked. Then run the reload task so that the document log is generated.
Hope this helps,
In case the problems come back:
This kind of issues where something works "locally" but not in QMC, is very often because the qlikview service accounts don't have the same (domain) security settings as your development account has.
Scripts trying to load or store from a drive or share with insufficient access on the service accounts.