I recently upgraded to April 2018 SR1 from June 2017 SR1. Now the reload of operations monitor is failing. The users are experiencing serious performance degradations also. Please help to fix this.
The first step is to open up the QMC and go to the "Data Connections" section of the QMC, and open one of the "monitor_apps" data connections
Inspect the connection string and other settings, as follows:
First, is the FQDN of the central server being used or is is "localhost"? It must be the FQDN. It's important to note that this is listed twice in the connection string (once at the beginning and once near the end) so be sure to edit both
Next, verify that this exists in the connection string ";skipServerCertificateValidation=true;" as seen in the example below
Third, if you use a prefix in the QMC's Virtual Proxy section (of the Central Proxy), then this prefix text must be added after the FQDN but before the line "/qrs". Below is an example. If your Virtual Proxy has the "Prefix" section filled out, and that text is "myprefix", then that must be added as indicated in the example below
Fourth, ensure that the User ID and Password is correct. The User ID needs to be the account running the qlik services. For example, open Windows Services and view the account running the Qlik services. If the user account is "mydomain\qlikservice" then you would enter in domain\qlikservice for the User ID and then type in the password for this account and then click Apply. The User ID cannot be ".\admin", which was a bug in a previous version after an upgrade.
Finally, ensure that the "Owner" is "sa_repository"
These changes must be made to every single Data Connection that begins with "monitor_apps". There should be 8 "monitor_apps" data connections that need updating
An example "connection string" would look like this:
CUSTOM CONNECT TO "provider=QvRestConnector.exe;url=https://qlikserver1.domain.local/myprefix/qrs/license/loginaccesstype/full;timeout=999;method=GET;autoDetectResponseType=true;keyGenerationStrategy=0;authSchema=ntlm;skipServerCertificateValidation=true;useCertificate=No;certificateStoreLocation=CurrentUser;certificateStoreName=My;trustedLocations=qrs_proxy%2https://qlikserver1.domain.local:4244;queryParameters=xrfkey%20000000000000000;addMissingQueryParametersToFinalRequest=false;queryHeaders=X-Qlik-XrfKey%20000000000000000%1User-Agent%2Windows;PaginationType=None;"
assuming my FQDN is "qlikserver1.domain.local", a Virtual Proxy prefix is being used and it's called "myprefix"
