Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi ,
OPS monitor and license monitor is failing with below error after June release upgrade:
2017-08-23 14:01:59 0613 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'
2017-08-23 14:01:59 0614 CALL monitor_apps_REST_license_user
2017-08-23 14:01:59 0634 LIB CONNECT TO ***
2017-08-23 14:01:59 0636 RestConectorMasterTable:
2017-08-23 14:01:59 0637 SQL SELECT
2017-08-23 14:01:59 0638 "id" AS "id_u0",
2017-08-23 14:01:59 0639 "createdDate",
2017-08-23 14:01:59 0640 "modifiedDate",
2017-08-23 14:01:59 0641 "modifiedByUserName",
2017-08-23 14:01:59 0642 "lastUsed",
2017-08-23 14:01:59 0643 "quarantined",
2017-08-23 14:01:59 0644 "quarantineEnd",
2017-08-23 14:01:59 0645 "__KEY_root",
2017-08-23 14:01:59 0646 (SELECT
2017-08-23 14:01:59 0647 "id",
2017-08-23 14:01:59 0648 "userId",
2017-08-23 14:01:59 0649 "userDirectory",
2017-08-23 14:01:59 0650 "name",
2017-08-23 14:01:59 0651 "__FK_user"
2017-08-23 14:01:59 0652 FROM "user" FK "__FK_user")
2017-08-23 14:01:59 0653 FROM JSON (wrap on) "root" PK "__KEY_root"
2017-08-23 14:02:00 14 fields found: id, userId, userDirectory, name, __FK_user, id_u0, createdDate, modifiedDate, modifiedByUserName, lastUsed, quarantined, quarantineEnd, __KEY_root, __extra_,
2017-08-23 14:02:00 Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 401 (Could not authenticate the request: Expected an authentication header.):
2017-08-23 14:02:00
2017-08-23 14:02:00 Requested resource requires authentication.
2017-08-23 14:02:00 Execution Failed
2017-08-23 14:02:00 Execution finished.
Hi Amit,
Have you managed to resolve this issue?
Kind Regards
Muhammad
Try this article of the knowledge base
Regards
Yes the issue got resolved by maintaining the connection string under data connection in QMC.
Sometimes its maintained as local host just try to change it with central node
in my case the issue resolved by re-entering the credentials in all monitoring apps and then making sure the app name is correct.
Cheers!!