Qlik Community

Ask a Question

New to QlikView

If you’re new to QlikView, start with this Discussion Board and get up-to-speed quickly.

Announcements
Talk to Experts Tuesday, January 26th at 10AM EST: Qlik Sense. REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Reload Failed

Hi,

We have scheduled a few reload to kick start once every morning and those reload will fail once every week. 

So far, I tried to check on the history log, it said the source document reload complete but then The Source Document was NOT reloaded successfully.  Is there any way I can further check on why it is not reloaded successfully?

Below is part of the failure message:

21 06:32:35) Information: The Source Document reload complete. DocumentPath=D:\QLIKVIEW\QVD\Revenue Analysis - QVD Generator New.qvw

(2014-10-21 06:32:35) Information: Memory Allocation Delta for this file=2531.37 Mb. Available Physical Memory Before Reload=245890.18 Mb. Available Physical Memory After Reload=239372.19 Mb. Total Physical Memory=239372.19 Mb.

(2014-10-21 06:32:36) Error: The Source Document was NOT reloaded successfully. DocumentPath=D:\QLIKVIEW\QVD\Revenue Analysis - QVD Generator New.qvw.

(2014-10-21 06:32:36) Information: Closing the document.

(2014-10-21 06:32:36) Information: Closed the QlikView Engine successfully. ProcessID=8072

(2014-10-21 06:32:37) Error: The task "QVD/Revenue Analysis - QVD Generator New.qvw" failed. Exception:

(2014-10-21 06:32:37) Error: 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\QVD\Revenue Analysis - QVD Generator New.qvw.

(2014-10-21 06:32:37) Error: at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult)

(2014-10-21 06:32:37) Error: at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage)

(2014-10-21 06:32:37) Error: --- End of inner exception stack trace ---

(2014-10-21 06:32:37) Error: at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage)

(2014-10-21 06:32:37) Error: at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)

(2014-10-21 06:32:37) Error: --- End of inner exception stack trace ---

(2014-10-21 06:32:37) Error: at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult)

(2014-10-21 06:32:37) Error: at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

(2014-10-21 06:32:37) Information: Task Execute Duration=00:32:36.9579210

Hope anyone could provide me some help in:

1.  Understanding the reason why the reload is failed

2.  Understanding if there is any method in reducing this reload failure to zero

3.  Understanding the best method in deciding the timeout seconds - if I have a job which most of the time will complete in 10 minutes, does this mean I should set up the timeout second around  700 seconds?

In addition, is there a way I can programme to reload a QVD if the reload is failed?  At the moment, one of the QVD reload is only programmed to start once per day, and every time when this reload is failed, it will not retry to reload again. In Reload, there is an option 'On Event from Another Task' 'Succesful' ... is there an option for 'Failed'?

Thank you,

David

3 Replies
Creator III
Creator III

Hi,

1. This issue is occurred due to the Low Memory Allocation.(the RAM is not sufficient for the execution). I hope it;s popping a type D error while loading.(Try a manual reload and check.)

2. There are some possible ways to avoid this issue like  increasing memory, application slicing, stopping other     processes and reload, etc.

3. When you increasing time out duration that will not solve this issue as I think. By increasing time out duration you can keep your connection alive but it won't any regarding memory.

Yes,there is an option on event Failed. But you cant reload the same application. for an example in the event of fail of application C you can't reload the application C again. Instead of that try to load a sliced application which solve your problem.

BR,

Dinu'1

Not applicable

Hi Dinu,

Cheers for the reply. 

1.  May I ask which message indicate that the Memory Allocation is insufficient?  Is it the first part of the message?  Yes.  Whenever this happened, we have to do the manual reload. Any idea how do we monitor the Memory Allocation of each reload?

2.  I thought if I increase the time out, and hopefully when the other processes stopped, it will have more Memory Allocation, no?

3.  I will do some research about application slicing - any good material regarding this?

4.  I dont quite understand what do you mean by try to load a sliced application which solve my problem?  do you mean if the reload is failed, I should load an .QVW application ?

David

Partner
Partner

1. windows perfomance monitor can help you.

2.it depends on how solve the windows memory manager