Qlik Community

Qlik Sense Deployment & Management

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

Highlighted
Partner
Partner

Trouble with monitoring apps reload after upgrading to QlikSense April 2018

Since upgrading to April 2018 in a coupe of environments, I have been having trouble with reloading the monitoring apps. The connection to the ArchivedLogsFolder hasn't changed. After duplicating to my work stream & reloading I get the follwing errors:

Does this have anything to do with the move from logging folders to a logging database in this release? is anyone else having this problem?

1 Solution

Accepted Solutions
Employee
Employee

Re: Trouble with monitoring apps reload after upgrading to QlikSense April 2018

Hey Zachary,

  1. Can you attach a script log from a reload in the QMC?
  2. For the current issue, you do not have the necessary rights to see those data connections. To resolve this:
    • Create a new Security Rule:
    • DataConnection_*
    • Read / Update
    • user.userid = "YourUserId"
    • Hub
4 Replies
Employee
Employee

Re: Trouble with monitoring apps reload after upgrading to QlikSense April 2018

Hey Zachary,

  1. Can you attach a script log from a reload in the QMC?
  2. For the current issue, you do not have the necessary rights to see those data connections. To resolve this:
    • Create a new Security Rule:
    • DataConnection_*
    • Read / Update
    • user.userid = "YourUserId"
    • Hub
Partner
Partner

Re: Trouble with monitoring apps reload after upgrading to QlikSense April 2018

I tried updating the security rule but am still getting the same errors on reload of the data.

Employee
Employee

Re: Trouble with monitoring apps reload after upgrading to QlikSense April 2018

At this point, the trace is as follows:

  • Error: QVX_UNEXPECTED_END_OF_DATA: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

This suggests that the prefix-less virtual proxy is configured to use Forms authentication rather than the default Windows value.

From our KB:

  • Operations Monitor and License Monitor apps use the Qlik REST Connector to fetch data. The connector requires Windows Authentication to be successful in fetching data. This issue occurs when no virtual proxy in the Qlik Sense deployment utilizes Windows authentication.


  • The issue can be resolved by enabling Windows Authentication for example by adding a secondary virtual proxy using Windows authentication.
  • Create a secondary virtual proxy and use standard windows authentication. In this example "win" is used as prefix, but this prefix can be any text value.
  • Attach it to an Engine, as you normally would for a Virtual Proxy
  • Ensure that the newly created Virtual Proxy is attached to a Proxy, so that there is a proxy listening for requests that come to https://example.company.com/win/:
  • For Qlik Sense 3.2.5 and older, edit all Data Connections prefixed with qrs_ to use the new virtual proxy. Change the connector URL path to contain the Windows authenticated virtual proxy.
  • For Qlik Sense June 2017 and newer, edit all Data Connections prefixed with monitor_apps_ to use the new virtual proxy. Change the connector URL path to contain the Windows authenticated virtual proxy.

j562JkK.png

  • Note, in Qlik Sense June 2017 and higher the virtual proxy is embedded in two locations:
    • CUSTOM CONNECT TO "provider=QvRestConnector.exe;url=https://localhost/qrs/app/full;timeout=900;method=GET;autoDetectResponseType=true;keyGenerationStrategy=0;authSchema=ntlm;skipServerCertificateValidation=true;useCertificate=No;certificateStoreLocation=LocalMachine;certificateStoreName=My;trustedLocations=qrs-proxy%2https://localhost:4244;queryParameters=xrfkey%20000000000000000;addMissingQueryParametersToFinalRequest=false;queryHeaders=X-Qlik-XrfKey%20000000000000000%1User-Agent%2Windows;PaginationType=None;allowResponseHeaders=false;allowHttpsOnly=false;"
Partner
Partner

Re: Trouble with monitoring apps reload after upgrading to QlikSense April 2018

This worked! Thank you!