Operation and License Monitor App Fail after Qlik Sense has been upgraded.
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.
Service Account permissions or availability:
If the service account is being listed as removed externally and inactive (on the Users tab), then error 400 or 403 will occur. The service user must have "No" listed for inactive/blocked/removed.
The reason why the service account is marked as removed externally and inactive is because it is not found when doing a sync to the UDC in use. The most common reason for this is that there is an LDAP filter in place which filters on a group where the service account is not a member of. Temporary Resolution: You can remove the LDAP filter and Sync the UDC in order to make the Qlik account in the QMC active again. To resolve this, tell the client's IT Dept to add the service account to the filtered group and resync the UDC (the change may take a few minutes to register so you may need to sync a few times).
monitor_apps_REST_* connections are not configured with the correct user
Make sure that monitor_apps_REST_* has the requested authentication to run Monitor apps.
Resolution
Follow the steps in Qlik Sense on premise Monitoring Apps fail with error 401 Unauthorized. Then proceed with:
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.
If the issue persists, 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.
