Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I have a QlkView Publisher (v11 SR2) task that shows that it failed, however when I look at the document log, it appears to have completed successfully. There are no errors, the qvw has been successfully updated and saved, but the task is showing up as failed in publisher. I've tried deleting and recreating the task, but this hasn't helped. Not sure what else to try. Has anyone else seen this behavior?
Thanks
Hi All,
I figured it out. I found this post: failed task status and Alexander Korsikov had the correct answer. I had to add a setting in the config file. Once I made the change, the task ran and completed successfully.
Thanks to everyone for your help,
Bret
Disk full where publisher logfiles are written could perhaps cause this. what is our last command in the script of the failing doc?
Hi Robert,
Thanks for responding to my post. No issue with disk space, and the last command in the script is Exit Script. I've tried loading up a dummy inline table and then dropping it prior to hitting the Exit Script. I'm going to try it without the Exit Script as well. I'd happily entertain any ideas you may have as well. This is the only script that's behaving this way out of, I don't know, dozens.
Thanks Again,
Bret
This is a weird error. Just some quick checks :
Do you have any STORE command in the script?
Is the task a Reload Only or also distribution and/or reduction ?
Robert
It is a weird error, but I've seen it before. There are store commands in the script, and it is a reload only, no distribution.
I would anyway start to place TRACE commands in the script before and after STORE just to be sure there is no pb with security.
Another check to do is to rename another QVW that is working from publisher ; to the same name as this failing qvw, just to know if this problem actually is caused by the task itself, or not.
You wrote you had recreated the task, with a new task name or not?
If you can confirm it is script related, then I guess fasted solution is trial/error process... to remove code by code until it is working....
In any case, some trace of an abnormal termination should be present in the TaskLog. You know where you can find the TaskLog? Please post it in this thread.
Hi Peter,
Thanks for weighing in. Ok, there IS an error in the Tasklog, here it is:
5/31/2017 08:31:44.5812483 | Error | Could not close the SourceDocument. Exception=The currently executing operation was aborted. |
5/31/2017 08:31:44.6749576 | Warning | The QlikView Engine isn't responding to close command, it will be killed (Please ignore logged errors about the kill). |
5/31/2017 08:31:44.6905824 | Information | Killing the QlikView Engine. ProcessID=1732 |
5/31/2017 08:31:45.4093522 | Information | Closed the QlikView Engine successfully. ProcessID=1732 |
5/31/2017 08:31:45.4562300 | Error | The task "A1.0615-PatientSurveys\PatientSurvey.qvw - Reload - Daily" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.LogBucketErrorException: Could not close the SourceDocument. Exception=The currently executing operation was aborted. || 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) |
5/31/2017 08:31:45.4562300 | Information | Task Execute Duration=02:16:20.2454154 |
5/31/2017 08:31:45.4562300 | Information | Sending Alert mail |
5/31/2017 08:31:45.6281126 | Information | TaskResult.status=Finished |
5/31/2017 08:31:45.6438901 | Information | Notifying all triggers of new state:FinishedWithErrors |
5/31/2017 08:31:45.6438901 | Information | Notifying all triggers of new state:FinishedWithErrors - completed |
5/31/2017 08:31:45.6438901 | Information | Saving Task Result |
Maybe this is helpful: False positive error-message from qmc.
- Marcus
Hi All,
I figured it out. I found this post: failed task status and Alexander Korsikov had the correct answer. I had to add a setting in the config file. Once I made the change, the task ran and completed successfully.
Thanks to everyone for your help,
Bret