UI upgrade of engine fails with no explanation

[xz4gb8]

As part of of the upgrade process, an opportunity to upgrade the Retrospect Engine is offered. It will always fail since no mention of requiring the engine be stopped is ever mentioned. This requirement was probably forgotten and never written down in the previous upgrade. Upgrades are not a daily occurrence. It should not be necessary to either guess or read through pages and pages of documentation to be reminded of this.

 

I would expect it would take minimal time and testing to simply add text to the UI noting that the engine must be stopped for a sucessful upgrade to occur.

[j.a.duke]

As part of of the upgrade process, an opportunity to upgrade the Retrospect Engine is offered. It will always fail since no mention of requiring the engine be stopped is ever mentioned. This requirement was probably forgotten and never written down in the previous upgrade. Upgrades are not a daily occurrence. It should not be necessary to either guess or read through pages and pages of documentation to be reminded of this.

 

I would expect it would take minimal time and testing to simply add text to the UI noting that the engine must be stopped for a sucessful upgrade to occur.

I think a better solution would be to include in the engine installer commands to stop the engine if it is running, perform the installation, then start the engine again.

 

That would be the way that many applications handle this scenario.

 

Cheers,

Jon

[bdunagan]

Sorry for the confusion over this issue. The upgrade process through the 10.1 console does not require you to manually stop the engine beforehand. The console uses our standard installer, and that installer always stops the existing engine if it's present and running, as part of the preflight workflow. One issue could be that the running engine is busy and finishing up before it stops.

 

Have you continued having an issue with this?