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: 
Not applicable

QlkiView Publisher failed

I have been receiving these error messages all weekend.

The task "Developer Reports/Group Weekly Sales - QVD creator.qvw" failed. Part of the log file follows:

25/02/2013 10:28:42        Error      The Source Document was NOT reloaded
successfully. DocumentPath=D:\QlikView Documents\Developer Reports\Group Weekly
Sales - QVD creator.qvw.

25/02/2013 10:28:43        Error      The task "Developer Reports/Group
Weekly Sales - QVD creator.qvw" failed. Exception:

  1. QDSMain.Exceptions.DistributionFailedException:
    Distribute failed with errors to follow. --->
    QDSMain.Exceptions.ReloadFailedException: Reload failed --->
    QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT
    reloaded successfully. DocumentPath=D:\QlikView Documents\Developer
    Reports\Group Weekly Sales - QVD creator.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 ---

Can anyone tell me what any of this means please or where I can find any helpful information to work it out. I'm very new to all this.

Thanks

2 Replies
Gysbert_Wassenaar
Partner - Champion III
Partner - Champion III

The reload of document Group Weekly Sales - QVD creator.qvw failed. Check that you enabled the Generate Logfile option it the document properties of that document. If you did there will be a log file in the same directory as the qvw. In that log file you can see what error occurred.


talk is cheap, supply exceeds demand
Not applicable
Author

Thanks. The Generate Logfile option wasn't enabled, but it is now. I've re-run it and I've been able to locate the fault which was a coding error.