Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
olaf_gschweng
Partner - Contributor II
Partner - Contributor II

Qlik Sense 1.00 crashes reproducible on concatenating QVD files

Hello

We have a set of QVD files with the same structure - one file per month. Qlik Sense crashes reproducible loading these files.

This is the script:

pos:

LOAD *  FROM [lib://Data/pos_2013-*.qvd] (qvd);

This is the output:

pos << pos_2013-01

(QVD columnar optimized)

Lines fetched: 132.498

pos << pos_2013-02

(QVD columnar optimized)

Lines fetched: 262.638

pos << pos_2013-03

(QVD columnar optimized)

Lines fetched: 413.367

pos << pos_2013-04

(QVD columnar optimized)

Lines fetched: 570.108

pos << pos_2013-05

(QVD columnar optimized)

Lines fetched: 732.856

pos << pos_2013-06

(QVD columnar optimized)

Lines fetched: 909.663

pos << pos_2013-07

(QVD columnar optimized)

Loading QVC file: 138.909

After the last line Sense Desktop crashes to desktop. With Sense Server 1.00 the engine crashes.

The same happens when loading the files individually and explicitly or implicitly concatenating them:

pos:

LOAD *  FROM [lib://Data/pos_2013-01.qvd] (qvd);

Concatenate LOAD *  FROM [lib://Data/pos_2013-02.qvd] (qvd);

Concatenate LOAD *  FROM [lib://Data/pos_2013-03.qvd] (qvd);

Concatenate LOAD *  FROM [lib://Data/pos_2013-04.qvd] (qvd);

Concatenate LOAD *  FROM [lib://Data/pos_2013-05.qvd] (qvd);

Concatenate LOAD *  FROM [lib://Data/pos_2013-06.qvd] (qvd);

Concatenate LOAD *  FROM [lib://Data/pos_2013-07.qvd] (qvd);

Is this a known bug?

Olaf

11 Replies
gandalfgray
Specialist II
Specialist II

Sorry I can't help you, but I became curious, how did you enable logging for the load script?

olaf_gschweng
Partner - Contributor II
Partner - Contributor II
Author

Hello Gandalf,

I didn't enable logging. In Sense Desktop I found the logfiles in my user directory under Qlik\Sense\Log\.

Olaf

Not applicable

Can you share the rest of the Logs (Performance, Engine etc., same folder) from the time you reload, so we can check what hapens in the Backround with the Engine?

olaf_gschweng
Partner - Contributor II
Partner - Contributor II
Author

Hello Daniel,

I appended a zip-file to my original post. I included all logfiles with the same process ID that I found in the log of the script (new one, also included). I hope this is the correct choice.

Olaf

gandalfgray
Specialist II
Specialist II

Thanks Olaf!

In Server version the logs seems to be stored in C:\ProgramData\Qlik\Sense\Log\Script with the guid that is associated with the app.

You can see what guid the app has as the last part of the url.

/gg

olaf_gschweng
Partner - Contributor II
Partner - Contributor II
Author

GandalfGray schrieb:

Thanks Olaf!

In Server version the logs seems to be stored in C:\ProgramData\Qlik\Sense\Log\Script with the guid that is associated with the app.

You can see what guid the app has as the last part of the url.

/gg

Thanks, Gandalf. On our server there is no 'Script' directory under Log. I checked QMC for any options. So far I only found "enable logging" for the engine, which is already enabled. So I give your question back to you: how did you enable logging for the script?

Olaf

gandalfgray
Specialist II
Specialist II

Hi Olaf

I didn't enable it.

Have you performed any data loads on the server, maybe it's not created until you do?

I can't find anything about Load Logging in the Sense Help, it ought to be in the "Using the data load editor" part I think, but it's not there.

olaf_gschweng
Partner - Contributor II
Partner - Contributor II
Author

Hi Gandalf,

I did data loads on the server but there is no such directory. Thanks for your help anyway.

Olaf

gandalfgray
Specialist II
Specialist II

That's weird then..

Hopefully Daniel or some other Qlik person could sort out where and when data loads on the server is logged.

/GG