topic Re: Operations Monitor 3.0.0 reload fails in Management & Governance

Operations Monitor 3.0.0 reload fails

Thu, 28 Jul 2016 13:52:20 GMT

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

Re: Operations Monitor 3.0.0 reload fails

korsikov — Fri, 29 Jul 2016 06:03:34 GMT

give Qlik Sense service user role RootAdmin

Re: Operations Monitor 3.0.0 reload fails

korsikov — Fri, 29 Jul 2016 06:04:39 GMT

Operations Monitor 3.0 fails to reload - can't connect to QRS with REST connector

Re: Operations Monitor 3.0.0 reload fails

Fri, 29 Jul 2016 07:40:07 GMT

Gorgeous!

Thanks a lot, it works 😃

Re: Operations Monitor 3.0.0 reload fails

Wed, 10 Aug 2016 09:07:50 GMT

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.

Re: Operations Monitor 3.0.0 reload fails

Fri, 11 Nov 2016 16:22:07 GMT

Thanks Alexander, it works perfectly!

Re: Operations Monitor 3.0.0 reload fails

Tue, 02 May 2017 08:06:56 GMT

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.

Re: Operations Monitor 3.0.0 reload fails

fginfrida — Mon, 27 Nov 2017 20:58:16 GMT

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.

Re: Operations Monitor 3.0.0 reload fails

santoshknc — Tue, 19 Dec 2017 17:36:37 GMT

Hi Francis,

Any updates on this issue ?

Thanks & Regards,

Santosh Kumar.

Re: Operations Monitor 3.0.0 reload fails

fginfrida — Tue, 19 Dec 2017 18:28:47 GMT

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.

Re: Operations Monitor 3.0.0 reload fails

santoshknc — Mon, 08 Jan 2018 05:28:49 GMT

Hi Francis,

Thanks for the inputs. I just brought the Apps from the default folder lcoation and did the reload part.

However i am unable to delete the old Operations Monitor App in the server and i am getting the error as

"Cannot read property 'forEach' of undefined in qliksense".

You got any idea on this? any help you can provide ?

Thanks

Santosh.

Re: Operations Monitor 3.0.0 reload fails

fginfrida — Mon, 08 Jan 2018 14:42:58 GMT

Santosh,

I've not experienced the issue/error that you report, so I can't provide a specific suggestion or help.

However, the Operations Monitor appears in a published stream, so you could try "unpublishing" by duplicating it (which will put the duplicate in "My Work"), then deleting it.

Frank.

Re: Operations Monitor 3.0.0 reload fails

santoshknc — Tue, 09 Jan 2018 04:48:11 GMT

Hi Francis,

Yes, I also got the imported the default Operaions Monitor app and reloaded and its workingg fine.

But i am unable to delete the existing operations monitor app which was giving issues..

I think have to find a way to delete the record from postgreSQL DB but its taking risk in the DB modification.

Thanks,

Santosh.

Re: Operations Monitor 3.0.0 reload fails

hbandari3636 — Tue, 03 Apr 2018 15:06:03 GMT

I have a similar problem which I am facing for a while. Can you please help me on this?

User System with User Directory NT Authority created in Qlik sense installation

Thanks in advance.

Hemantha