Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
korsikov
Partner - Specialist III
Partner - Specialist III

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

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.




47 Replies
Tyler_Waterfall
Employee
Employee

Okay.

Regarding REST data connection - it looks like you are not finding data at the endpoint. Is this multi-node? If so, update the REST data connections' connection string URL to replace "localhost" with the fully-qualified domain name of the central node (or wherever the QRS database resides).

Also, this might be the issue with the ArchivedLogs Folder.

If you are running multi-node with sync, change the ARchivedLogsFolder data connection (in QMC) to point to the central node instead of to c:\programdata...

Or if you have shared persistence, use the ArchivedLogsfolder path listed in the "ServiceCluster" section in QMC.

Regarding the pgadmin, it is under Program Files, not ProgramData. Sorry, that wasn't clear in my original email.

Anonymous
Not applicable

Hi Tyler,

This is a single node.

I have shared persistence. Have changed the ArchivedLogsFolder data connection path to the folder listed in the service cluster.

Untitled.png

Still unable to reload operation monitor successfully. Thanks for your help, I think that this has to do with the connection string rather than the user rights to reload.

Tyler_Waterfall
Employee
Employee

ARchivedLogs folder is not under Qlik\Sense\Log but is either under \\FQDN_of_central_node\c$\ProgramData\Qlik\Sense\Repository\Archived Logs (in the case of single node or multi-node sync) OR at the path of the Service Cluster's archived log entries as shown in the "ServiceCluster" section of QMC (for shared persistence).

Tyler_Waterfall
Employee
Employee

Yes, something sounds strange here. I would try creating a new REST data connection to the app endpoint using https://FQDN_where_QSR_db_is/[any virtual proxy prefix with windows authentication/qrs/app/full

example:  https://myserver.domain.com/my_virtual_proxy_prefix/qrs/app/full

Check the existing qrs data connection to get an idea of the other settings.

If you can't access any app data (as root admin) with this new data connection, then there is something more going on.

Anonymous
Not applicable

Apologies for the late response. I have solved the issue by changing the following settings in the IIS server:

1. Add service account to Administrators group (Server Manager)

2. Change service account for all Qlik Sense engine service to the user account running the Qlik Sense server

Thanks !

rohitk1609
Master
Master

Hi,

I have updated the QRS connection string from https to http , added Archive folder to program data ,my account is root admin, I can restart the qlik services,It was working before upgraded to 3.2.4, same account I am using now, Please help me to make monitoring apps working again.

Thanks in advance

Best,

Rohit Kumar

Tyler_Waterfall
Employee
Employee

rohitkumar1609‌ - changing the URL to http will only work if your proxy is set to allow HTTP (check the proxy settings in QMC).

And you need to be sure you have a virtual proxy with "Windows Authentication" which either does not have a "virtual proxy prefix" or, if it does have a prefix, the qrs_ data connections' URL has been updated to include that prefix (https://myserver/prefix/qrs/app/full for example).

rohitk1609
Master
Master

Hi Tyler,

I have enabled HTTP and now my License Monitor app is working but Monitoring App is still now working , Is it because or Archive folder, I have just created one Archive folder but sub folder is not there, If you suggest I can add sub folders too ?

Tyler_Waterfall
Employee
Employee

When you say "Monitoring App" is still not working, are you referring to the Operations Monitor app is not reloading successfully? (Or the app doesn't look right when you open it even after successful reload?)

ArchivedLogs folder should look like this:

\ArchivedLogs

     \Server1

          \Engine

          \Repository

          \Proxy

          \Scheduler

          \...

     \Server2 (if you have multiple nodes!)

          \Engine

           ...

rohitk1609
Master
Master

Hi Tyler,

Thanks for instant response. I am talking about the Operation Monitor Apps reloading tasking is not getting successful. I am going to create archive folder and till please let me know this archive folder will help to make task reload ?