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

Announcements
AWS Degraded - You may experience Community slowness, timeouts, or trouble accessing: LATEST HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
Despotis
Contributor II
Contributor II

Reload task works in App, but not in QMC

Hi,

while reloading data from inside the app works perfectly, every reload try in qmc is failing.
As you can see in the log, the database connection is working properly, all selected lines are fetched correctly, the $syn tables are created automatically but in the penultimate line the task fires an error, see attachment. Unfortunately "Execution Failed" is not that meaningful, so i don't have an idea what's going wrong.

I read in another thread, that it could be important to consider "INTERAL\sa_scheduler" as ADMIN in the section access, which i did as well, just to make sure that this is not the problem.

Thanks in advance
Stefan

PS: Why can't i upload a .log file? 

Labels (2)
1 Solution

Accepted Solutions
Despotis
Contributor II
Contributor II
Author

First of all, thanks  @Vikram_Jayakumar for trying to help!

Now coming back to my problem. It was really hard to find out what is going wrong, since i'm migrating the apps from our 'old' server to out 'new' server. And all apps and reload tasks were working perfect! The old server is running Qlik Sense 12.212.4, the new server is running 12.969.2.

I tried several things to find the "real" problem and it turned out, that it has to do with Section Access. Whenever i left out the Section Access directive, the task was loading fine! After much more searching I found somwhere in the forums, that it might could be necessary to add the sa_scheduler to the permissions list. In the example, the guy wrote something like "add INTERNAL\sa_scheduler to your list" in another thread. I was sekptical but gave it a try. It didn't work.

Long story short, you have to put the sa_scheduler to the permissions list, obviously this is new compared to our old server. But, i had to capitalize sa_agent. So after adding INTERNAL\SA_SCHEDULER, the reload tasks are working flawles.

But why do i need to store the USERID for Section Access capitalized?

View solution in original post

4 Replies
Vikram_Jayakumar

Hi @Despotis 

Is it for all the tasks or one in particular? If only one try duplicating the app and schedule the task for that 

If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.
Despotis
Contributor II
Contributor II
Author

Hi @Vikram_Jayakumar 

It is for all tasks and apps, no matter whether just a single "reload now" or a scheduled job on a recurring basis. And it doesn't matter if the app is in my "personal working space" or already published to a stream.

Vikram_Jayakumar

Hi @Despotis 

That is odd, Just to verify does your service account has read/write access to clustered path. Also for testing create a new app with some folder connection and try scheduling from QMC

If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.
Despotis
Contributor II
Contributor II
Author

First of all, thanks  @Vikram_Jayakumar for trying to help!

Now coming back to my problem. It was really hard to find out what is going wrong, since i'm migrating the apps from our 'old' server to out 'new' server. And all apps and reload tasks were working perfect! The old server is running Qlik Sense 12.212.4, the new server is running 12.969.2.

I tried several things to find the "real" problem and it turned out, that it has to do with Section Access. Whenever i left out the Section Access directive, the task was loading fine! After much more searching I found somwhere in the forums, that it might could be necessary to add the sa_scheduler to the permissions list. In the example, the guy wrote something like "add INTERNAL\sa_scheduler to your list" in another thread. I was sekptical but gave it a try. It didn't work.

Long story short, you have to put the sa_scheduler to the permissions list, obviously this is new compared to our old server. But, i had to capitalize sa_agent. So after adding INTERNAL\SA_SCHEDULER, the reload tasks are working flawles.

But why do i need to store the USERID for Section Access capitalized?