Enabler Upgrade Failures - Revision history

Robert: Redirected page to Investigating Enabler Upgrade Issues

2011-07-05T03:38:06Z

Redirected page to Investigating Enabler Upgrade Issues

← Older revision		Revision as of 03:38, 5 July 2011
Line 1:		Line 1:
	~~Created: 07 August 2009. Last Reviewed: 31 August 2009~~		#REDIRECT [[Investigating_Enabler_Upgrade_Issues]]


	~~'''Recovering from Enabler upgrade failures'''~~


	~~'''''Enabler won’t run'''''~~


	In rare occasions, an automated Enabler upgrade may fail due to reasons such as a corrupt database file. If an Enabler upgrade fails, and you are unable to start POS, then the following instructions should be followed to allow you to start POS and ultimately run the upgrade again. These procedures will allow you to run POS again on the old version.


	~~An example of an upgrade failure, would be a message similar to the one below when you attempt to start POS, Nibbler, or Back Office.~~

	[[~~Image:Enabler_Upgrade_Failures_figure_1.jpg~~]]


	* While not critical, if you have the available disk space, it is worthwhile taking a backup of the entire Enabler folder at this point, to avoid the risk of data loss if problems with the recovery occur.
	* Copy all .oxe files in the enabler folder to .exee.g. ''copy c:\enabler\.oxe c: \enabler\.exe'' overwriting the existing files
	* Copy all .oll files in the enabler folder to .dlle.g. ''copy c:\enabler\.oll c: \enabler\.dll'' overwriting the existing files
	* Copy all .opt files in the enabler folder to .rpte.g. ''copy c:\enabler\.opt c: \enabler\.rpt'' overwriting the existing files
	* If there are any files in \enabler\local or \enabler\lantran with an extension of .old, and a date of the current date, then these files should be copied to the same location with an extension of .dbf, e.g.copy c:\enabler\lantran\.old c:\enabler\lantran\.dbf overwriting the existing files.copy c:\enabler\local\.old c:\enabler\local\.dbf overwriting the existing files
	* From the enabler folder from a command prompt, perform a full reindex.e.g. infoctrl indexall

	~~After you have done the above steps you should be able to start POS again. Before rescheduling the upgrade, you should contact Magenta Retail for assistance in determining why the upgrade failed.~~


	~~'''''Enabler runs but upgrade failed'''''~~


	There could be occasions where a failure has occurred during an upgrade but this failure doesn’t stop Enabler from running. It is most important that any failures be investigated before the store commences trading and it is recommended to seek advice from Magenta Retail before continuing.


	If you attempt to re-run an upgrade that has failed, it is most important that you backup any .OLD files that exist in \enabler\local, \enabler\lantran and \enabler\lanmnt folders. '''Failure to backup any .OLD files may lead to loss of data.'''


	If re-running a failed upgrade, it is important that you only replace .OLD files (as explained on the previous page), if the store hasn’t traded since the upgrade failure. '''If the store has traded, replacing files with the .old files may lead to data loss.'''


	~~''If you are unsure about how to proceed following an upgrade failure, it is strongly recommended that you contact Magenta Retail for assistance.''~~

Trevor at 09:42, 31 August 2009

2009-08-31T09:42:36Z

← Older revision		Revision as of 09:42, 31 August 2009
Line 13:		Line 13:
	An example of an upgrade failure, would be a message similar to the one below when you attempt to start POS, Nibbler, or Back Office.		An example of an upgrade failure, would be a message similar to the one below when you attempt to start POS, Nibbler, or Back Office.

	[[Image:]]		[[Image:Enabler_Upgrade_Failures_figure_1.jpg]]

Trevor: New page: Created: 07 August 2009. Last Reviewed: 31 August 2009 '''Recovering from Enabler upgrade failures''' '''''Enabler won’t run''''' In rare occasions, an automated Enabler upgrade ma...

2009-08-31T09:36:20Z

New page: Created: 07 August 2009. Last Reviewed: 31 August 2009 '''Recovering from Enabler upgrade failures''' '''''Enabler won’t run''''' In rare occasions, an automated Enabler upgrade ma...

New page

Created: 07 August 2009. Last Reviewed: 31 August 2009

'''Recovering from Enabler upgrade failures'''

'''''Enabler won’t run'''''

In rare occasions, an automated Enabler upgrade may fail due to reasons such as a corrupt database file. If an Enabler upgrade fails, and you are unable to start POS, then the following instructions should be followed to allow you to start POS and ultimately run the upgrade again. These procedures will allow you to run POS again on the old version.

An example of an upgrade failure, would be a message similar to the one below when you attempt to start POS, Nibbler, or Back Office.

[[Image:]]

* While not critical, if you have the available disk space, it is worthwhile taking a backup of the entire Enabler folder at this point, to avoid the risk of data loss if problems with the recovery occur.
* Copy all *.oxe files in the enabler folder to *.exee.g. ''copy c:\enabler\*.oxe c: \enabler\*.exe'' overwriting the existing files
* Copy all *.oll files in the enabler folder to *.dlle.g. ''copy c:\enabler\*.oll c: \enabler\*.dll'' overwriting the existing files
* Copy all *.opt files in the enabler folder to *.rpte.g. ''copy c:\enabler\*.opt c: \enabler\*.rpt'' overwriting the existing files
* If there are any files in \enabler\local or \enabler\lantran with an extension of *.old, and a date of the current date, then these files should be copied to the same location with an extension of *.dbf, e.g.copy c:\enabler\lantran\*.old c:\enabler\lantran\*.dbf overwriting the existing files.copy c:\enabler\local\*.old c:\enabler\local\*.dbf overwriting the existing files
* From the enabler folder from a command prompt, perform a full reindex.e.g. infoctrl indexall

After you have done the above steps you should be able to start POS again. Before rescheduling the upgrade, you should contact Magenta Retail for assistance in determining why the upgrade failed.

'''''Enabler runs but upgrade failed'''''

There could be occasions where a failure has occurred during an upgrade but this failure doesn’t stop Enabler from running. It is most important that any failures be investigated before the store commences trading and it is recommended to seek advice from Magenta Retail before continuing.

If you attempt to re-run an upgrade that has failed, it is most important that you backup any .OLD files that exist in \enabler\local, \enabler\lantran and \enabler\lanmnt folders. '''Failure to backup any .OLD files may lead to loss of data.'''

If re-running a failed upgrade, it is important that you only replace .OLD files (as explained on the previous page), if the store hasn’t traded since the upgrade failure. '''If the store has traded, replacing files with the .old files may lead to data loss.'''

''If you are unsure about how to proceed following an upgrade failure, it is strongly recommended that you contact Magenta Retail for assistance.''