Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
ChristopheDupont_BME
Contributor
Contributor

OPERATION MONITOR does't work

Hello,
"OPERATION MONITOR never worked on my 2 QLIK servers (November 2021)
But I didn't need it.
Now that I need it, I can't resolve the error messages.
I have tried many solutions found on the forums without success (reload the application, add rights on the connectors, etc ...) but I always come across a new problem.

The current problem is visible in the LOG of the reload task:


20220420T183934.911+0200 2231 CALL QRS // Call QRS data AFTER LogContent table is stored
20220420T183934.911+0200 1234 TRACE Fetching data from Qlik Sense Repository (QRS) database
20220420T183934.911+0200 1234 Fetching data from Qlik Sense Repository (QRS) database
20220420T183934.911+0200 1235
20220420T183934.911+0200 1237 LET NumRowsQRS = 0
20220420T183934.912+0200 1238 SET QRS_RowCounts = 'QRS Row Counts: '
20220420T183934.912+0200 1240 For each endpoint in 'monitor_apps_REST_user','monitor_apps_REST_app','monitor_apps_REST_appobject','monitor_apps_REST_task'
20220420T183934.912+0200 1241 CALL monitor_apps_REST_user
20220420T183934.912+0200 1262 LIB CONNECT TO 'monitor_apps_REST_user_condensed'
20220420T183935.492+0200 Connected.
20220420T183935.496+0200 1264 User:
20220420T183935.496+0200 1265 Load
20220420T183935.496+0200 1266 userDirectory & '\' & userId AS UserId,
20220420T183935.496+0200 1267 [name] AS [User Name],
20220420T183935.496+0200 1268 userDirectory as [User Directory]
20220420T183935.497+0200 1270 SQL SELECT
20220420T183935.497+0200 1271 "userId",
20220420T183935.497+0200 1272 "userDirectory",
20220420T183935.497+0200 1273 "name"
20220420T183935.497+0200 1274 FROM JSON (wrap on) "root"
20220420T183936.133+0200 3 fields found: UserId, User Name, User Directory,
20220420T183936.146+0200 Error: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
20220420T183936.162+0200 Execution Failed
20220420T183936.183+0200 Execution finished.

Thanks for your help ...

Labels (1)
2 Solutions
2 Replies