Seems you have section access in your document, do you? Can you pick document log from your log folder. You can enable document log by opening your document in QV and press Ctrl+Al+D - General Tab - Check Generate Log File option and save it. Then run your document on QMC. When it fails it generated a log file. The path will be given in the status history where you can find your doc log file.
Can you please enable the log file by opening your document in QV and press Ctrl+Al+D - General Tab - Check Generate Log File. During your next reload it will genrate a log file in the folder. Can you post that here to know what exact error you are getting .
Whenever a document is reloaded under QMC control, it can generate two log files that document different details of the reload process:
The QDS scheduler plans a reload and assigns a reload engine to the job. The QDS doesn't do the reload by itself, but monitors the reload job and records the end-result. It can also abort the reload when there doesn't seem to come an end to the reload. All these details are logged in a TaskLog.txt file. That's the one you posted (twice) in this discussion. However, the TaskLog may report failure due to script errors at the end of script execution but will not tell you what they are because it doesn't know. That's because the reload is handled by...
The Reload engine (QVB.exe) that was assigned this job, and that will open the QVW document, execute the load script, save the document (if all went well) and exit. During script execution, the reload engine may generate a detailed DocumentLog.txt file that includes messages and script error details, but only if you enable log generation in your document, as Vishwarath and Pradosh already explained.
The TaskLog told you that errors occured during the reload but is useless for figuring out what went wrong during script execution. We need a DocumentLog. Enable log generation in your QVW document, wait until the reload fails again and post the resulting DocumentLog file.
