topic Operations Monitor 3.0 fails to reload - can't connect to QRS with REST connector in Management & Governance

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

korsikov — Fri, 22 Jul 2016 09:39:33 GMT

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.

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

Tyler_Waterfall — Fri, 22 Jul 2016 11:25:17 GMT

korsikov‌ - Thanks for the post.

Can you be sure that the service account running the reload (i.e. running the Qlik services) is a root admin and that sa_repository is also a root admin on the server?

We have seen this before and sometimes adding rootadmin role to any account that is reloading the apps can resolve it.

Let me know. Thanks!

Tyler

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

korsikov — Fri, 22 Jul 2016 12:01:39 GMT

Thanks for the quick response. But he has already come to the same decision.

For the first time confronted with the fact that we have to do on behalf of the user running the Server service which root administrator.

There are other servers that are upgraded from older versions of the server in these services user does not have the right root admin but reload performed normally. Why can this be?

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

Tyler_Waterfall — Fri, 22 Jul 2016 14:29:21 GMT

Can you help us debug this by running the Qlik Repository service with the -record parameter?

You do this by changing the option in the windows Services for Qlik Repository Service and adding "-record" as a startup parameter and then restarting the service (which will restart all services).

Try reloading both apps a few times and then gather the logs which are produced.

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

pnowicki — Fri, 22 Jul 2016 14:31:49 GMT

currently having the same problem, just posted on a separate thread. here is the snippet of the error from the load script of my license monitor. I made the sa scheduler and sa repository root admin but that didn't resolve it.

2016-07-22 08:26:52 0457 CALL qrs_userAccess

2016-07-22 08:26:52 0458

2016-07-22 08:26:52 0478 *** CONNECT TO ***

2016-07-22 08:26:53 0480 RestConectorMasterTable:

2016-07-22 08:26:53 0481 SQL SELECT

2016-07-22 08:26:53 0482 "id" AS "id_u0",

2016-07-22 08:26:53 0483 "createdDate",

2016-07-22 08:26:53 0484 "modifiedDate",

2016-07-22 08:26:53 0485 "modifiedByUserName",

2016-07-22 08:26:53 0486 "lastUsed",

2016-07-22 08:26:53 0487 "quarantined",

2016-07-22 08:26:53 0488 "quarantineEnd",

2016-07-22 08:26:53 0489 "__KEY_root",

2016-07-22 08:26:53 0490 (SELECT

2016-07-22 08:26:53 0491 "id",

2016-07-22 08:26:53 0492 "userId",

2016-07-22 08:26:53 0493 "userDirectory",

2016-07-22 08:26:53 0494 "name",

2016-07-22 08:26:53 0495 "__FK_user"

2016-07-22 08:26:53 0496 FROM "user" FK "__FK_user")

2016-07-22 08:26:53 0497 FROM JSON (wrap on) "root" PK "__KEY_root"

2016-07-22 08:26:53 14 fields found: id, userId, userDirectory, name, __FK_user, id_u0, createdDate, modifiedDate, modifiedByUserName, lastUsed, quarantined, quarantineEnd, __KEY_root, __extra_,

2016-07-22 08:26:53 Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 403 (Forbidden):

2016-07-22 08:26:53

2016-07-22 08:26:53 The server refused to fulfill the request.

2016-07-22 08:26:53 Execution Failed

2016-07-22 08:26:53 Execution finished.

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

korsikov — Fri, 22 Jul 2016 14:51:20 GMT

let's be clear.

I do it on the server where faced with this problem.

1. add to Qlik repository service option -record

old record "C:\Program Files\Qlik\Sense\Repository\Repository.exe" -iscentral change to "C:\Program Files\Qlik\Sense\Repository\Repository.exe" -iscentral -record

Restart Qlik Repository service

Delete role Root admin from qlik services user (qvsuser) then try reload application and then gather the logs

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

Tyler_Waterfall — Fri, 22 Jul 2016 15:52:19 GMT

Thanks Alexander-

It's simpler than that I believe.

Go to "Services"
Stop the Qlik Repository Service
In the "Parameter" input box, add -record
Start the Qlik Repository Service
Start the other Qlik services
Restart the Qlik Service Dispatcher

Start the License Monitor reload and the Operations Monitor reload.

When they finish, check the repository logs here:

If you can, email them to me twa@qlik.com so the developers can check them.

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

Tyler_Waterfall — Fri, 22 Jul 2016 15:53:17 GMT

To confirm for both of you, you have no virtual proxy prefixes in place? (Meaning, when you access the hub, you use something like https://servername/hub)

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

pnowicki — Fri, 22 Jul 2016 15:56:37 GMT

correct, no virtual proxy in place.

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

Tyler_Waterfall — Fri, 22 Jul 2016 16:11:05 GMT

Okay - the way to do this is to:

Stop the Qlik Sense Repository Database (stops all other services)
Stop the Qlik Sense Repository Service (if not already stopped)
In the "Properties" of the Qlik Sense Repository Database, add -record to the parameter at the bottom.
Click Start
Repeat 3 and 4 for the Qlik Sense Repository Service
Start all the other Qlik Sense services
You may have to restart the Qlik Sense Service Dispatcher at the end
Reload both Monitoring Apps (see the failure)
Send twa@qlik.com the following two logs, which are found in c:\
1. qrsresponses.txt
2. qrsrequests.txt
Turn off qrs recording by restarting all the services.

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

korsikov — Fri, 22 Jul 2016 16:20:06 GMT

Thn for clear instructions.

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

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

Tyler_Waterfall — Fri, 22 Jul 2016 17:01:33 GMT

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!

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

korsikov — Fri, 22 Jul 2016 18:14:55 GMT

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

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

Tyler_Waterfall — Fri, 22 Jul 2016 18:36:29 GMT

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?

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

korsikov — Fri, 22 Jul 2016 18:47:44 GMT

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?

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

Tyler_Waterfall — Fri, 22 Jul 2016 19:02:06 GMT

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?

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

korsikov — Fri, 22 Jul 2016 19:06:18 GMT

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.

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

Tyler_Waterfall — Fri, 22 Jul 2016 19:12:14 GMT

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.

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

korsikov — Fri, 22 Jul 2016 19:19:41 GMT

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"

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

Tyler_Waterfall — Fri, 22 Jul 2016 20:01:34 GMT

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