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

[korsikov]

Hi Tyler.

Can you help me. I'm have dev server w2012r2 with installed QV 12 desktop, QV 12 server. I'm deinstall QV 12 server and install QS 3.0. and faced with problem - operaion monitor not reload.

Reload stop on line " LIB CONNECT TO 'qrs_user';"

with error "Could not fetch connection by name using identifier qrs_user: LIB CONNECT TO 'qrs_user'"

Operations_Monitor_Reload_Stats_3.0.0.txt in attach and task log too

I think may be the cause of conflict with any previously installed QVRestConnetor, but why Licence monitor reload success.

[pnowicki]

Ok, it appears that this was the issue. The service account had it's access turned to "inactive" and "removed externally" which was an issue in the user directory connector.  Once the status of the service account was restored the reports ran no problem.  Thanks for the help. 

[mountaindude]

Coming late to this discussion, but having the same problem.

Trying to reload the Operations Monitor that ships with Sense Enterprise 3.0.1, and get this error:

The following error occurred:

Could not fetch connection by name using identifier qrs_user

The error occurred here:

LIB CONNECT TO 'qrs_user'

Have made the sa_repository user RootAdmin. Btw, I didn't see any reference to sa_repository user above, but that would be the user - right? AFAIK that name is configured by the Sense installer, which makes it a bit strange if it is called different things on different systems...

Running the reload while RDP:d into the server, logged in as a Windows user that is both domain Admin in Windows and RootAdmin in Sense.

Virtual proxies were mentioned earlier - we do have a bunch of them.

[korsikov]

you need set RootAdmin role to Qlik Sense service user.

[mountaindude]

Yeah I know - that was first thing I did. That seems to be pretty well documented in Qlik's knowledgebase too.

[mountaindude]

Duh.

Was running the reload from the Hub (while RDP:d into the server). But the Sense user I was logged in as did not have access to the qrs_* data connections. Adding a suitable security rule to those data connections, and things are hunky dory again.

[mountaindude]

This doc is pretty useful, btw:

https://help.qlik.com/en-US/sense/3.0/pdf/Monitor%20Qlik%20Sense%20sites.pdf

[Anonymous]

Hi Tyler.

I seem to be having the same problem.

However, using QMC, i am able to load the license monitor, but not the operations monitor.

(View the .log file for the reloading of operations monitor as attached !.)

I am using virtual proxy with one node.

I have appended the prefix of the virtual proxy to the URL of the data connections (qrs_*) but to no avail.

I have set the reload user as root admin and these includes Sa repository and Sa scheduler.

Do note that i have read and tried these solutions.

Monitoring a Qlik Sense site ‒ Qlik Sense (Updating data connections due to prefix of virtual proxy).

Setting reload user, sa repository and scheduler to root admin.

Import and replace operations monitor on the monitoring stream.

Thanks all, appreciate your help.

[Tyler_Waterfall]

Hi gameoverzx‌ -

Thanks for posting after reading the help instruction and trying that out.

It appears that you are connecting fine to the QSR database with the REST connector but you are not fetching any data - which means that the data connections are set up in a way to connect okay.

This leaves at least two possibilities:

1. No permission to view data.
   1. You say the service account running the Qlik Sense Engine and Qlik Sense Repository services has been made RootAdmin?
   2. If you set yourself as owner of the data connection qrs_app (and you are RootAdmin), go out to hub, create a new app, open data load editor, and click the add data from the qrs_app data connection. Do you see data there? (It should show more than just "Root" in the data preview drop down.)
2. Something else related to your system . 
   1. Is this an upgraded environment?
   2. Can you open pgadmin (program files\qlik\sense\repository\postgresql\9.3\bin) and connect to the QSR database? (localhost, port 4432, postgres maintenance db)
      

[Anonymous]

Hi Tyler,

Thanks for your quick response.

1. No permission to view data.

     1. Yes. Service account running is RootAdmin and Qlik Sense Repository services has been made RootAdmin as well. (sa_scheduler and sa_repository).

     2. I have obtained the following screenshots for following the steps provided.

Does this mean that as a RootAdmin, i do not have permission to view data.

2. Something else related to system.

     1. To my current knowledge, this is not an upgraded environment.

     2. I am unable to locate the bin file within the folder. (Attached below)

[Anonymous]

Hi Tyler,

I would like to add on just in case i am off track. The initial problem was with reloading the operations monitor AND the license monitor in qmc and this is because the data connection "ArchivedLogsFolder" is unable to locate the file location. I have checked and there is no file labeled "ArchivedLogs" within C:\ProgramData\Qlik\Sense\Repository

Since then, i have changed the connection string of the ArchivedLogsFolder to C:\ProgramData\Qlik\Sense\Log\

This allowed for the reloading of the license monitor but not the operations monitor.