Qlik Community

Ask a Question

App Development

Discussion board where members can learn more about Qlik Sense App Development and Usage.

Announcements
April 22, 2PM EST: Learn about GeoOperations in Qlik Sense SaaS READ MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
Sajid_Mahmood
Creator
Creator

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

Hi Qlik Experts,

IT IS TOP URGENT

Cannot reload both monitoring apps due to REST connector issues. For License monitor app, below error is appearing.

QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 403 (Forbidden):

The server refused to fulfill the request.
The error occurred here:
RestConectorMasterTable:

  SQL SELECT

      "id" AS "id_u0",

      "createdDate",

      "modifiedDate",

      "modifiedByUserName",

      "lastUsed",

      "quarantined",

      "quarantineEnd",

      "__KEY_root",

      (SELECT

          "id",

          "userId",

          "userDirectory",

          "name",

          "__FK_user"

      FROM "user" FK "__FK_user")

  FROM JSON (wrap on) "root" PK "__KEY_root"

QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 403 (Forbidden)

4 Replies
hugo_andrade
Partner
Partner

Sajid, suggestions:

find the account that runs the Qlik Sense services. Go to QMC and add the "Root Admin" role to it. This will ensure the account has access to the "qrs_*" data connections. Make the sa_ accounts "Root Admin" as well.

jordigonz
Creator
Creator

Hi Hugo,

I had the same problem and your solution worked for me.

Thank's!

luizcdepaula
Creator II
Creator II

Hi Hugo,

My account had all admin rights and still did not work. We realized that the system admins had not added the Qlik group to the service account created in AD. So, if you are using Active Directory, don't forget to add the Qlik group to the service account. Other wise, the service account in Qlik will be Inactive and Removed Externally in QMC.

LD

zsbaksa
Contributor II
Contributor II

Thank You. Assigning RootAdmin role to the qlik service user solved the issue for me.