Skip to main content

Official Support Articles

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
CUSTOMERS ONLY: Now accepting customer applications for the 2023 Luminary Program: SUBMIT NOW

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

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"

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."

Environment:

  • Qlik Sense Enterprise all versions

 

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 intsead: 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)
Version history
Last update:
‎2021-02-10 06:58 AM
Updated by:
Contributors