Our customer is unable to install upgrades from us. We deploy our upgrades and use the RDKInstall subroutine to install the upgrade.

If we copy over our development version of OI it works fine.

Help, our customer not very happy.

Peter,

Can you provide some more detail? Is this an Upgrade/Module deployment? Does nothing work or just some things? How, exactly are you sending the update and how does the application call RDKInstall and know what directory to look at? What version of OI?

[email protected]

SRP Computer Solutions

]Can you provide some more detail? Is this an Upgrade/Module ]deployment?

Yes

]Does nothing work or just some things?

Some things. One customer running Novell has to copy our development version of OInsight over to get the upgrade to go through. Another (also running Novell) seems to be able to put an upgrade through as long as all users are logged out (Is that normal?)

Yesterday, another customer (running just Windows) couldn't get an upgrade through, switched to Development system as above, and successfully installed the first but not the second upgrade.

]How, exactly are you sending the update and how does the application ]call RDKInstall and know what directory to look at?

We Compress the Rev files with Pkzip and e-mail. They copy the zip file into a temporary directory. Our install upgrade routine prompts for the name of that directory, and then calls PKUnzip which unloads it into a specific directory we have set up for upgrades. RDKInstall then installs from this specific directory. When we check that directory after the upgrade process, the correct files have been unzipped into the correct place.

] What version of OI?

3.6

Help, we have some sad customers at the moment.

Peter,

First, we've been deploying upgrades for using the RDKInstall function in a runtime environment for over a year without any problems. So the good news is that this should work normally, the bad news is that we have to look harder for the solution to your problem.

Second, it is normal that all user be logged out of the application before running the RDKInstall function. In this regard it is no different than installing a Revelation update or upgrade using InstallShield and it requires the same thing.

Third, I can't see how a runtime engine versus a development engine should make the difference. Are we certain that other things aren't happening in the process of switching engines? For instance, they might be logging in as as ADMIN or SUPERVISOR to rename files which then also gives them the rights necessary to complete the upgrade. Have you (or can you) visit the site and trace through everything to make sure everything is working as expected? Unless you get to the point of absolutely pinpointing the problem to the RDK routines you could easily be running in circles with this. Another idea for your Novell clients is to have the update files unzipped in a local drive instead of a network drive. This should eliminate any network access rights issues.

Otherwise, your strategy looks reasonably sound and simple and I assume that it has always worked on your systems.

[email protected]

SRP Computer Solutions

Peter,

I confirm Don's comments that RDKINSTALL - in the general methodology you describe - works. We have been deploying by zipping the sysupgrade vol and then getting client to decompress in a suitable directory (eg C:\Upgrade). Then they run a simple tool which we created which verifies the path and then calls RDKINSTALL MyPath.

Suggest that before you zip up your deployment vol that you inspect it: ie attach_volume Path_To_Deployment. Then OPen Record SYSUPGRADE from System Editor.

Regards

Richard Bright

Yesterday I visited two of our customers with this problem. First one with Novell, an upgrade that should have taken several minutes to install went through in just a few seconds. I am checking @FILEERROR as I notice it returns an error condition if the user chooses the wrong directory. The program assured us there was no problem. When I copied the Development files over, the upgrade took the several minutes and actually worked. Same result at the Windows Network site. Does someone know something I don't about checking whether RDKInstall thought the upgrade process was successfull? It would be nice if could at least make my program say something other than 'Upgrade successfully completed.'.

In both cases I didn't change log-ins, and in fact was in Supervisor access anyways.

The files copied were OEngine.exe, OInsight.exe, LH.DLL.

Thanks in Advance

Peter

View this thread on the forum...