An Error Occured: Internal Engine Error

[parthakk]

Hi Everyone,

We have developed 5 applications and all have been published. Everything works fine except for one. In one of the application when we try to search, a pop message gets displayed saying its Internal Engine Error.

I have gone through some of the discussion in this forum which suggest of restarting services, it does solve problem but we cannot restart services every time.

Kindly suggest how this issue can be handled. Is it a bug or there are any changes that need to be done.

Thanks,

Partha K

[Vegar]

Are you using Qlik Sense 2.x? If you are then I could be a problem work your app.  Try to export the app from QMC and open it in the Desktop client. If it works in the app then save it and import it to the server again.

[#3]

Hi Partha,

Expect for one person / Expect one report?

Please check the log file , you may get more details, this could be some times network issues..

Thank you...Ravi Kancharla

[ift_isabelle]

Do you have enough Memory and CPU available?

If your CPU is higher then 95% or your memory is higher then 95% you can also get this error...

[parthakk]

Hi Vegar,

I am using server 3.0.

I tried it in loacal system and it seems working fine. I saved application and when imported the same issue is occurring again.

Thanks,

Partha K

[parthakk]

Hi Kancharla,

It happens for all users but only for one or two application. And there is not network issue either.

Regards,

Partha K

[parthakk]

Hi Isabelle,

I have enough memory and CPU. Its completely fine for all application except for one.

Even in one application, there is no performance issue or anything. Only when i go for global search it throws an error.

Regards,

Partha K

[Vegar]

This is behavior sounds strange. I have no other suggestions other than to file a support case. Please update this thread if you do find a solution to this issue.

[#9]

Hello,

are there any news on this topic? I am experiencing the same behaviour...

Regards,

Tobias

[vlad_komarov]

If the problem is fixed by restarting services, than your system resources are causing this issue, most likely.

Try to check what's happening on your server while users are doing the search. you might see a spike in Memory or CPU usage.

I would suggest to check your data model and see if it's optimally designed.

How many active pages you have in this app? Is this problem occurs on every page?

Try to select some item in your application and do a search after that...

Is it happening with ANY search?

Try to load a limited set of records and see if this problem still occuring...

It sounds like a bug in QS, but it's not the first one.... The system is not yet stable enough, despite the 3 major releases...  So you just need to find a workaround or re-design your app.

VK