Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Load script stops suddenly, causing scheduled execution to fail

Good morning community!

I'm having an issue with a scheduled load execution in Qlikview.  My Create_QVD is scheduled to run on Sunday at 15:00, but often I'll check the schedule on Monday to find that this run has failed.  I check the log, and there is no error message; the script seems to just stop suddenly.

Every time that this has happened, it has always stopped at the exact same place.  The last line is always "Order Discount from Current Retail Price, "

This is attempting to load an archived version of the transactional table to concatenate to this week's version of the table.

Please see below the section of my load script that the execution stops at:

Load script fail.JPG

Is this an issue with memory?  Or with the load script?

Thanks,

Henry

1 Solution

Accepted Solutions
RadovanOresky
Partner Ambassador
Partner Ambassador

Well, it could also be caused by the Timeout limit for the document reload.

I believe that the default timeout is 21600, which is  6 hours.

If it started at 1500, than it was already 5 hours running, when it started the last logged load. It looks like a big one, so it might not have enough time to finish.

If this will end up the be the cause, I suggest you either increase the timeout limit in the QMC for this document, or segment the load to multiple smaller / shorter loads.

Radovan

View solution in original post

10 Replies
prieper
Master II
Master II

Hard to judge without further details ...

But looks very much to be a memory-problem.

What happens, when you run it on local computer?

RadovanOresky
Partner Ambassador
Partner Ambassador

Well, it could also be caused by the Timeout limit for the document reload.

I believe that the default timeout is 21600, which is  6 hours.

If it started at 1500, than it was already 5 hours running, when it started the last logged load. It looks like a big one, so it might not have enough time to finish.

If this will end up the be the cause, I suggest you either increase the timeout limit in the QMC for this document, or segment the load to multiple smaller / shorter loads.

Radovan

Anonymous
Not applicable
Author

I'll try running it manually now.  So far it seems to be fine.  It may be a few hours before I can give a proper answer, though

Anonymous
Not applicable
Author

Hi Radovan,

Do you know where I can find the option to increase the timeout value in QMC? I can't find it under the 'Documents' tab

passionate
Specialist
Specialist

The best place to find issue is Qlikview server log.

Anonymous
Not applicable
Author

Hi Pankaj,

Do you know where the server logs would usually be kept?  Or how I can find out where they are kept?

Peter_Cammaert
Partner - Champion III
Partner - Champion III

I'm assuming that you don't have a Publisher license, because in a standard task definition the default timeout is 1440 minutes or 24 hrs. On a Publisher-less server, you can find the timeout field on the Reload tab here:

Reload Timeout Value.jpg

Note: to make sure that a reload engine being killed due to a timeout really is the cause of failure, check the TaskLog.txt file in the relevant subfolder of the QDS tree (C:\ProgramData\QlikTech\DistributionService\1\Log\). It should list an error message about "...engine aborted..." or something like that, while the DocumentLog doesn't tell you anything (being killed makes that rather difficult 🙂

RadovanOresky
Partner Ambassador
Partner Ambassador

Hi, if you have Small Business Edition server, the option is on:

Documents tab > select one document > Reload sub-tab (right side of the screen) > Timeout in seconds option.

You need to hit Apply after you change it.

On Enterprise Edition server, this option is on the reload task on Source Documents on the Triggers subtab (here it states the timeout in minutes).

Radovan

Anonymous
Not applicable
Author

Hi Peter,

I believe I've found the log for this reload in the location you've specified above, and the error message is as follows:

Load script fail2.JPG

From what I can gather, this is indeed a timeout issue