Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.
I have the following problem with my QMC tasks: they end up in Aborted status. Their connection to the database is OK (connection test suceeds), the server itself is whitelisted in the proxy settings, Hub is available and all the services are up and running. I 've also looked into the logs (scheduler), these two lines belong to the same app:
|50||126.96.36.199||20190106T051551.071+0100||ERROR||qlik||0b8e07b1-091b-4d0a-b18d-338a1f39c581||Command=Start task;Result=20;ResultText=Error: Failed||0||0||0||Not available||Not available||cc02c25e-d452-4192-b81e-60565d8d1677|4bdefe8b-1181-4244-b2dd-8742b8a007ee||NAME1||Scheduler||Not available||Not available||Start task||20||Found active session for Task. Task not started||0b8e07b1-091b-4d0a-b18d-338a1f39c581|
|51||188.8.131.52||20190106T051606.571+0100||ERROR||qlik||45ff698c-58ed-4d0d-901c-a9efa5260375||Command=Finished task;Result=65;ResultText=Error: Failed||03f3b52d-22a1-45a9-95dd-e5405cd254fb||0||0||INTERNAL||sa_scheduler||cc02c25e-d452-4192-b81e-60565d8d1677|4bdefe8b-1181-4244-b2dd-8742b8a007ee||NAME1||Scheduler||Not available||Not available||Finished task||65||Task finished with state Aborted||45ff698c-58ed-4d0d-901c-a9efa5260375|
I have already stopped and restarted the Scheduling Services without much effect.
When I try to manually reload an app, all I can see is that it kind of starts the reload but can't fetch any records. After a while it quits the process with a "Connection lost" message.
Do you have any idea how to solve this?
Any help would be much appreciated!
By manually reload you mean going to QMC and start reload or opening the .QVW and then clicking in Reload button or CTRL+R or F5? Can you open the specified document and reload without problem? Did the reload always had this problem or it is a recent unexpected problem?
Send a screenshot of the error that occurred please.
I've tried reloading the app both on the QMC and by opening the qvw. I have attached the error, this is what I see after almost an hour of running the reload process (this reload should take 1 minute max).
I would suggest that you look into the script log to understand when exactly the issue happens.
the last script log was created on 2018.12.31, but I don't see any error in them (QlikShare/ArchivedLogs/SERVERNAME/Script).
It is kinda weird that it stopped working in the "new" year. Definitely has to do something with that.
Hi Tibor. Please, open a support case (either with us, if entitled to direct support, or with your responsible partner).
Provide the details and use the log collector to get the log files from both before and after the issue started happening.