Qlik Community

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
Don't miss the upcoming Q&A with Qlik session on Qlik Application Automation on November 16th! REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
krilk
Contributor II
Contributor II

App Corrupted - exception -2

Hello, I'd like to reach out in order to understand the root cause of our recent App Corrupted issues that are making it impossible for us to do a PROD release with confidence.

This looks to be a random issue, using the same files it is possible to load the application successfully, but the same Application would be corrupt after a server restart.

 

We observe the following symptoms:

Engine.exe reaches high RAM usage(Sandbox: ~115GB, UAT: ~210GB), consequently crashing and displaying App Corrupted messag. Following log entries we capture every  time this happens:

WorkingSet: Virtual Memory is growing beyond parameters - 89.740(89.600) GB 0

Document Load: The document 56bbc826-16c0-4b8f-9ea6-8237e409b752 failed to load

DOC loading: LoadDocument caught exception -2 while loading document 56BBC826

Document Load: The document 56bbc826-16c0-4b8f-9ea6-8237e409b752 failed to load because file couldn't be loaded [3002]

 

Please assist

Labels (6)
2 Replies
gaidamichal
Partner
Partner

Hello,

Can you check the RAM footprint of that app? (ID 56bbc826-16c0-4b8f-9ea6-8237e409b752 it seems). The WorkingSet: Virtual Memory is growing beyond parameters error indicates that working set is being reached. What is the RAM amount on that server and what % is set in working set?

Regardless it's not really "corrupted" if you can open the QVF. Can you verify by moving the QVF elsewhere (even to open on QS desktop)? If it opens it's just a RAM issue, if not then it could have been damaged on publishing or migration (if the environments run different versions of Qlik Sense).

It seems to occur when the app is loaded into RAM after restart (first user opening maybe?) and there is not enough RAM to finish loading. Might be that there is simply not enough memory to finish the task. Similiar to QlikView issue here: (https://support.qlik.com/articles/000063182). Is the -2 the only exception number that you can see in the log?

krilk
Contributor II
Contributor II
Author

Hi Gaidamichal,

The footprint of the app is large only on the first user load. The engine is allowed 90% of the available RAM, which is a 128GB, 256GB and 1TB on dev, uat, prod respectively.

We've obviously not tried to deploy it to PROD due to the UAT issue, however we have noticed that problem on PROD in the past as well.

Sure, I do not think the QVF itself is corrupted, and everything points into a RAM issue, but something that I struggle to understand is why our PROD backup of the same application (Simply lacking some minor visual changes) will load reliably every time.

All our environments run the same QlikSense version.

We are also seeing the following entry:

Document Load: The document 56bbc826-16c0-4b8f-9ea6-8237e409b752 failed to load because file couldn't be loaded [3002]

Which we suspected might have something to do with the Binary load in our data load script, but that is not the case.

 

Thank you