This is working as designed. The Qlik Sense Logging service is stopping due to it trying to communicate to a database and failing as the database was configured to accept only encrypted traffic. The centralize logging connection string is missing the "Ssl Mode=Require". Traffic then is unencrypted and as result it is rejected by the database and the service reaction is to fail to start with the 1064 error.
Currently there is no way to modify the connection string from the centralize logging, other than keeping it in cleartext. A Feature Request has been registered.
Feature Request ID(s):
2511 - Enable SSL/TLS on Qlik Logging Service
! Qlik has previously received feedback on this feature and recorded the request for future review. For up to date information and to express you would like the Feature implemented please contact support at support.qlik.com referencing this article.
NOTE! The workaround consists of adding encryption to the database connection by making the centralize logging connection string appear in cleartext.
Go to %Program Files%\Qlik\Sense\Repository\Util\QlikSenseUtil.
Open QlikSenseUtil.exe as Admin (right-lick > run as administrator)
In QlikSenseUtil.exe > select "Connection String Editor".