I have a reload task that I can't get to run, I'm getting the error -
Task Log:
3/12/2026 11:42:14 AM The Source Document was NOT reloaded successfully. DocumentPath=C:\QlikView_Documents\Live_Reports\Live_HIPE_Load\TestDocs\HipeDataNewBU2r.qvf. 3/12/2026 11:42:15 AM The task "Live_HIPE_Load/TestDocs/HipeDataNewBU2r.qvf" 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=C:\QlikView_Documents\Live_Reports\Live_HIPE_Load\TestDocs\HipeDataNewBU2r.qvf. || at QDSMain.AbstractReloadTask.VerifyConditions(IExecutingTaskResult executingTaskResult) || at QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || --- End of inner exception stack trace --- || at QDSMain.AbstractReloadTask.Reload(String fileName, IExecutingTaskResult executingTaskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || at QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || --- End of inner exception stack trace --- || at QDSMain.DistributeTask.PerformExecute(IExecutingTaskResult executingTaskResult) || at QDSMain.Task.AbstractTask.TaskExecution(CurrentExecutionArgs args)
Document Log:
3/12/2026 Error: Connector reply error: ErrorSource: Microsoft OLE DB Provider for SQL Server, ErrorMsg: The conversion of a varchar data type to a datetime data type resulted in an out-of-range value.
I'm not an expert in SQL, but I think this error message is generated due to SQL is trying to convert a varchar value in a datetime value when the call is done. I mean, it doesn't seem an issue in QlikView code.
It could happen for example with the date 31-12-2025. If SQL is trying to read it like MM-DD-YYYY, it could trigger this error. Or it could be an impossible date like 32-12-2025.
Hence, I think the best option would be to review that all the values in the data source are properly set for the field impacted.
