Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
LDR
Creator II
Creator II

Scheduled tasks fail if tasks are started manually

Hi Qlikers,

I'm facing a weird situation, at least for me. On of my servers was running out of disk space, then any app wasn't able to be updated as it was scheduled. Once I released enough space, any task executed automatically by the scheduler run but, if any task is started manually it didn't. 

 

Checking the service engine log file I found that:

LDR_0-1715856556270.png

 

But the Engine service is running, etc.

I restarted any Qlik service and the error continues happening.

Did anyone face any situation like that? how it was fixed?

 

Thanks in advance

 

Labels (2)
1 Solution

Accepted Solutions
LDR
Creator II
Creator II
Author

Finally I found what was wrong. I don't know why but due to his lack os disk space some of the apps with failed tasds, got corrupted. For those apps I tried to update their data opening app by app and  they failed too with the same error related to internal engine error.

 

So finally, I had to spend some time but following the steps below I was able to have my environment running again:

1- Duplicate affected app.

2- Link the existing task with the new app.

3- Run the task. It always works.

4- Delte the old app and publish the new one.

 

Doing that I was able to replace the corrupted apps.

 

Regards

View solution in original post

1 Reply
LDR
Creator II
Creator II
Author

Finally I found what was wrong. I don't know why but due to his lack os disk space some of the apps with failed tasds, got corrupted. For those apps I tried to update their data opening app by app and  they failed too with the same error related to internal engine error.

 

So finally, I had to spend some time but following the steps below I was able to have my environment running again:

1- Duplicate affected app.

2- Link the existing task with the new app.

3- Run the task. It always works.

4- Delte the old app and publish the new one.

 

Doing that I was able to replace the corrupted apps.

 

Regards