Both May 2021 and August 2021 Failed Installations
Failed Qlik Sense Enterprise on Windows August 2021 and May 2021 - Installing AWS AMI: QSE_August/May_2021_BYOL
Concerns failures on both August and May 2021 AMI's
August 2021 Update 2:
QSE_August_2021_BYOL_Upd2_1634038484-590d28f7-5d64-4a03-ad0d-32e54e210929 (ami-0e578d0294bddd205)
Qlik Sense Enterprise on Windows May 2021
Installed QWS AMI: QSE_May_2021_BYOL_1627384765
Windows 2019 server, single server node
Issue: 2021-08-31 16:24:44.829 UTC [924] FATAL: password authentication failed for user "qliksenserepository" 2021-08-31 16:24:44.829 UTC [924] DETAIL: Password does not match for user "qliksenserepository". Connection matched pg_hba.conf line 84: "host all all 127.0.0.1/32 md5"
After a brand new install for this issue the event log was filled with the usual postgres error above.
For a full explanation see the following link:
https://community.qlik.com/t5/Deployment-Management/Failed-Qlik-Sense-Enterprise-on-Windows-August-2021-and-May-2021/td-p/1832629
Note after spending hours trying to recover from these errors on the May 2021 AMI we decided to try the August 2021 BYOL as suggested. The same issue happened again. The suggested corrections (by running various install scripts) do not work.
Thousands of the errors below are logged daily.
The description for Event ID 0 from source PostgreSQL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
2021-11-05 12:02:30.974 UTC [12588] FATAL: password authentication failed for user "qliksenserepository"
2021-11-05 12:02:30.974 UTC [12588] DETAIL: Password does not match for user "qliksenserepository".
Connection matched pg_hba.conf line 84: "host all all 127.0.0.1/32 md5"
The errors only appear when the service dispatcher is running.
It's been 2 months since I logged the issue and no response.
Qlik needs to fix this installation problem ASAP.
Note subsequent to the review I was contacted in the ongoing thread I referenced about a potential correction. I applied the correction to all the ps1's and it finally worked. The problem is I was left lingering for 2.5 months before issue was resolved. The CPU was running high the whole time for both servers and of course the thousands of daily event errors. Not to mention that it wasn't only a few configurations, it was all of them. Qlik needs to endeavor to take these issues more seriously from the outset. I appreciate the fix, albeit far too late.