This issue usually occurs on upgrading to 10500 or post 10500 migrations. This occurs due to mismatch in the DB password and inbuilt hard coded password for the user postgres.
To tackle this issue we need to find certain prerequisites in the CX end.
NOTE: Make sure Stonebraker does not work as the password for user postgres when the DB is connected with mode as MD5 in pg_hba.conf.
If it does not work, then change it to TRUST mode and then go ahead with following steps.
FOR A POSTGRES USER.
Check for a table named " DBCredentialsAudit " in the CX end using the query.
SELECT * FROM TableDetails where TABLE_NAME like '%DBCredentialsAudit%';
Case 1 : The Table is not present(USUALLY SHOWN AS 0 ROWS FOR PREVIOUS QUERY).
In this case its easy to solve we just need to connect to DB in console mode and execute the following query.
ALTER USER postgres WITH PASSWORD 'Stonebraker';
Once this query is executed close the DB connection and upgrade.
Case 2 : The Table is present .
In this case we need to check if the table has a user named postgres as its value by executing the following query.
SELECT * FROM DBCredentialsAudit;
If the value is present navigate yourself to servicedesk\conf directory and check the encryption algorithm in the product-config.xml file.
The value will be specified as below, inside the xml file
<property name="encryption.algo" value="aes256"/>
Use this value to substitute in the following query
UPDATE DBCredentialsAudit set password=pgp_sym_encrypt('Stonebraker','SChar@123Mas!er','s2k-mode=1, cipher-algo=<ALGO>') where username='postgres';
**Replace the <ALGO> with the algorithm value present in the product-config.xml file. Once executed upgrade the application.
FOR A MSSQL USER.
Change the DB to Postgres and run the application and follow the steps told above. Once completed change the DB back to CX's MSSQL and proceed with upgrade