QlikSense Engine Crashes : Internal inconsistency errors

[asmitamkhrj]

Hi All,

We are currently running in a problem where we face frequent QlikSense engine service crashes with the following errors :

1. Internal inconsistency, type CPV, detected.

2. Internal inconsistency, general exception detected (Simple Request).

3. Internal inconsistency, type A, detected.

4.  Internal inconsistency, type TM, detected.

5. Internal inconsistency, type CT, detected.

6. Internal inconsistency, type F, detected.

Any help would be apprrciated.

[Øystein_Kolsrud]

The first thing I typically check when I'm experience engine instability is to check if it's running out of memory. Check the logs for messages indicating that you're in the "critical" memory level:

https://community.qlik.com/t5/Knowledge-Base/What-does-quot-Warning-WorkingSet-Virtual-Memory-is-quo...

If that is not the case, then I'd recommend you to contact Qlik support.

[asmitamkhrj]

Hello, You are monitoring these messages in Engine/Trace logs I believe ?

[Øystein_Kolsrud]

Yes, exactly. More specifically I think you'll find them in the System-logfile of that folder.

[asmitamkhrj]

Yes, I have checked that, couldnot spot "Working Set : Virtual memory errors/ warnings".

I found this resolution, that is for QlikView, but I don't think this is applicable to QlikSense.

• Stop the QlikView WebServer Service or the QlikView Settings Service
• Navigate to C:\Program Files\QlikView\Web Server
• Open QVWebServer.exe.config
• Inside the <appSettings> section, add the following key (if not already present):
  <add key="SocketTimeOutInSeconds" value="600"/>
• Save the file, and start the QlikView WebServer Service or the QlikView Settings Service

https://community.qlik.com/t5/QlikView-App-Dev/Internal-inconsistency-type-CPV-detected/td-p/1298867

I have reached the support, did not hear back form them yet. 😞 

[Øystein_Kolsrud]

Have you looked at the memory consumption profile of the machine where you get these errors? It might be that there are other large processes there that prevents the engine from even reaching the low-water mark before struggling to allocate the memory it needs. If that is the case, then you might want to check if you can remove some of those processes from the node or possibly tune the high/low water marks for the engine memory in the QMC.

Here is some more trouble shooting information on the topic: https://community.qlik.com/t5/Knowledge-Base/Troubleshooting-Qlik-Engine-quot-Internal-Inconsistency...