Upgrade failure
Issue:
Solution:
Upgrade fails with error - "Error occurred :: Irrevertable exception occurred"
Analysis:
Tried to start database manually, but it fails to start. Antivirus has been disabled/uninstalled.
Log Traces:
Aug 10, 2016 4:02:37 PM [com.adventnet.db.adapter.postgres.DefaultPostgresDBInitializer] [INFO] : Command to be executed [C:\ManageEngine\AnalyticsPlus\pgsql\bin\pg_ctl.exe, -w, -D, C:\ManageEngine\AnalyticsPlus\pgsql\data, -o, "-p33366", start]Aug 10, 2016 4:02:37 PM [pglog] [INFO] : waiting for server to start....This program is blocked by group policy. For more information, contact your system administrator.Aug 10, 2016 4:02:38 PM [pglog] [INFO] : stopped waiting
Check for any anti virus policy which is blocking the database to start (If disabling anti virus is not possible).
Verify if there is a Group Policy to prevent exe files from running under the appdata folder.
New to ADSelfService Plus?
Related Articles
Upgrade issue in build 3200
Upgrade issue in build 3200 The below cases were identified in local system and couple of customer's system during 3200 upgrade. Issue 1: PGSQL migration fails: Since this upgrade will upgrade pgsql version, pgsql has its own upgrade prior to ...Upgrade Key steps
Key steps that must be followed without which the upgrade may fail. All Analytics Plus Services must be stopped. AnalyticsPlus folder must be given "Everyone" folder permission with "Full Control" before upgrade (Can be revoked after upgrade) ...Failed to upgrade to build 5300/5301
Issue: Upgrade fails while attempting to upgrade to the build 5300/5301. Cause: Upgrade fails due to a necessary system property required for logging slow queries is missing. This issue will arise while attempting to upgrade to the ...Path too long - Upgrade/Backup
The 'Path Too long' problem might occur due to an earlier patch/upgrade that is applied. While upgrading (applying PPM,) the files that are to be overwritten in the PPM will be backed up inside a folder named Patch. The files inside this follow ...Slowness in accessing dashboards after an upgrade to 4000
Analysis: CPU spikes to 100% and the pgsql.exe processes consuming more memory. The phantom server which used to generate the snapshots for all the reports is enabled by default after the upgrade. This process creates load and causes the performance ...