topic License Monitor - reload error (parsing json) in Management & Governance

License Monitor - reload error (parsing json)

feliciano_alan — Fri, 15 Nov 2024 22:28:39 GMT

The apps License Monitor and Operations monitor aren't reloading.

Both apps stop the reload in the same point.

20221003T142521.989-0300 0697 LIB CONNECT TO 'monitor_apps_REST_license_user' 20221003T142523.004-0300 Connected. 20221003T142523.007-0300 0698 trace connect to monitor_apps_REST_license_user 20221003T142523.007-0300 0698 connect to monitor_apps_REST_license_user 20221003T142523.008-0300 0699 20221003T142523.009-0300 0700 user_map: 20221003T142523.010-0300 0701 Mapping LOAD 20221003T142523.010-0300 0702 [__FK_user]&'user' as key, 20221003T142523.010-0300 0703 LOWER(userDirectory & '\' & userId) as UserId 20221003T142523.012-0300 0705 SQL SELECT 20221003T142523.012-0300 0706 (SELECT 20221003T142523.012-0300 0707 "id", 20221003T142523.012-0300 0708 "userId", 20221003T142523.012-0300 0709 "userDirectory", 20221003T142523.012-0300 0710 "__FK_user" 20221003T142523.012-0300 0711 FROM "user" FK "__FK_user") 20221003T142523.012-0300 0712 FROM JSON (wrap on) "root" PK "__KEY_root" 20221003T142523.720-0300 2 fields found: key, UserId, 20221003T142523.760-0300 20221003T142523.761-0300 Unexpected character encountered while parsing value: <. Path '', line 1, position 1. 20221003T142523.761-0300 Error: Unexpected character encountered while parsing value: <. Path '', line 1, position 1. 20221003T142523.761-0300 Unexpected character encountered while parsing value: <. Path '', line 1, position 1. 20221003T142523.767-0300 Execution Failed 20221003T142523.803-0300 Execution finished.

It looks to be an error when the REST API (monitor_apps_REST_license_user) are creating the json file for response.

This is in the production server, because in the test server there isn't reload error in these apps.
Probably, because the general users don't access and use license there.

The last reload of License Monitor was sep 13,2022 and after some ours, they were added more users by user directory.

I don't know if these users affected something or if was another thing.

This error looks to be in the Rest Api, better, in the data processed by the REST API (monitor_apps_REST_license_user).

I don't any ideia what to explore in the Qlik Postgres database.

The server is Qlik core licensed.

So, someone had experienced something like this? What can I do?

Re: License Monitor - reload error (parsing json)

SachinB — Tue, 11 Oct 2022 02:33:29 GMT

Hello @feliciano_alan ,

I think you have selected the wrong product (Qlik Enterprise Manager), It should belong to Qlik Sense Enterprise. Correct me if I am wrong.

However, I have found the below community link for you. Hope this helps you.

https://community.qlik.com/t5/Official-Support-Articles/Unexpected-character-encountered-while-parsing-value-lt-Path/ta-p/1714588

Note : Please confirm on product, I will route this to proper team in order to get faster resolution.

Regards,

Sachin B

Re: License Monitor - reload error (parsing json)

feliciano_alan — Tue, 11 Oct 2022 12:49:34 GMT

Hi @SachinB,

you're right about the product, it's Qlik Sense Enterprise.

About the topic you share, I found it and all of the steps were ok in this server, but was what I though. haha.

Checking it again for post here the results in the server, I see the step 3 wasn't satisfied it my early analyze.

I change just change the connection string of monitor_apps_REST_license_user adding the correct virtual proxy prefix and it works.

thank you so much.

God bless you.

Re: License Monitor - reload error (parsing json)

achentouf — Fri, 10 Nov 2023 15:58:10 GMT

Hello,

I have exactly the same issue. I've checked the connection, and it seems to be fine. I tried the method of adding a new virtual proxy main without any result, even though it was working well a few months ago.

Do you have a solution, please?

Thank you.

Best regards,
Anass

Re: License Monitor - reload error (parsing json)

Steve_Nguyen — Mon, 13 Nov 2023 17:34:10 GMT

@achentouf best to open a support case so that one of the support team can isolate the issue .