Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!

QlikView "Out of Virtual memory" or "Internal Inconsistency" errors in 32-bit environment

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

QlikView "Out of Virtual memory" or "Internal Inconsistency" errors in 32-bit environment

Last Update:

Nov 3, 2020 4:19:05 AM

Updated By:

Sonja_Bauernfeind

Created date:

Aug 12, 2013 12:09:15 AM

Regardless whether tried to run the script from Desktop or Server, the following error messages generated: 

Error 1: Out of Virtual and/or Logical memory, allocating <2MB>
Error 2: Internal inconsistency, type D, detected

Note: When verified the document logs, the following information was found:


18/07/2013 12:46:51 PM:      CPU Target                    x86
18/07/2013 12:46:51 PM:      Operating System              Windows 7 Professional Service Pack 1 (32 bit edition)
18/07/2013 12:46:51 PM:      Wow64 mode                    Not using Wow64

 

Resolution

The problem here is related to insufficient memory, which is also more limited in 32-bit environments. 

32-bit operating systems only support 32-bit memory addressing and thus are able to access only 4 GB of memory. The exception is if PAE or 4 GT is enabled, for reference see Physical Address Extension (Source: docs.microsoft.com).

QlikView is an in-memory technology and memory requirement is a reflection of document size and calculation complexity. If the business requirement for analytics can no longer be met with a 32-bit QlikView deployment, it is recommended to consider upgrading the server to a 64-bit operating system, as it will greatly increase the maximum memory capacity. 

Labels (1)
Contributors
Version history
Last update:
‎2020-11-03 04:19 AM
Updated by: