Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Unexpected character encountered while parsing value: <. Path '', line 0, position 0"

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Unexpected character encountered while parsing value: <. Path '', line 0, position 0"

Last Update:

Sep 25, 2023 9:28:07 AM

Updated By:

Sonja_Bauernfeind

Created date:

Aug 31, 2016 2:06:48 AM

Operation Monitor and License Monitor apps in Qlik Sense failed to reload with error message;

"Error: QVX_UNEXPECTED_END_OF_DATA: Unexpected character encountered while parsing value: <. Path '', line 0, position 0."

Step 1: Verify the connection string

Check the connection string of the data connections for your monitor_apps_*.
The connection string should be: queryHeaders=X-Qlik-XrfKey%20000000000000000%1User-Agent%2Windows;PaginationType=None; 
If the string is instead: queryHeaders=X-Qlik-XrfKey%20000000000000000%1User-Agent%2Forms;PaginationType=None;  then modify it to User-Agent%2Windows.

 

Step 2: Create a second Virtual Proxy allowing Windows authentication. 

Create a secondary virtual proxy using standard windows authentication. In our example we use "win" as the prefix. For detailed instructions on how to add a new Virtual Proxy, see Qlik Sense: How to create a new Virtual Proxy
 


User-added image

 

 

Step 3: Modify the Data Connection prefixes

Edit all Data Connections prefixed with monitor_apps_ to use the new virtual proxy. Change the connector URL path to contain the Windows authenticated virtual proxy.

User-added image




Cause:

Operations Monitor and License Monitor apps use the Qlik REST Connector to fetch data. The connector requires Windows Authentication to be successful in fetching data. This issue occurs when no virtual proxy in the Qlik Sense deployment utilizes Windows authentication. 

Labels (2)
Comments
mikegrattan
Creator III
Creator III

I'm on Qlik Sense Enterprise for Windows, version May 2023 Patch 3.  I'm getting a similar error when attempting to load the License Monitor, but the connection string does not contain User-Agent%2Windows or anything similar.  I have added the virtual proxy but that does not fix the problem.  Any suggestions?

 

20230919T140838.694-0700 0529 LIB CONNECT TO 'monitor_apps_REST_license_user'
20230919T140839.444-0700 Connected.
20230919T140839.446-0700 0530 trace connect to monitor_apps_REST_license_user
20230919T140839.446-0700 0530 connect to monitor_apps_REST_license_user
20230919T140839.446-0700 0531
20230919T140839.446-0700 0532 user_map:
20230919T140839.446-0700 0533 Mapping LOAD
20230919T140839.446-0700 0534 [__FK_user]&'user' as key,
20230919T140839.446-0700 0535 LOWER(userDirectory & '\' & userId) as UserId
20230919T140839.446-0700 0537 SQL SELECT
20230919T140839.446-0700 0538 (SELECT
20230919T140839.446-0700 0539 "id",
20230919T140839.446-0700 0540 "userId",
20230919T140839.446-0700 0541 "userDirectory",
20230919T140839.446-0700 0542 "__FK_user"
20230919T140839.446-0700 0543 FROM "user" FK "__FK_user")
20230919T140839.446-0700 0544 FROM JSON (wrap on) "root" PK "__KEY_root"
20230919T140839.982-0700 2 fields found: key, UserId,
20230919T140840.009-0700
20230919T140840.009-0700 Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
20230919T140840.009-0700 Error: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
20230919T140840.009-0700 Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
20230919T140840.018-0700 Execution Failed
20230919T140840.056-0700 Execution finished.

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @mikegrattan 

Operations Monitor and License Monitor apps use the Qlik REST Connector to fetch data. The connector requires Windows Authentication to be successful in fetching data. This article specifically documents a solution in case you do not have Windows authentication enabled. Can you confirm if you use Windows Authentication by default and/or that the virtual proxy you created to and which you switched the connection string to is using Windows authentication?

I have also located a user who reported that this article has resolved the issue for them.

All the best,
Sonja 

mikegrattan
Creator III
Creator III

Hi Sonja,

Yes, I have already created the Windows authentication virtual proxy and updated the connection strings for all monitor_apps_REST* connections as described above, as well as updating the connection strings to use FQDN for the URL and trusted connection sections.  But I'm still getting the same error regarding the unexpected character string.  I have also created a ticket with support in regards to the issue, but I thought I'd post here in case you had any information regarding the connection string when it doesn't contain User-Agent%2Windows?  I'm curious if I've got something wrong with my connection strings if they don't contain that section and therefore can't be updated as described in your solution?

Qlik_FZ
Partner - Creator
Partner - Creator

Hi Sonja,

I have made the changes you suggested above and now I am able to reload operation monitor from hub but

I am still getting same issue while reloading "qs-data-connection-analyzer-v1.5.2" app.

I configured qs-data-connection-analyzer-v1.5.2 app as per the given instruction.

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @Qlik_FZ 

This is not one of the Qlik-supported monitoring apps, from what I understand. Is this the one you are referring to? Qlik Sense Data Connection Analyzer 

It is flagged as unsupported by the authors on github, but you can use the issues section to report problems. Alternatively, the Qlik Sense Deployment & Management board may be a good choice to get answers from. Place a new post there, describing the issues you are seeing and the errors the app throws.

All the best,
Sonja 

Qlik_FZ
Partner - Creator
Partner - Creator

Hi Sonja,

 

Yes this is the same app.

Contributors
Version history
Last update:
‎2023-09-25 09:28 AM
Updated by: