11.0 Upgrade related fixes

11.0 Upgrade related fixes

cx tried to upgrade from 11016 to 11020 but it failed. 


27-Apr-2022 09:11:50  [SYSERR]  [INFO] :  at com.adventnet.tools.update.installer.ApplyPatch.run(ApplyPatch.java:286)
27-Apr-2022 09:11:50  [SYSERR]  [INFO] :  at java.lang.Thread.run(Thread.java:748)
27-Apr-2022 09:11:50  [com.adventnet.servicedesk.updatemgr.util.SDPostProcessor]  [INFO] : Problem during installation of patch {0}org.postgresql.util.PSQLException: FATAL: password authentication failed for user "postgres"
at org.postgresql.Driver$ConnectThread.getResult(Driver.java:403)
at org.postgresql.Driver.connect(Driver.java:261)
at java.sql.DriverManager.getConnection(DriverManager.java:664)
at java.sql.DriverManager.getConnection(DriverManager.java:247)
at com.adventnet.persistence.DefaultPostProcessor.UpdatePermissionsForDefaultUser(DefaultPostProcessor.java:1490)
at com.adventnet.persistence.DefaultPostProcessor.installPatch(DefaultPostProcessor.java:2099)
at com.adventnet.servicedesk.updatemgr.util.SDPostProcessor.installPatch(SDPostProcessor.java:62)
at com.adventnet.persistence.DefaultPostProcessor.install(DefaultPostProcessor.java:1423)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.adventnet.tools.update.installer.Unzipper.contextPostInstallation(Unzipper.java:1716)
at com.adventnet.tools.update.installer.Unzipper.invokePostInstallationClasses(Unzipper.java:1505)
at com.adventnet.tools.update.installer.ApplyPatch.installPatch(ApplyPatch.java:498)
at com.adventnet.tools.update.installer.ApplyPatch.run(ApplyPatch.java:286)
at java.lang.Thread.run(Thread.java:748)

27-Apr-2022 09:11:50  [SYSERR]  [INFO] : org.postgresql.util.PSQLException: FATAL: password authentication failed for user "postgres"


Super user password cannot be found (FIX)
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.


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.


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

        New to ADManager Plus?

          New to ADSelfService Plus?

            • Related Articles

            • How to build a test environment and try upgrade in SupportCenter Plus ?

              When you are planning to upgrade SupportCenter Plus to the latest version, it is highly advisable to try the upgrade on the test environment first so that you will be confident about the upgrade on the Production server. Make sure the test setup is ...
            • 11.0 Upgrade failure Inputs needed for analysis

              To analyze Supportcenter plus upgrade failure cases (Upgrade from 8121 - to 11.0 version), we need following types of logs. 1) If upgrade itself got failed -> need SCP\server\default\log for analysis 2) After upgrade, if the product does not start, ...
            • solution for postgres 11 upgrade issues

              When Supportcenter Plus is upgraded to 14300 or later, postgres is also upgraded to 11.17. If you are using bundled postgres, data migration through pgdump and restore mechanism also happens. To ensure efficiency in Postgres 11.17, make sure your ...
            • Error - Sanity Failed - Upgrade from 8121 to 11

              While upgrading from 8121 to 11, after executing Updatemanager.bat and if the update fails, You need to check the Updatemanager logs in the path < Support Center Plus Application path -> Server-> Default-> Logs > .  And if you find the below ...
            • How to upgrade SupportCenter Plus instance ?

              Users who wants to upgrade the Supportcenter Plus instance needs to proceed with the following steps :  Building a test environment is must while upgrading SupportCenter Plus. It is highly advisable to try the upgrade on the test environment first so ...