Qlik Sense - Upgrade failed - System.ArgumentException: Item has already been added. Key in dictionary: 'PGPASSFILE' Key being added: 'PGPASSFILE'
Article Number: 000070604 | Last Modified: 2019/04/04
Description
Qlik Sense upgrade fails on the Qlik Sense Repository Database. Looking at the installation logs under C:\Users\<Username>\AppData\Local\Temp\Qlik_Sense_PostgreSQL.log we can see the following:
Action 23:58:58 26 System.ArgumentException: Item has already been added. Key in dictionary: 'PGPASSFILE' Key being added: 'PGPASSFILE' at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add) at Qlik.Burn.Common.Validators.DatabasePasswordValidator.ValidateSuperUserPassword(String port, String superUser, String superPass, String postgresDir) at Qlik.QustomActions64.DatabaseInitializer.ValidationSuperUserPasswordRetry(IMsiHelper msiHelper, String postgresDir, String port, String superUser, String superPass, DatabasePasswordValidator databasePasswordValidator) at Qlik.QustomActions64.DatabaseInitializer.ValidateSuperUserPassword(Session session) CustomAction CA_ValidateLimitedUserPassword returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (84:7C) [23:58:58:292]: Note: 1: 2265 2: 3: -2147287035 MSI (s) (84:7C) [23:58:58:292]: User policy value 'DisableRollback' is 0 MSI (s) (84:7C) [23:58:58:292]: Machine policy value 'DisableRollback' is 0 Action ended 23:58:58: InstallFinalize. Return value 3.
Environment: Qlik Sense September 2017 (Probably earlier and later version too)
Cause
Check if you have created any windows environment variable call PGPASSFILE. You can find the list of environment variables in Control Panel -> System -> Change Settings -> Advanced -> Environment Variables
Resolution
If there is a Windows environment variable called PGPASSFILE then you will need to remove it.
Get Answers
Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.