Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I installed February 2018 on a new Windows 2012 R2 server in a single node environment. I have not been able to refresh the included monitoring apps (license and operations). When I look at the logs, both end with:
2018-04-18 07:04:30 0625 LET NumRowsQRS = 0
2018-04-18 07:04:30 0626 SET QRS_RowCounts = 'QRS Row Counts: '
2018-04-18 07:04:30 0628 For each endpoint in 'monitor_apps_REST_license_user','monitor_apps_REST_license_login','monitor_apps_REST_user','monitor_apps_REST_license_access','monitor_apps_REST_app'
2018-04-18 07:04:30 0629 CALL monitor_apps_REST_license_user
2018-04-18 07:04:30 0649 LIB CONNECT TO 'monitor_apps_REST_license_user'
2018-04-18 07:05:00 Error: Connection aborted (System error: ***)
2018-04-18 07:05:00 Execution Failed
2018-04-18 07:05:00 Execution finished.
I have run a number of times. Every time there is exactly 30 seconds between LIB CONNECT and the error. I tried updating the default monitor_apps_REST_license_user connection string by changing localhost to the FQDN, but that didn't work. I tried increasing the timeout from 900 (not a multiple of 30, but worth a shot) to 9000, but that had no impact. The connection string is set to use the service account (default setting) which is a member of the administrator group on the server.
Any suggestions?
Hi,
Try to Create Separate Virtual Proxy and link it to the Monitoring Dashboard, it should work.
Regards,
Poppy
Thank you for responding. Can you explain how to link a specific application/task/data connection/stream to a virtual proxy? I created a new virtual proxy, but I'm not clear on how to direct an application (the monitoring apps. in particular) to reload against the new virtual proxy. In QMC none of the options for application/task/data connection/stream allow it to be linked to a given virtual proxy.
Hi,
Please follow the steps below.
1. Create Virtual Proxy as Monitoring, Prefix as monitoring and session cookie header name as X-Qlik-Session-monitoring
2. link virtual Proxy to Proxy/
3. Replace Localhost to FDQN/monitoring in all the Data Connections which Begins with "monitor".
4. Reload the Monitoring Apps.
Regards,
Poppy