Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Publisher Task Times out after 45 Minutes

We have large batch of non dependant tasks that run overnight and we schedule them all in Publisher to start at the same time.

Some of the tasks take minutes to run, some of them can take over an hour.

Some of the tasks fail with this error:

01/01/2012 02:15:06     Error     Failed to allocate a QlikView Engine.

01/01/2012 02:15:06     Error     No QlikView Engine was available after waiting for 45 minutes

01/01/2012 02:15:06     Error     Reload failed because the document could not be opened successfully. DocumentState=CouldNotGetSlot

01/01/2012 02:15:06     Error     Reload failed. Distribution skipped.

01/01/2012 02:15:06     Error     The task "QV Instrument Dataload" failed. ErrorCount=4

It looks as though once a task has been scheduled if it doesn;t get allocated and engine within 45 minutes it fails.

We have set "Max number of simultaneous QlikView engines for distribution" to be the same as the number of CPU cores and don;t want to set it a ny higher.

How can we raise this default 45 minutes and allow the submitted, pending jobs to run as and when an engine becomes available.

Thanks

1 Solution

Accepted Solutions
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

You can change limit in

C:\Program Files\QlikView\Distribution Service\QVDistributionService.exe.config.

The key is "QvbWaitTimeoutMinutes".

-Rob

http://robwunderlich.com

View solution in original post

5 Replies
rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

You can change limit in

C:\Program Files\QlikView\Distribution Service\QVDistributionService.exe.config.

The key is "QvbWaitTimeoutMinutes".

-Rob

http://robwunderlich.com

Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist

Hi Rob Wunderlich

Do you know what is the recomended number o simultaneous reloads task that we should set??

Regards!

rwunderlich
Partner Ambassador/MVP
Partner Ambassador/MVP

The general recommendation is no more than the number of cores on the machine. If you are running reloads on the same box as QV server, you'll probably want to go with less than the number of cores so you can save some juice for Users. Unless of course, all your reloads are hapening during a period when no users are on.

If you set more than 7 reloads, be sure to apply the Desktop Heap registry change.

-Rob

Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist

Thank you Rob!

Not applicable
Author

Great advice and will sort out issues with my server - when changing these variables does the server need to be restarted?

Thanks.