Skip to main content

Repository System Log Shows Error "Not possible to decrypt encrypted string in database"

No ratings
Showing results for 
Search instead for 
Did you mean: 
Digital Support
Digital Support

Repository System Log Shows Error "Not possible to decrypt encrypted string in database"

Last Update:

Dec 28, 2020 3:06:05 PM

Updated By:


Created date:

Jan 27, 2015 7:55:30 AM

Qlik Sense cannot be accessed and used as expected. Qlik Sense Repository System logs shows error: 

Not possible to decrypt encrypted string in database; this is probably due to the secrets key on server certificate has been changed and the old database value hasn't; sending back empty result and leaving the value unchanged in database 

The script logs for reloading monitoring apps may show similar lines as the ones below:


20201228T174644.330+0100 Error: HTTP protocol error 401 (Unauthorized):
20201228T174644.330+0100 Requested resource requires authentication.
20201228T174644.331+0100 Execution Failed
20201228T174644.339+0100 Execution finished.



  • Qlik Sense Enterprise for Windows, all versions



Passwords and other connection values are stored encrypted in the database in a hash created based on currently used self-signed certificates. When the system reads the hash it uses the content of self-signed certificates currently installed to decrypt the passwords.



There are two possible resolutions:

  1. Revert to the backup of your server and root certificates. Qlik Sense does not run an automated backup of its certificates. This option requires that the certificates were backed up by the system admin or 3rd party automation tools.
  1. Go to the Qlik Management Console (QMC)  > Data Connections & User Directory Connectors > 
    (a) Open each Data Connection / User Directory Connector
    (b) Enter a null password for each data connection, i.e. ; (semi-colon) which will be interpreted as an escape character
    (c) If the connection does have a password, then do step (b) followed by re-entering the password
    This causes the system to write new encrypted strings to the database using the current certificate.
Version history
Last update:
‎2020-12-28 03:06 PM
Updated by: