article Qlik Engine: Internal Inconsistency Errors in Official Support Articles

Qlik Engine: Internal Inconsistency Errors

ToniKautto — Fri, 01 Apr 2022 00:29:20 GMT

The Qlik Associative Engine registers Reason for restart: Internal inconsistency error.

The Qlik Associative Engine in Qlik Sense and QlikView may restart automatically due to Internal Inconsistency error. The list provided below is meant as a general guideline to assist in locating the root cause for the various inconsistency types.

Type	Details
A	General exception when Engine fails to allocate memory. Troubleshooting Qlik Engine "Internal Inconsistency Type A" Error
B	Failed attempt to release memory that is no longer allocated. Typically it is a side-effect of a failure (access violation) and the subsequent clean-up. Troubleshooting Qlik Engine "Internal Inconsistency Type B" Error Qlik Sense nodes show as stopped in QMC and "Internal inconsistency, type B" errors in Engine logs
C	Run-time terminates QlikView in an unexpected way. Troubleshooting Qlik Engine "Internal Inconsistency Type C" Error
CPV	General exception when Engine fails to allocate memory with an increased memory quota. Similar to type A but detected on another level. QlikView Server restart in loop with "DOC loading: LoadDocument caught exception -2" error "Internal inconsistency, type CPV" error in QlikView Desktop when downloading document from access point
CRT	Triggered by QlikView shared file corruption
CT	CPU Throttle control exception "Internal inconsistency, type CPV" error in QlikView Desktop when downloading document from access point QlikView Server restart in loop with "DOC loading: LoadDocument caught exception -2" error
D	General exception during deletion of a dynamic array(TDynArray or TObjArray) Typically it is a side-effect of a failure (access violation) and the subsequent clean-up. Troubleshooting Qlik Engine "Internal Inconsistency Type D" Error QlikView: "Out of Virtual memory" or "Internal Inconsistency" errors in 32-bit environment
E	Engine attempts to flush memory and has looped more than 100 000 times on one memory block size. The blocks are tied together in linked lists, so the loop indicates a circular reference in the list of allocated blocks.
F	General exception when Engine fails to allocate memory. Similar to type A but detected on another level.
MT	QlikView Desktop attempts to reach a previously used server that is no longer accessible
S	Document session fails and is forced to close. For example when a document that is already opened is reloaded and distributed.
L	Circular reference has been found in the global memory pool.
T	General exception that does not indicate an explicit root cause. Possible reasons for this exception can be e.g. memory access violation, which may indicate general memory shortage or security software scanning blocking memory access. If the error persists, please raise a ticket with Qlik Support with complete logs for the time occurred and Qlik Engine core dump file.
SE (WF)	"FailFast" system that detects access violations
WH	General exception in WinHTTP callback. The WinHTTP library is used internally by the Qlik Engine for making asynchronous HTTP calls. The error can be caused due to network issues or while the asynchronous callback function provided to WinHTTP is getting executed by the Qlik Engine internally to process any progress updates for the request. If the error persists, please raise a ticket with Qlik Support with complete logs for the time occurred and Qlik Engine core dump file.
Simple Request	Internal inconsistency exceptions that do not match any of the above types are logged as general exceptions.

Related Articles

Environment

Qlik Sense, all versions
QlikView, all versions

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

Re: Qlik Engine: Internal Inconsistency Errors

Emmanuelle__Bustos — Wed, 30 Mar 2022 22:24:12 GMT

Hi Tony,

What about Type T:

"Error Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type T, detected"

Re: Qlik Engine: Internal Inconsistency Errors

ToniKautto — Fri, 01 Apr 2022 00:30:04 GMT

@Emmanuelle__Bustos Type T is unfortunately not very explicit, but I have updated a short note in the table.

Re: Qlik Engine: Internal Inconsistency Errors

Emmanuelle__Bustos — Fri, 01 Apr 2022 00:38:58 GMT

@ToniKautto

Excellent, in our case it was because of AV blocking directories.

Thank you for the update.

Re: Qlik Engine: Internal Inconsistency Errors

fmarvnnt — Thu, 06 Apr 2023 09:05:01 GMT

What about type TM? It happens on a QS Nov 2021 production site.

Thank you in advance,

FMa

Re: Qlik Engine: Internal Inconsistency Errors

Sonja_Bauernfeind — Thu, 06 Apr 2023 09:33:22 GMT

Hello @fmarvnnt

Reviewing previous instances of this in our internal tickets, TM is related to memory access/corruption issues (much like T).

I can reach out to our subject matter experts to see if we can get additional information.

All the best,
Sonja

Re: Qlik Engine: Internal Inconsistency Errors

Sonja_Bauernfeind — Thu, 13 Apr 2023 14:25:51 GMT

Still looking into this for you.

Re: Qlik Engine: Internal Inconsistency Errors

Sonja_Bauernfeind — Fri, 14 Apr 2023 13:30:44 GMT

Hello @fmarvnnt

TM is an unhandled exception on Windows runtime, usually an access violation. It occurs in the internal timer thread. This thread is a high-priority thread that performs delay, await and timeout services to the engine runtime system. It's a very shallow and uncomplicated functionality, and the timer thread is usually just a victim of another request or thread using the services and then unexpectedly terminating, leaving some timer registration trashed.

Not much can be deduced from this alone.

All the best,
Sonja

Re: Qlik Engine: Internal Inconsistency Errors

fmarvnnt — Fri, 14 Apr 2023 13:45:14 GMT

Thank You Sonia, I'll monitor the site in order to get more info.

Regards,

FMa

Re: Qlik Engine: Internal Inconsistency Errors

fabdulazeez — Tue, 30 Jul 2024 07:26:46 GMT

While I was working in the hub, I received an error message saying "Engine not available." The engine status was showing as stopped in QMC, but when I checked the services, the engine service was running. The status in QMC eventually changed to running after some time. I can see below error in logs.

"Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, general exception detected (Simple Request)"

According to the article, this is classified as a general exception. How should I proceed? Should I log a support ticket? The error isn't frequent, but I'm sure I've encountered it before.

Re: Qlik Engine: Internal Inconsistency Errors

Sonja_Bauernfeind — Tue, 30 Jul 2024 09:06:13 GMT

Hello @fabdulazeez

We recommend investigating the Engine first, reviewing log files previous to the restart.

Some points to look into:

Resource usage (CPU, memory, disk)
What apps were being used at that point (can you see a pattern between the restarts?) and what objects and users were active

This is not an extensive list, but should help you get started.

If the above doesn't lead you to a solution and your environment remains unstable, please log a case.

All the best,
Sonja