This is a fix for issues relating to the Operations Monitor not reloading in 3.0 with the error message in the script log of "There was a problem fetching data from QRS via the REST connector." Example:
Load There was a problem fetching data from QRS via the REST connector. Reload terminated. QRS Row Counts: qrs_user = 0 lines, qrs_app = 0 lines, qrs_appobject = 0 lines, qrs_task = 0 lines,
Error: Syntax error, missing/misplaced FROM:
The root cause here is pending investigation by R&D, but the Rest connector used by the Operations Monitor requires some level of access by the service account, albeit the level can be minimal like in the example above.
The cause for this issue tends to be that the service account running Qlik Sense Services does not have sufficient access as determined by the security rules to perform the reload.
Assigning the Qlik Sense Service account as a RootAdmin will accomplish this task, but that is a high level of authorization. Minimally this style of security rule should suffice:
In this example the filter applies only to streams (Stream_*) and we are granting read only access (read), setting the condition(s) for this security rule apply only to the UserID of the Qlik Sense Service account, and the context is scoped to only the QMC.
This functionally means that the Qlik Sense Service Account can only read, but do no modifications to streams in the QMC. Example view of this user's access:
If you do not know the service account being used by Qlik Sense, then you will need to login to the the server running Qlik Sense Enterprise, then:
- Windows 2008: Start > Run > services.msc
- Windows 2012: Start > Search for services.msc
Scroll down to the Qlik Sense Services and note the account running the Qlik Sense Engine service.