Qlik Community

Knowledge

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
QlikWorld 2022, LIVE in Denver CO., May 16-19, 2022. REGISTER NOW TO RECEIVE EARLY BIRD PRICING

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

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"

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


Environment:

 

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 ConnectionStringEditor.exe (in Qlik Sense Enterprise 3.x) or 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 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 password does not match.
  9. Save the file
  10. Restart all services

 

Labels (1)
Attachments
Version history
Last update:
‎2021-05-07 05:35 AM
Updated by:
Contributors