Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
AC187
Contributor II
Contributor II

Qlikview Management console

Hi all, I have a task on qlikview management console which runs for almost 2-3 hrs everyday and exactly after executing complete document while saving the document it fails saying task is being aborted and below error.

xyz.qvw - Task failed.Saving task progress for retry

Taskresult.status=retry

however in the immediate auto retry it does not completely executes the code but starts the retry of saving from where it left saving of document in earlier run.

 

so the task looks like: status of qmc:

Run 1).           19-11-2019 Failed 2 hrs 

Run retry 2) 19-11-2019 completed -

can anyone help what is the reason and how to resolve this.

5 Replies
Arthur_Fong
Partner - Specialist III
Partner - Specialist III

Is it because of your disk space running low?

AC187
Contributor II
Contributor II
Author

Hi Arthur,

nope this is not due to space, the application is of 10 gb and space on server is around 120 gb free

Arthur_Fong
Partner - Specialist III
Partner - Specialist III

Is there any other task running in parallel?

AC187
Contributor II
Contributor II
Author

Nope no task running in parallel

Brett_Bleess
Former Employee
Former Employee

Arjun, It would be more helpful if I had the full task log, the snippets are not as helpful as you would think, need the rest of the context to piece together exactly what is happening.  There are only two things of which I an think here.  The first would be related to Desktop Memory Heap, comes into play depending upon how many concurrent tasks you are running, here is an article regarding that:

Desktop Heap/QVB Engines... 

The other thing is the following setting that you could add to the QDS exe.config file:

SecondsToWaitBeforeQVBKill

The default setting is 16 seconds, if the file is rather larger etc., you could bump this to say 30 or 60 seconds to allow more time for the file system to handle things and see if that helps or not too.

Regards,
Brett

To help users find verified answers, please do not forget to use the "Accept as Solution" button on any post(s) that helped you resolve your problem or question.
I now work a compressed schedule, Tuesday, Wednesday and Thursday, so those will be the days I will reply to any follow-up posts.