/build/static/layout/Breadcrumb_cap_w.png

OpenEdge network client 10.0a

Hi

I'm trying to make a MSI out of the original netsetup of Progress OpenEdge network client 10.0a.
Original it's a setup.exe developed using InstallShield 7.0.

Why repackage?
The original netsetup is depending on being installed from where the OpenEdge server is installed.
And I don't care much for ISS-files.

I also want to add the property PROGRESS_SERVER="<share / driveletter>" to the MSI to make the package independent of the server.



I have made about 100 snapshots using InstallShield AdminStudio6 and also tried WinInstall, but always the same result.

It works fine for the loged on user, but when I starts a program using runas and the program is dependent of the OpenEdge client it returns some errors.

"Error occured while creating CONTROL-FRAME: CtrlFrame.
Ugyldig klassestreng.
Error code: 0x800401f3 (5898)"

"**Unable to realise CONTROL-FRAME widget. (4025)"

"Unknown error code 1 for attribute NAME of the CONTROL-FRAME widget. (4104)"

"Unable to set attribute NAME in widget of type CONTROL-FRAME. (3131)"

I have tried to use filemon and regmon to discover any dependencies that are missing but can't find anything.
I have looked things in registry, especially HKCU settings but can't find anything.

I can/must have missed something but what??



When installed from the original setup the program runs fine, even when using runas.

I'd be most greateful for any support.


br
andler

0 Comments   [ + ] Show comments

Answers (0)

Be the first to answer this question

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ