Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

auto reload

Hello

I have a problem with auto reload.

This is my log file:

(2012-04-25 11:59:33) Information: Starting task 'lampiris.qvw'. Id:e38c6c72-c669-4d8d-8302-5c7e2c2ef007. Triggered by 'ContinuousTrigger'. Id:0000000f-000f-000f-0e0e-0e0e0d0d0d00 (2012-04-25 11:59:33) Information: Entering Task Execution. (2012-04-25 11:59:33) Information: ClusterID=1 (2012-04-25 11:59:33) Information: QDSID=3ab1c3e2-92f0-040b-0bf9-747b91b56cf8 (2012-04-25 11:59:33) Information: TaskID=e38c6c72-c669-4d8d-8302-5c7e2c2ef007 (2012-04-25 11:59:33) Information: MaxRunTime=06:00:00 (2012-04-25 11:59:33) Information: Max attempts:1 (2012-04-25 11:59:33) Information: Current Attempt=0 (2012-04-25 11:59:33) Information: Task Dependencies are OK (2012-04-25 11:59:33) Error: The task "lampiris.qvw" failed. Exception: (2012-04-25 11:59:33) Error: QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> QDSMain.Exceptions.SourceDocumentNotFoundException: Could not find SourceDocument (Distribution): qvp://localhost/lampiris.qvw (2012-04-25 11:59:33) Error:    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult )(2012-04-25 11:59:33) Error:    --- End of inner exception stack trace --- (2012-04-25 11:59:33) Error:    at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) (2012-04-25 11:59:33) Error:    at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult) (2012-04-25 11:59:33) Information: Task Execute Duration=00:00:00.0156248 (2012-04-25 11:59:33) Information: TaskResult.status=Finished (2012-04-25 11:59:33) Information: Notifying all triggers of new state:FinishedWithErrors (2012-04-25 11:59:33) Information: Notifying all triggers of new state:FinishedWithErrors – completed (2012-04-25 11:59:33) Information: Saving Task Result

Any ideas?

7 Replies
subin6600
Creator III
Creator III

Guess it is because the report could not find the Source document. Might it it must have been renamed check it.

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi there,

subin6600 is most likely correct.  This message occurs when the document that is scheduled to reload has been renamed or deleted from the file system.  It can actually be a bit fiddly to stop the reload firing once a document has been removed, as the document is no longer shown on the Documents tab on the QEMC.

What you need to do to remove the rogue task is to create a dummy QlikView document and name it the same as the old one and place it in the same location.  You can then find the document on the Documents tab and disable the reload task.

Once you have done this you can set up a new task on the document where it now resides.

Post back here if this doesn't work out for you.

Steve

http://www.quickintelligence.co.uk/

Not applicable
Author

Hi Steve,


I'm facing the same scenario. For example, the old location for qvws is wm.corp.com\Projects\IT\Business Data and moved to a new location wm.corp.com\Projects\IT\qlikview\dashboards\Business Data. The tasks were deleted from the old location without disabling them and set up the exact same task names for the qvws in the new location. The qlikview sends task failure notifications to the DL everyday.

Below is the Task failure notification looks like:

Subject Line: QlikView Publisher: The task "IT/Business Data/Analysts.qvw" failed

Email Body :The task "IT/Business Data/Analysts.qvw" failed. Part of the log file follows:

1/21/2015 12:00:00 PM Error The task "IT/Business Data/Analysts.qvw" failed. Exception:
QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> QDSMain.Exceptions.SourceDocumentNotFoundException: Could not find SourceDocument (Distribution): qvp://localhost/DMG_Dashboards/Data Quality/Employee.qvw
   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)


As per your suggestion, restored the folder with the qvws to the old (original) location. Couldn't find the tasks. so tried creating the same tasks, disabled & deleted them and also deleted that folder (original location). It's still the same.

Everyday it sends the notifications @ 12:00 am and for one task it sends 12:00 pm. When restored the folder it was 12:00 pm so it didn't send the notification just one day because that qvw exists @ 12:00 pm per the notification time.

Just for info, when restored to the old location the new location qvws & tasks with same tasks name were there and didn't delete them. It would be really helpful if you suggest what to do next on this. Thank you!

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi Preetha,

I would recommend you take a look at the excellent QlikView User CAL Manager by dvasseur .This will allow you to get a list off of all of the documents on your server, along with where they are.

You can also take a look in the Distribution Service folder (by default this can be found at c:\ProgramData\QlikTech\DistributionService\ ).  You should be able to work out which task is failing by finding the TaskExecutionHistory record with the same time stamp as the failure.  You can then locate the Task itself in the Tasks folder (the filename will have the same GUID in it).  This will give you yet more information about the document you need to recreate in order to kill the task.

You can also just delete the XML file for the task you want to remove from the Tasks folder.

Hope that helps.

Steve

Not applicable
Author

Thank you so much Steve.

I checked in C:\ProgramData\QlikTech\DistributionService\  TaskExecutionHistory,Tasks & TaskResults etc. It didn't help much.

Basically there is no trace for these Tasks. If you noticed in the email there is no task name and no logs or GUIDs associated for the tasks anywhere. Only evidence is the Email notifications.

Business team have doc admin rights and have set up the tasks like below. Thus how the tasks started to send out the notifications.

1) Copied Business data folder(where qvw docs reside) from wm.corp.com\Projects\IT\Business Data and pasted to wm.corp.com\Projects\IT\qlikview\dashboards.

2) in QMC, created the tasks with trigger to the docs in the new location with the exact same name but by default it will have (2) in the name because we can't have the same task name twice. Example: Reload Analyst Data (2). 

3) Then deleted the task for the qvw's from wm.corp.com\Projects\IT\Business Data under Source Documents.

4) Removed Business Data folder from wm.corp.com\Projects\IT.

5) Renamed the task name without (2) for the qvw's in the new location.

There are around 12 tasks looking for qvw's in that location and send out notifications everyday @ 12:00 am for 11 tasks and 1 task @ 12:00 pm but trigger time for the tasks are different but not sure how it's picks up the time @ 12:00.

Surprising thing is the notifications are not sending to the email addresses given in QMC\System\Setup\Distribution Services\QDS@local host\Alert Email. Also verified there is no email address given in System\Setup\Mail Server for Override E-mail. From somewhere else it's picking up the DL and sending the notifications. Also checked the email addresses for the Document Administrators below Source Folders in QMC\System\Setup\Distribution Services\QDS@local host\General.

For info, our server is 11.2 SR3. We have two servers, one publisher set up.

Do you think restarting the QDS will help ? This issue is in Prod Server and No solution till now. Any suggestions will be much helpful. Thank you!

stevedark
Partner Ambassador/MVP
Partner Ambassador/MVP

It's not that you have an old development / test server that has not been properly decommissioned somewhere?

Distribution tasks will continue on a box even after the licence has expired, I believe.

Steve

Not applicable
Author

Good to know and Thank you  so much for the information.

I remember this was the only change happened in that server and after that it started to send out the notifications.

Couple of days ago I restorted the Business Data folder to the original location along with the qvws to see if I could see any tasks in QMC\Documents\Source Documents for the qvws. I couldn't find any tasks and I forgot to delete the folder from that location. So, from past couple of days we receive notifications only for 4 of them and for 8 of them it stopped sending notifications.

When I checked the qvws in the original location for the ones which stopped sending notifications, the date modified was 01/29/2015 12:00 am which means the reload happened at that time also in Access point the last update for the qvw's were same 12:00 am. . As mentioned earlier this was not the trigger time for the tasks.

Now the error message for the 4 qvws looks like below.

Subject: QlikView Publisher: The task "IT/Business Data/Analysts.qvw" failed

The task "IT/Business Data/Analysts.qvw" failed. Part of the log file follows:

1/29/2015 12:00:53 AM Error The Source Document was NOT reloaded successfully. DocumentPath=\\wm.corp.com\Projects\IT\Business Data\Analysts.qvw.
1/29/2015 12:00:54 AM Error The task "IT/Business Data/Analysts.qvw" failed. Exception:
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=\\wm.corp.com\Projects\IT\Business Data\Analysts.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)

Once the folder will be deleted from the original location we will still receive the same notification messages. Please let me thoughts/suggestions. Thank you!