Operation and License Monitor App Fail after Qlik Sense version has been upgraded to June 2017 or newer.Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 401 (Unauthorized):
2017-10-05 16:39:00 Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 401 (Unauthorized):
2017-10-05 16:39:00 Requested resource requires authentication.
2017-10-05 16:39:00 Execution Failed
2017-10-05 16:39:00 Execution finished.
OR Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 404 Not Found:
2018-06-25 16:58:36 Error: QVX_UNEXPECTED_END_OF_DATA: The remote server returned an error: (404) Not Found.
2018-06-25 16:58:36 Execution Failed
2018-06-25 16:58:36 Execution finished.
Make sure that monitor_apps_REST_*
has the requested authentication to run Monitor apps
================= FIX 1 ========================
1. Go to QMC >> Data connections
2. Search all monitor_apps_REST_*
3. Edit all monitor_apps_REST_*
4. Put the correct User ID and Password in the field under "Edit data connection"
If Qlik Sense service is running as a local administrator, you need to put the account of Local administrator within the field. (e.g. Domain\administrator)
- Open cmd.exe
- Type "whoami
- Check the account or user id
- Go to services.msc and check Qlik Sense service account
===================== FIX 2 =======================
404 NOT FOUND
Do the previous steps plus ...
It is possible that in a multinode environment the REST connection strings would need the 'localhost' setting of the connection string changed to the FQDN of the central node. In the connection string there are two places where localhost is contained.
Create a Virtual Proxy called win with a win prefix.
Add /win/ between the FQDN and 'qrs' of the first FQDN entry (but not after the second FQDN entry)
The prefix has to be added to the connection string right after the FQDN. such as "localhost/win/grs" to point to the new virtual proxy.
===================== FIX 3 =======================
If the issue does not go away. Test the connection with another root admin account and ensure the password on that account is 'simple' free of special characters.
It is possible that the account used (should be the service account) may be corrupted or have too complex a password.