Submit a Ticket
Upgrade using AMI to v2.6.0 from earlier versions may fail with "Configuration Failed" and "Could not migrate database to version 2.6.0 scheme"
Upgrade using AMI to v2.6.0 from earlier versions may fail with "Configuration Failed".
The following error may be printed in the "config_shell_commands.log" file:
perform_shell_commands(:629) Could not migrate database to version 2.6.0 scheme, returned: 256
handle_configuration_result_notification(:34) Due to configuration failure = Stopping cpmagent
If you encounter this error, please use the latest 2.6.X version AMI.
Reference defect number – N2WS-8408, fixed in v2.6.0a (AMI only)
Link to Release Notes and the latest patch –
Updated: 20 Jul 2019 11:30 AM
Help us to make this article better
Upgrade using AMI to v2.6.0 from earlier versions may fail with the Configuration Wizard timing out and "Could not upgrade mysql"
CPM Server may fail to finish configuration when upgrading from v2.1.3 to v2.1.3a using AMI
Linux scripts may start failing after upgrading to a new CPM version (using AMI) or migrating CPM to a different account/region
CPM Server upgrade may fail with the "Reason: The instance ID 'i-1234567890abcdef' does not exist" and "Configuration Failed" errors
Installation/upgrade using the AMI method may fail when using proxy with error 500 displayed
Help Desk Software
by Zoho Desk