Error - Sanity Failed - Upgrade from 8121 to 11

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 mentioned error trace in the logs, you need to follow the solution given below.

Error Trace: 
 [SEVERE] : Problem during PostgreSQL upgrade sanity failed.


In version 8121, edit the updatemanager.bat file that will be present under the Path <ManageEngine\SupportCenter\bin> folder and add the below given entry as shown in the snapshot  


After entering the entry save it and close it. 

Continue with the migration in a new setup. Make sure you do not upgrade in the failed setup again. 

        New to ADManager Plus?

          New to ADSelfService Plus?

            • Related Articles

            • Error when Processing Request during Upgrade - Version8121 - 11

              Error:  While upgrading 8121 to 11011 when you get the below shown error,  Cause of the error: The issue with the Upgrade is that the System defined user kept getting deleted and it was because of data anonymization.   Solution : In 8121,  Go to ...
            • 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 ...
            • 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, ...
            • Office 365 basic Auth deprecation - Solution

              If you are using Office 365, please note that the issue could be due to Microsoft depreciating basic authentication. You have to configure mordern authentication (Oauth) to fix it. Please refer the below article for reference Office 365 basic Auth ...
            • Steps to revert the environment from an upgrade failure situation ?

              1. Rename the failed set up installation folder to <supportcenter_old> . Don't delete the installation folder until the process is completed. Download the existing version which you had before this upgrade from the below archives link. ...