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.

[korsikov]

Thn for clear instructions.

I am not use custom virtual proxy. But can not see different. Because I'm run task in qmc.

[Tyler_Waterfall]

The virtual proxy would only come into play if it has a "prefix" (which is not default - blank). So, unless you know that you changed the virtual proxy prefix, then we can be sure that the "prefix" name is not the issue.

But yes, if you can capture those logs - that would be awesome!

[korsikov]

good night, Tyler.

I am do all what you want. logs in attach

1. qvsuser without Root Admin task -failure

2. qvsuser with Root Admin task success

wait for your decision

[Tyler_Waterfall]

Thanks Alexander!

You might have been experiencing the RootAdmin issue which causes a failure. (There is another different issue)

When you get back on Monday, can you confirm that you get data in the License Monitor for users - namely User Name - when it succeeds?

[korsikov]

thx for quick replay.

I can connect from home via VPN  and obtain the necessary information.

open License Monitor - open User Name and see here users names. Is that what you needed?

[Tyler_Waterfall]

Yes- looks like you are in business!

Summary of korsikov‌ issue was giving the service account running Qlik Sense services RootAdmin rights in QMC.

pnowicki‌ - Does this address your issue?

[korsikov]

I want to note once again that I have other QS server version 3.0  which services user (qvsuser) does not have Root admin role  and everything works fine.

[Tyler_Waterfall]

Thanks! Yes, this is part of the mystery. Some reloads fail when user account does not have RootAdmin rights.

But with the other non-RootAdmin system - be sure to check that you get User data back (UserName). We have seen that the reload is successful without RootAdmin rights but there is no User data fetched from the QRS.

[korsikov]

You are completely right!  I checked on another server. I had not noticed it. In fact in the application  "licenses monitor"  no data in the field "user name"

[Tyler_Waterfall]

This is (somewhat) expected behavior. We don't want non RootAdmin people creating connections to the QRS and pulling back user data.