Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi
I feel confused and need help to find where to start troubleshooting.
We use QlikSense 2018November enterprise version. Our central node has been offline for a while. Restarting the server and services won't help. So we now live with the failover node - engine node.
Last weekend was the maintenance break. Today we found no app can be reloaded.
Error messages from QMC, task status: Message from ReloadProvider: Reload failed in Engine. Check engine or script logs.
But no script log has been generated. Engine log shows this error:
522 23.11.2.0 20190527T130007.537+0300 ERROR PROD-QSENG-W01 5b7e2d26-a802-414e-a416-5f1380a51b23 20190527T130007.516+0300 12.244.5.0 Command=Open app;Result=1003;ResultText=Error: App not found 0 0 25 SIEVOHOSTING mikkomy bfb48a98-7e6b-4cf7-950b-21819e8f7e4c d1797046-57cc-43c2-9100-99e5e5b9c005 Not available Engine Not available Global::OpenApp Open app 1003 Could not find app 5b7e2d26-a802-414e-a416-5f1380a51b23
Message from engine trace log:
DOC loading: LoadDocument caught extended exception 1003: App not found while loading document
I don't think this is related to central node, as we haven't used it for a while. But don't understand what went wrong so that the engine doesn't find all the existing apps...
Appreciate for your help!
Best regards
Susan
Hello,
I would start by making sure that the Qlik Shared folder is available from the rim node connected as the Qlik Sense Service account.
Also, make sure that the AppId you highlighted in the post is present in the shared folder.
If everything seems correct, try to restart the Qlik Sense services one more time.
Hope this helps!
Hello,
I would start by making sure that the Qlik Shared folder is available from the rim node connected as the Qlik Sense Service account.
Also, make sure that the AppId you highlighted in the post is present in the shared folder.
If everything seems correct, try to restart the Qlik Sense services one more time.
Hope this helps!
Thank you Bastien, restart services helped!
Just curious, can this problem be caused by services started in wrong order?
Hello Susan,
Great and glad that it helped!
I have seen this issue once before and this was caused by the Service Dispatcher (hosting multiple sub-services) not starting up correctly and being partially functional.
This should not have anything to do with the order normally but just to make sure you can check this page https://help.qlik.com/en-US/sense/April2019/Subsystems/PlanningQlikSenseDeployments/Content/Sense_De...
At the bottom, you will find the correct order to start up the Qlik Sense services.