topic Re: Error code -128 in QlikView

Error code -128

krumbein — Mon, 29 Oct 2018 14:32:25 GMT

We have some QVWs running on a server via Windows tasks. Rather randomly they sometimes crash in the middle of a load operation with a log entry, which always looks something like this

2018-10-26 16:04:00 0293 EkVonOrig desc

2018-10-26 16:04:19 6 Felder gefunden: MarktNr, Datum, GebindeNr, EkWarenpreis, EkWarenpreisKalk, EkPfand,

2018-10-26 16:04:19 -128 =

2018-10-26 16:04:19 Fehler bei der Ausführung

2018-10-26 16:04:19 Ende der Skriptausführung

In the middle of the typical enumeration of found fields a "-128 =" appears on the next line. End of story. Or script...

Ever seen this? Ideas?

Sandro

Re: Error code -128

alextimofeyev — Fri, 23 Nov 2018 09:47:20 GMT

We've run into the same problem. Commenting to follow.

Re: Error code -128

krumbein — Fri, 23 Nov 2018 11:06:54 GMT

Let's collect some data

For us it is 12.20 SR7 and now 12.30 Initial Release. Executing in QlikView Desktop on Windows 10.

And you?

Re: Error code -128

alextimofeyev — Fri, 23 Nov 2018 11:14:37 GMT

We are on Qlik Sense November 2018 patch 1 (12.44.2).

Re: Error code -128

Anonymous — Mon, 24 Dec 2018 08:47:14 GMT

Did anyone find out what the cause of this problem is and how it can be fixed?

Re: Error code -128

Lauri — Tue, 19 Mar 2019 14:17:52 GMT

I was having the same error code (128) when running a load script in Sense Enterprise (Feb 2019). I determined that the error occurs when my script attempts to store data to a text file. One of the fields is the product of a hash function, so it contains many special characters (like /$%&"). (For example, the first occurrence is NFG4H0I2C#IP6--`?VN1Q/.)

The error only occurs when I try to store the hash field to the left of a date field (which contains slashes, like 1/1/2019). Sense seems to get confused about something about the two fields and throws the error before storing the first row of data (but after storing the field names).

So I put the hash field in the last position in my file and it works fine.

Re: Error code -128

Lauri — Wed, 27 Mar 2019 14:12:32 GMT

I spoke too soon (in my last post a week ago). The problem started happening again when my load script tried to export to txt even without Hash fields. Exporting to QVD works.

I tried exporting the data from the app sheet (right-click on table > Export > Export data), and got an "Access denied" message! Same for any object on the sheet. I waited a few hours and exporting started to work again.

I then found that November 2018 update 3 has been released, and the release notes state:

Jira issue ID: QLIK-92824
Description: An error in Qlik's Engine could make Excel exports in NPrinting fail with the error code -128 when several exports are made in a quick succession. This is now fixed.

This looked darn familiar, so I installed update 3, tried my script, and still got error 128.

At this point it feels very much like a bug and not an avoidable error so I'll try posting the issue to Support.

Re: Error code -128

Lauri — Wed, 27 Mar 2019 14:24:36 GMT

I found a support case (https://support.qlik.com/articles/000060597) that seems to address my issue:

Description
There is an unexpected behavior of the STORE statement in Qlik Sense version November 2018 when storing the data in TXT format.

When you try to store the data in TXT format then only the value in the first line of a table gets stored in the version November 2018.

Environments Qlik Sense November 2018 12.44.1 and 12.44.2

Cause
This behavior is caused by a bug (bug ID QLIK-92555)

Re: Error code -128

alextimofeyev — Wed, 27 Mar 2019 14:25:44 GMT

We found that in our case the error was caused by Exists() that had a non-existent field as one of parameters. For some reason, the error didn't occur at every reload.

Re: Error code -128

krumbein — Wed, 11 Dec 2019 07:49:02 GMT

Our current understanding of the situation is, that the server simply runs out of RAM. That seems to be the only commonality between all those errors we faced.

Once it went somewhere below 2GB of free RAM, it crashed. It is a development machine, which isn't that well equipped... We could follow its demise that by simply opening the resource monitor on the RAM tab and watching the numbers decrease until the crash happened

Sandro