QVW gives error internal inconsistency, type CPV, detected

[loringl]

Hi, I have a qvw wich runs daily via QMC. Since a few days the run fails each time and I also can't open the qvw. I get;

Nothing has changed to the qvw. Any tips how to fix this?

[vincent_ardiet_]

See the error types here: https://community.qlik.com/t5/Official-Support-Articles/Qlik-Engine-Internal-Inconsistency-Errors/ta...

If this is due to the memory, maybe could you try to open without data in order to change your script and reduce the amount of data loaded.

[David_Friend]

@loringl what size is that QVW? Like @vincent_ardiet_  already mentioned you need to some data reduction most likely.

[loringl]

The size is 1 721 211 392 bytes
I tried opening without data but I get failed to load error and then failed to open.
Also tried moving it from the folder but no difference.

[David_Friend]

is that 1.7GB? I am guessing you are trying to open it using QlikView Desktop on your PC, how much RAM do you have?  Is QV Desktop licensed? If its showing 'Personal Edition' it won't be able to open the file, you have to lease a license from your QlikView server.

https://community.qlik.com/t5/Official-Support-Articles/How-To-License-QlikView-Desktop-Client/ta-p/...

[loringl]

Yes that is 1.7 gb. I'm trying to open it on the desktop and yes indeed without license... Will it open if I use a login with a license?

Correction it does not show personal edition, I'm on the server and it shows QlikView x64 but license info gives me User License (using license from server)

[vincent_ardiet_]

I've checked with one of my application which weights also 1.7GB (and yes this is not an exact science, it depends of the complexity of the datamodel and the visualisation).
Once opened, it is using 12GB of RAM, but during the opening it was using 20GB.
Do you have enough memory on your machine?

[loringl]

I checked and the machine has 32GB of RAM

[David_Friend]

I remember when that used to be a large amount, wow have times changed 🙂 my laptop has 32GB now! Trying bumping up to 64 and see if that helps.

[loringl · Accepted solution]

The solution that has proven effective for me is as follows:

1. Retrieve a previous version from the last 30 days of backups. I opted for the version from the day before the last successful run.
2. Perform a full reboot of the server.

Following these steps, everything is now functioning as it did before.