Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
arethaking
Creator II
Creator II

Message from ReloadProvider: Reload failed in Engine. Check engine or script logs.

Hi Qlikians,
We got this error message at QMC log for 3 Qlik sense app reload which are reload in parallel.
What is the reason?
We have kept Qlik reload tasks default values “Task Session timeout“ of 1440 minutes (24 hours) and “Max retries” of 0.

Each reloads task will run at least 1.5 hours.

Please advise.

Hostname: Central_Node
2020-07-04 10:25:31 UTC
Max retries reached (0)
2020-07-04 10:25:31 UTC
Changing task state from Started to FinishedFail
2020-07-04 10:25:31 UTC
Message from ReloadProvider: Reload failed in Engine. Check engine or script logs.
2020-07-04 10:06:41 UTC
Changing task state from Triggered to Started
2020-07-04 10:06:41 UTC
Trying to start task. Sending task to slave scheduler Central_Node
2020-07-04 10:06:40 UTC
Changing task state to Triggered

 

3 Replies
Or
MVP
MVP

"Reload failed in Engine. Check engine or script logs."

I think you might want to check the engine or script logs...

Additionally make sure your reload server has enough resources for these tasks. In particular, if it is a virtual server with shared-pool resources, make sure you aren't taking up more resources than it is able to get from the shared pool.

arethaking
Creator II
Creator II
Author

Additionally make sure your reload server has enough resources for these tasks. In particular, if it is a virtual server with shared-pool resources, make sure you aren't taking up more resources than it is able to get from the shared pool.

 

How to check this?

 
 
 
 
Or
MVP
MVP

Have a chat with your local system / server administrators. This isn't a Qlik-related issue, it is related to how resources are assigned to virtual servers.