topic Can't relaod Operations Monitor in App Development

Can't relaod Operations Monitor

reshma_km — Wed, 04 Jul 2018 14:19:03 GMT

Hi,

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.

Re: Can't relaod Operations Monitor

Gysbert_Wassenaar — Wed, 04 Jul 2018 14:26:19 GMT

Do you have a log file of the execution of the script of the Operations Monitor?

If you have scheduled a task in the QMC for it you should be able to find the log by clicking on the info icon in the status column of the Tasks view.

If you don't you should be able to find the log in the %ProgramData%\Qlik\Sense\Log\Script

Re: Can't relaod Operations Monitor

reshma_km — Wed, 04 Jul 2018 15:52:38 GMT

Hi,

At the end of the log file, I see the below message:

2018-07-04 15:49:58 1218 For each endpoint in 'monitor_apps_REST_user','monitor_apps_REST_app','monitor_apps_REST_appobject','monitor_apps_REST_task'

2018-07-04 15:49:58 1219 CALL monitor_apps_REST_user

2018-07-04 15:49:58 1240 LIB CONNECT TO 'monitor_apps_REST_user'

2018-07-04 15:50:28 Error: Connection aborted (System error: ***)

2018-07-04 15:50:29 Execution Failed

2018-07-04 15:50:29 Execution finished.

Re: Can't relaod Operations Monitor

reshma_km — Wed, 04 Jul 2018 16:06:29 GMT

I provided the service account with root admin access. still, reload is failing.

error:

2018-07-04 16:02:32 1218 For each endpoint in 'monitor_apps_REST_user','monitor_apps_REST_app','monitor_apps_REST_appobject','monitor_apps_REST_task'

2018-07-04 16:02:32 1219 CALL monitor_apps_REST_user

2018-07-04 16:02:32 1240 LIB CONNECT TO 'monitor_apps_REST_user'

2018-07-04 16:03:03 Error: Connection aborted (System error: ***)

2018-07-04 16:03:03 Execution Failed

2018-07-04 16:03:03 Execution finished.

Re: Can't relaod Operations Monitor

BalaBhaskar_Qlik — Wed, 04 Jul 2018 16:21:46 GMT

May be these are the issues:

Check & provide, Qlik Sense service user role as RootAdmin.

Quite often the problem comes from a miss configuration with the Qlik Repository Service (QRS) using the REST connector. If so, try to follow these steps:

1) Login in the qmc with rootAdmin grants

2) Got to the Data Connections TAB (third from the top on the left side panel)

3) Find out and modify these connections (qrs_app, qrs_appobject, qrs_event, qrs_licenseSummary, qrs_loginAccess, qrs_task, qrs_user, qrs_userAccess). For each of those change the owner to your user

4) Login in the hub, go to the Data Load Editor, now you can see the previous Data Connections in all you apps (in your working area) even from a new app

5) For each one click on the pencil icon and flag "Skip server certificate verification" notice, the data connection name change appending your user to the data connection original name

6) Make a Connection TEST, now the connection test should work

7) Come back to qmc, for each data connection rename it (removing the user name appended) and replace the original owner (INTERNAL\sa_repository)

Now the task should works.

Also check the below link.

https://help.qlik.com/en-US/sense/June2018/Subsystems/Monitoring/Content/Troubleshooting/troubleshooting-monitoring.htm

Re: Can't relaod Operations Monitor

reshma_km — Wed, 04 Jul 2018 16:54:12 GMT

I also see the below text in the logs:

LIB CONNECT TO 'QLogs'

2018-07-04 15:56:10 Error: Connection aborted (System error: ***)

2018-07-04 15:56:10 0078 LET tempErrorDetails = ScriptErrorDetails

2018-07-04 15:56:10 0079 IF Len(tempErrorDetails) > 0 THEN

2018-07-04 15:56:10 0080 trace ERROR: Connection aborted

2018-07-04 15:56:10 0080 ERROR: Connection aborted

tempErrorDetails =

2018-07-04 15:56:10 0083 TRACE Could not validate active database logging. Sourcing from file logs instead.

2018-07-04 15:56:10 0083 Could not validate active database logging. Sourcing from file logs instead.

Re: Can't relaod Operations Monitor

reshma_km — Tue, 10 Jul 2018 19:43:59 GMT

Skip server certificate verification is already set to true.

Re: Can't relaod Operations Monitor

reshma_km — Tue, 10 Jul 2018 19:48:21 GMT

gwassenaar‌

Hi,

I duplicated the license monitor and reloaded it from data load editor. I am getting the below errors while reload.

Both data connections exists in QMC.

Re: Can't relaod Operations Monitor

Gysbert_Wassenaar — Wed, 11 Jul 2018 07:10:25 GMT

Can you post a screenshot of the Connections page of the QMC?

Re: Can't relaod Operations Monitor

reshma_km — Wed, 11 Jul 2018 18:37:39 GMT

Hi,

Re: Can't relaod Operations Monitor

satishkurra — Wed, 11 Jul 2018 19:02:25 GMT

Try this.

We even faced similar issue and reached Qlik.

QLik provided us below steps to make this work

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:
1. 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
2. Next, verify that this exists in the connection string ";skipServerCertificateValidation=true;" as seen in the example below
3. 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
4. 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.
5. 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
Finally, refer to this Qlik Help page that shows a few other items that need to be checked for accuracy: http://help.qlik.com/en-US/sense/November2017/Subsystems/Monitoring/Content/Introduction/Configure-monitoring-apps.htm

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"

Re: Can't relaod Operations Monitor

reshma_km — Thu, 12 Jul 2018 20:19:38 GMT

Thanks for your response. I changed localhost. But still, reload fails.

Re: Can't relaod Operations Monitor

NZFei — Tue, 17 Jul 2018 02:14:31 GMT

Untick the box "Kerberos authentication":