Qlik Community

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

korsikov
Valued Contributor II

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
Employee
Employee

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

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

korsikov
Valued Contributor II

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

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?

Employee
Employee

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

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.

pnowicki
Contributor

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

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.

korsikov
Valued Contributor II

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

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

Employee
Employee

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

Thanks Alexander-

It's simpler than that I believe.

  1. Go to "Services"
  2. Stop the Qlik Repository Service
  3. In the "Parameter" input box, add -record
  4. Start the Qlik Repository Service
  5. Start the other Qlik services
  6. 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.


Screen Shot 2016-07-25 at 11.42.42 AM.png

Employee
Employee

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

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)

pnowicki
Contributor

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

correct, no virtual proxy in place. 

Employee
Employee

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

Okay - the way to do this is to:

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

Screen Shot 2016-07-25 at 11.42.42 AM.png

Community Browser