Investigating Enabler Upgrade Issues

From EnablerWiki
Revision as of 04:55, 23 May 2011 by Robert (talk | contribs) (Created page with "'''Note: If unsure of the cause of the upgrade failure, contact Magenta Support for assistance before continuing''' ===How to recover from an auto upgrade that has partially run...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

Note: If unsure of the cause of the upgrade failure, contact Magenta Support for assistance before continuing

How to recover from an auto upgrade that has partially run but failed

During the upgrade process the system will rename existing files and tables and then copy in new version of the files and tables and then migrate the old with the new. Once this migration is complete a reindex processes then runs across the new tables, occasionally this process can be interrupted and cause the upgrade to not fully complete. Re-running the upgrade process after a failure can potentially cause loss of data so file sizes and modified dates will need to be reviewed prior to re running upgrade.

Unable to open Enabler after upgrade

The application files in the enabler folder require being from the same version. If any of the application files in the enabler folder do not fully or properly migrate then usually a message similar to the following will display when any attempts to open enabler applications are made

Retrieved from "https://theoracle.magentaretail.com.au/index.php?title=Investigating_Enabler_Upgrade_Issues&oldid=848"