Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 400 (Bad Request):
Article Number: 000043836 | Last Modified: 2019/08/29
The reload tasks fail with the specific error:
Error: Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 400 (Bad Request):
- There are a few causes, but the most noticeable are:
- The User ID and/or Password being used within the Data Connections are incorrect. For example, if a monitoring app is being reloaded and the task fails with "HTTP protocol error 400 (Bad Request):" then in order to fix, each "monitor_app_" data connection must have the User ID (domain\user) and Password updated. The most common cause is that the User ID is typed incorrectly or does not exist.
- 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)