We are regularly suffering from restarts of QVS and have been working with Qlik to understand and fix these without much luck. We often get this message in the logs:
Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type ?, detected.
I found some info about these errors a while back (I forget the Source):
These “type” errors are fairly generic. However they only occur when something deep inside QlikView goes wrong. Historically this was often due to a bug but also can happen when the QVS.exe is allocated the maximum physical memory available. There’s no easy diagnosis here and we have to try various changes. QlikTech may ask you to put your QVS.exe into trace mode but usually only when a repeatable action can be executed that causes the failure. The output of the trace is passed over to R&D.
Here is the explanation of the ‘type’ errors:
Internal inconsistency, type A, detected. This error is signalled when QlikView gets a general exception when it tries to allocate memory.
Internal inconsistency, type C, detected. This error is signalled when the run-time terminates QlikView in an unexpected way.
Internal inconsistency, type D, detected. This error is signalled when QlikView gets a general exception on deletion of a dynamic array (TDynArray or TObjArray). Typically it is a side-effect of a failure (access violation) and the subsequent clean-up.
Internal inconsistency, type F, detected. This error is signalled when QlikView gets a general exception when it tries to allocate memory. (Same type of inconsistency as type A, but detected on another level)
So a typical error trigger can be memory allocation. This would be a Type F. By the nature of not being able to allocate memory, you’d expect Type D and C to follow. The memory allocation could be to the QVS.exe or to a single chart.
However more recently we are also seeing:
Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type B, detected.
Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type S, detected.
Has anyone got a full list of Internal Inconsistency types and their meaning?
This was something I did look in to. You simply change the setting as described above. i.e.
However some months ago we had to change the setting 'Server...' to 'Client initiates...' because of some session termination issues we were having.
The Qlikview setting for "Refresh Mode when document is Updated on Server" was set to "Client initiates refresh. If old data not kept on server or client too old, session will be disconnected" , this is incorrect as it clashes with the "Allow only one copy in Memory" parameter of the Qlikview server control Panel. "Server performs refresh automatically without any client action".
The statement about "A setting that may cause this..." was from Qlik (not myself) so I would take it with a large dose of salt.
Thx a million. I changed the settings for the application we faced this issue with. Since we had up to five errors of that type a day we shall rather quickly see results (or rather not see anything at all, since the error vanishes).
I did try changing the server settings, but the error still came up qhen I tried to draw a PieChart with multiple expressions. I tried changing some expressions, but the result was always the same. The application closes down and sometimes I get the following error. If I change the chart to use a Mekko chart, it renders just fine.
Add type CT to the mix. Occurred while opening a 250GB+ file, and while I already had 3 files open, one of which was also that size (and indeed a copy of the same file, but about a month old and with a different filename). Text was simply "Internal inconsistency Type CT" - nothing more. Can't screenshot because the app has since quit.