Knowledge

[ToniKautto]

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 p...
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 p...  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

• Troubleshooting QlikView Server resource problems and crashes 
• Qlik Sense - How to troubleshoot Engine related issue 

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.

[Emmanuelle__Bustos]

Hi Tony,

What about Type T:

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

[ToniKautto]

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

[Emmanuelle__Bustos]

@ToniKautto 

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

Thank you for the update.