Qlik Community

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Not applicable

Operations Monitor 3.0.0 reload fails

Dear everyone

Since a couple of weeks our Operations Monitor's reload task fails (last successful reload: 25.5.2016).

Error message in log file: "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, Operations Monitor"

No idea where it could come from, as far as I know no one was changing any REST connector settings.

Hope anyone can help

Best regards

Michael

1 Solution

Accepted Solutions
korsikov
Valued Contributor II

Re: Operations Monitor 3.0.0 reload fails

give Qlik Sense service user role RootAdmin

13 Replies
korsikov
Valued Contributor II

Re: Operations Monitor 3.0.0 reload fails

give Qlik Sense service user role RootAdmin

korsikov
Valued Contributor II

Re: Operations Monitor 3.0.0 reload fails

Not applicable

Re: Operations Monitor 3.0.0 reload fails

Gorgeous!

Thanks a lot, it works =)

Not applicable

Re: Operations Monitor 3.0.0 reload fails

Just to clearify

Under "Users" in the QMC

Give the user "System" (It has the User Directory: NT AUTHORITY) RootAdmin

You can do this by selecting it in the list and then Editing it and adding the "RootAdmin" role to it.

Not applicable

Re: Operations Monitor 3.0.0 reload fails

Thanks Alexander, it works perfectly!

Not applicable

Re: Operations Monitor 3.0.0 reload fails

I have the same problem, but the solution does not work for me. We have a seperate scheduling user set up, "sa_scheduler". This user has been granted the root_admin role but the refresh fails with the exact same error.

fginfrida
New Contributor II

Re: Operations Monitor 3.0.0 reload fails

Simon,

I'm experiencing a similar problem with QS June 2017 (QS server 11.11.1) running on Windows Server 2016.

I receive the same error message, but there is no user "System" under QMC users. The list of users:

francis_ginfrida (my logon)

qvadmin, sa_api, sa_converter, sa_engine, sa_hub, sa_printing, sa_proxy, sa_qlikview, sa_reporting, sa_repository, and sa_scheduler.  I've assigned RootAdmin to qvadmin, sa_engine, and sa_repository to no avail; the error recurs. 

Do you have a suggestion?

Thanks,

Frank.

santoshknc
Contributor

Re: Operations Monitor 3.0.0 reload fails

Hi Francis,

Any updates on this issue ?

Thanks & Regards,

Santosh Kumar.

fginfrida
New Contributor II

Re: Operations Monitor 3.0.0 reload fails

Santosh,

Thank you for reminding me.  The update was on my to-do list.

The issue in my case had to do with QS behavior in migration.  In my development environment (using QS desktop), I had used the generic ODBC connection to an Oracle DB, using the connection information in TNSNames.ora and a System DSN file.

The migration switched to the Qlik ODBC Connector Package.  Even though that connection reported "Connection Successful" when tested, it would not load data.  The notes that I created for the Qlik Admin are attached.

Issues

  • When the file is migrated, Qlik creates a data connection on the server and associates the connection in the file with that connection.
    • Connections can be viewed from the QMC (Manage Content…Data Connections).
    • Do not assume that the connection will be the same as the connection on the desktop. Applications will be developed using the generic ODBC connector; when the file is migrated the connection will be changed to the Qlik ODBC Connector Package.  That package will not point to the DSN and the TNSNames entry referenced in the DSN.  The application will report “Connection Successful” when the connection is tested, but will not load data.
    • It will be necessary to create a new data connection that points to the DSN in each application that is migrated.  When you do so, the Qlik server will either create a server connection or, if the connection has been created previously, use an existing connection. The server identifies data connection by name, so you must use the exact name that exists.
Community Browser