After successfully installing Qlik Sense September 2017, November 2017 or February 2018 with centralized logging, the Qlik Logging service does not start.
When attempting to start it you receive "Error 1064: An exception occurred in the service when handling the control request"
If you open Windows Event logs, you see the error message:
FATAL: password authentication failed for user "qlogs_writer" DETAIL: Role "qlogs_writer" does not exist. Connection matched pg_hba.conf line 82: "host all all ::1/128 md5"Environment:
Qlik Sense September 2017
Qlik Sense November 2017
Qlik Sense February 2018
This is caused by special characters in either the superuser password, or the qlogs_writer/reader account passwords. Currently we are aware that ^ can cause this issue, but it is possible other characters may trigger it.
If the problematic password is either the qlogs_reader or qlogs_writer password, try a new one without ^ or other special characters.
The password can be changed using the same process as the original configuration of the Qlik Logging Service. See the online help
for assistance or How to set up the Qlik Sense Logging Service
Note that the update command lets you change the passwords the service will try to use, while the the setup command with -f will let you change the passwords themselves, though will also wipe the qlogs db in the process.
If it is the superuser password, review the procedure for changing the database superuser password here