Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

QVW Reload Failure: at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage)

Hi,

I got the following error during the execution of one of our scripts:

(2015-06-08 09:10:35) Error: The task "Reload of QDF\5.Attendance\1.Application\3.Transformation\11.Attendance_Fact_temp.qvw" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT reloaded successfully. DocumentPath=D:\QlikView\TI\SourceDocuments\QDF\5.Attendance\1.Application\3.Transformation\11.Attendance_Fact_temp.qvw.  ||    at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult) ||    at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) ||    --- End of inner exception stack trace --- ||    at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) ||    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) ||    --- End of inner exception stack trace --- ||    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) ||    at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)


I've been doing some research in the community, and it seems that this error is not an specific one. Some posts recommends to look in the document log. Unfortunately, we didn't have logging active at that time.

Is there other way to look for more details about this error in any other log?

Thank you in advance,

Regards,


1 Solution

Accepted Solutions
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

No. You must have a document log. Otherwise you can only guess at the error. Good reason to always have document log turned on. I'm sorry Log On is not the default for new QlikView installations.

-Rob

View solution in original post

2 Replies
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

No. You must have a document log. Otherwise you can only guess at the error. Good reason to always have document log turned on. I'm sorry Log On is not the default for new QlikView installations.

-Rob

Anonymous
Not applicable
Author

Thank you Rob, we will turn on this feature from now on in all documents.

Regards,

-Karla