Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
RedSky001
Partner - Creator III
Partner - Creator III

Large file failing to reload

We have a large (over 10 GB) qvw document which fails to reload when run as a task from the management console.

The error file is attached. I am guessing the task has some timeout limit associated withopening the document.

Does anyone know wherethis is or any other possible cause?

Cheers

Mark

12 Replies
Not applicable

I'd like to add that I am experiencing the same issue in QV11.  We have a 3GB Qlikmart that fails with the same error message. No section access in any of our documents.

I tried using the local client and it seemed to work fine.

Next I reduced all data in the Qlikmart, and it worked fine in publisher.

So following msheraton's workaround I added an external task to copy a reduced Qlikmart on top of the existing file just before reloading.  This seems to be working fine, however I will raise the issue with Qliktech as well.

Thanks msheraton for your post!!!  You saved my migration to QV11!!!

Not applicable

Try this:

I had similar problem in QV 10 SR3 with extract large data. I expand shared memory area in register.

I did:

1. run regedit

2. find SharedSection (edit--->find)

3. inside you have - ......SharedSection = 1024,20480,512)  --- (512 or more)

4. right click--->Modify

5. last value-512 (or what you have) multiply by 2   (512* 2 = 1024)

6. if needed multiplay by two again....or more,depending how much memory you have. We have 64GB of ram and I expand the last value to 12288 and now work fine.

Worked for me.

RedSky001
Partner - Creator III
Partner - Creator III
Author

Forgot to reply back to this post but Qliktech have confirmed it's a bug and will be released in QV11 SP1.

http://community.qlik.com/thread/47446

SLOCowboy think I'll wait for SP1 the workaround is doing the job for now..

Cheers

Mark