Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Repository service does not start after patch removal or repair installation - Fatal exception password authentication failed for user "postgres"

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

Repository service does not start after patch removal or repair installation - Fatal exception password authentication failed for user "postgres"

Last Update:

Jan 30, 2023 2:15:27 AM

Updated By:

Sonja_Bauernfeind

Created date:

Oct 6, 2016 4:26:46 PM

Attachments

The Repository service does not start after patch removal or repair installation.

The Windows Application Event logs record the following:

Log Name: Application
Source: PostgreSQL
EventID:0
Level: Error:
User: N/A
General:
...
FATAL: password authentication failed for the user "postgres"
DETAIL: Password does not match for user "postgres".
           Connection matched pg_hba.conf line 80: "host  all       all      127.0.0.1/32        md5"

The Repository > Trace > System Repository logs the following:

Fatal exception password authentication failed for user "postgres"??The provider did not return a ProviderManifestToken string.??An error occurred accessing the database. This usually means that the connection to the database failed. Check that the connection string is correct and that the appropriate DbContext constructor is being used to specify it or find it in the application's config file

or

ERROR SERVERNAME System.Repository.Repository.Repository.QRSMain 6 <ID> domain\user Fatal exception during startup  Waiting for database timed out after 0 seconds

 

Resolution

The repository configuration file (C:\Program Files\Qlik\Sense\Repository\Repository.exe.config) has been modified and is no longer passing the correct credentials.

  1. Stop all services
  2. Backup the Repository.exe.config file (default: C:\Program Files\Qlik\Sense\Repository\Repository.exe.config but is where ever they install Qlik Sense)
  3. Open the "Connection String Editor" in QlikSenseUtil.exe
  4. If not already, direct it to the Repository.exe.config file (default: C:\Program Files\Qlik\Sense\Repository\Repository.exe.config but is where ever they install Qlik Sense)
  5. Use the "Connection String Editor" in QlikSenseUtil.exe to decrypt the Connection String (Click on "Read")
  6. Check and see that the password and user ID is correct. If not correct to look as the following:
    <connectionStrings>
        <add name="QSR" connectionString="User ID=postgres;Host=localhost;Port=4432;Database=QSR;Pooling=true;Min Pool Size=0;Max Pool Size=90;Connection Lifetime=3600;Unicode=true;Password='ENTERYOURSUPERUSERPASSWORDHERE';" providerName="Devart.Data.PostgreSql" />
    </connectionStrings>​
  7. Make the same correction to other strings if present (newer versions), except for the one connecting to the database called "postgres"
  8. It is possible that steps in The QSR, SenseServices, QSMQ, and Licenses login role need to be revisited if the password does not match.
  9. Save the file
  10. Restart all services

 

Environment:

Qlik Sense Enterprise on Windows 

 

Labels (1)
Contributors
Version history
Last update:
‎2023-01-30 02:15 AM
Updated by: