Upgrade failure from 10500 to 10512.
Exception missing file
HelpDesk/ServiceDeskplus-MSP/tools/postgres/bin/gettimezone: not found
The upgrade failed because of a missing file Gettimezone.
Please navigate to the application folder ManageEngine/ServiceDeskPlus-MSP/tools/postgres/bin
Check if there is a file called Gettimezone
If the file is already available in the above folder please follow these steps
1. Stop the Manageengine ServiceDesk Plus-MSP application
2. Go to the directory ../ManageEngine/ServiceDeskplus-MSP/tools/postgres/bin. Move the existing 'gettimezone' file to a different location outside ManageEngine installation directory.
3. Rename the 'gettimezone_64' as 'gettimezone'.
4. Initiate the upgrade. This should do it.
New to ADSelfService Plus?
Related Articles
10.5 Linux Upgrade failure and solutions
Traces in logs : 1. java.lang.Exception: InitPgsqlScript exited with value :: 1 at com.adventnet.persistence.PostgresPreProcessor.executeInitPgsqlScript(PostgresPreProcessor.java:1733) 2. PGSQL Permission related errors. 3. SDP MSP installed as root ...Upgrade failure from 1420X to 14300.
Error trace: 5 Sep, 2023 6:08:56 PM [com.adventnet.tools.update.installer.Unzipper] [INFO] : lib/phantomjs/linphantomjs/phantomjs 25 Sep, 2023 6:08:56 PM [com.adventnet.tools.update.installer.Unzipper] [SEVERE] : ERR:Exception while writing ...Upgrade failure to 10500 - Linux platforms
You may experience an upgrade failure in linux platforms when upgrading to 10500. Here are the traces from logs, Feb 21, 2020 4:55:03 PM [com.adventnet.tools.update.installer.Unzipper] [SEVERE] : ERRUnexpected Error. Please click View Log>> for ...SDP MSP solution for postgres 11 upgrade issues
When ServiceDesk Plus MSP 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 ...ServiceDeskPlus MSP Upgrade Instructions
Kindly follow the below instructions for the upgrade. 1. We highly recommend you do the upgrade in a test environment first. 2. Below is the upgrade path, kindly proceed with the upgrade based on your current version: 10500 >> 10538 >> 10600 >> 10611 ...