Reload in HUB fine but not in QMC

[carpeimagos]

We have just move the hole Qlik Sense Enterprise platform to a new more secure environment by doing full backup and restore of everything. The hole Qlik Sense is up and running good, but... 

In the old environment every app reload runs perfect both in QMC with tasks and in the HUB with reload button.

And now i the new environment almost every app reloads perfect both in QMC with tasks and in the HUB with reload button. But some will not. In the HUB all perfect, but not in QMC when same app loads with a task.

Same apps, same task setup, same Qlik Sense version, same data connections etc only moved to a new environment.

So why strange load error i QMC and not in HUB?

[Maria_Halley]

Do you get any error message? Anything in the log that gets generated when it tries to reload?

[carpeimagos]

Yes we get some error message in the loadlogs, but they aren't  so relevante to the basic error. We got errors about Oracle Call Interface (OCI) and dateformat, despite that we don't use any kind of date in the load scriptm like Where INDATE = '2021-03-29' (Swedish format). We also got errors like 'Cant't find field X', but field X exist. The error are generated we access Oracle databases. This is the same database as before, with the same way to connect and extract data.    

[Maria_Halley]

Is it only the apps that are using this connector that has the problem?

[vegard_bakke]

Executing reloads from the QMC, is being run as INTERNAL\sa_scheduler, and not as the owner of the task or the app.

Therefore, you may be able to reload an app that is using a data connection that only you have access to. But when reloading it as a task, it will fail if INTERNAL\sa_scheduler does not have access to this data connection.

(Sadly, the opposite is true, also. If you can deploy an app, you can use data connections that you won't have access to with your own user. At least it was like this. In the thread Solved: Security rules on data connections can easily be c... - Qlik Community - 1663644, a fix was scheduled for release in Feb 2020. But I haven't checked yet if or how it has been implemented.)

Not sure if this helps. Hope it does. 🙂

Vegard

[carpeimagos · Accepted solution]

Thank's for all inputs. Our solution was to reinstall Oracle OCI clients on all Qlik Sense nodes (servers). We also notice that after the full restore/backup from old to new environment, none of the old data connections did worked. So we have to open, edit and save them ones more to get them to work. So that's our solution.