Re: iSphere Update from 3.4.1.r to 3.5.0.r

Hi Craig,

I do not think that it makes any difference whether you first uninstall iSphere and reinstall it or continue with the Remediation Page and see what happens.

But most likely I would uninstall iSphere by hand and then reinstall 3.5.0. I have no idea why these things happen from time to time.

For example, today I updated my RDi to 9.5.0.6 at home with no errors and no plug-in migration page. But in the office, where RDi is installed to c:\Program Files\IBM\..., I got that plug-in migration page (or whatever the name is) and when the guy from our system service department (who did the update) clicked "Continue", CMOne and the SVN plug-in went away. I had to reinstall them afterwards.

At home I installed RDi to c:\IBM\... and never had update problems.

All I can say is that you did not make a mistake.

Regards,

Thomas.

Am 14.12.2018 um 11:27 schrieb Craig Richards:

Hi,

Apologies if it's just me being a buffoon, but I'm having trouble updating
iSphere again, but as far as I can tell I'm performing all of the correct
step.

I'm currently on version 3.4.1.r.

I'm running RDi under administrator priviledges.

Here is my update process so far:

1. Download the zip file for 3.5.0.r from Sourceforge and then add that
archive file to RDi using Help | Install New Software.
2. I seleted the components:
1. iSphere Additions for RDi 9.5+
2. iSphere for RDi 8.0+ (Base Component)
3. iSphere Job Log Explorer
4. iSphere Journal Explorer
5. iSphere STRPREPRC Utility
3. Which means I didn't select the compoents:
1. iSphere Addtions for RDi 8.0+
2. iSphere TN5250

When I hit the NEXT button I get a work splash screen with "Cannot Perform
Operation - Computing Requirements" and then it shows me an Install
Remediation Page
Here is an image of what I see:

http://www.greywidget.co.uk/tech/isphere.gif

Presumably I could carry on with the suggestions on the Remediation Page
but it seems like the process should be way more straightforward?

Any advice gratefullly accepted.

Thanks kindly,
Craig