Silent installation of OpenEdge 10.2a
Hi guys,
I have some problems with the silent installation of the openedge 10.2a Shared Network Installation.
i read some installation documents from the company but these parameters didn't work.
Have any one a idea how i could solve these problem.
The installation package is an installshield exe. and the parameters with a .iss also didn't work
BG
Phil
Answers (6)
This is a serious thread necro, but I just got done dealing with this.
For anyone still wondering, you can do a silent install on OpenEdge. It is a pain the way PSC modified the installer, and also bundled in a program that requires you to except a EULA.
Now, the big problem with this is that OpenEdge has to install Document Explorer 2005. But you have to accept the EULA. This is where the OpenEdge silent install fails. The work around is to install DExplore before OpenEdge, which circumvents this issue. Find a copy of the Microsoft Document Explorer 2005 installer online, and script that to run as a silent install before triggering the OpenEdge install. Everything should work fine after that.
This is what my OE install line looks like:
\\server\oe102a\netsetup\setup.exe -psclogC:\Epicor905 -s
I enabled logging, it makes troubleshooting this install much easier! Put your setup.iss response file in the same directory as the setup file. I couldn't get this to work when I would define the path. Using the -s switch makes it automatically use it.
This document contains a section on how to create your response file:
http://documentation.progress.com/output/OpenEdge102b/pdfs/gsins/gsins.pdf
Unfortunately, I don't think there is any way to do an unattended UNinstall. You are always prompted with a Yes/No dialog, and AFAIK you can't create a response for it.
Have any one a idea how i could solve these problem.
What exactly are the problems?
How do you execute the installation?
Any error messages?
i wanted to run the installation silent. but when i wanted to run the installation with some installshiled parameters. The setup starts normally with the UI.
I execute the installation with following parameters: -s /f1="path to iss file", or -psc_s -psc_f1=path to response.ini file,
everything i tried it didn't work. :(
When i start the installation with the .iss file the log file shows me no error.
have you tried setup.exe /s /f1"<path to iss file>" /f2"<path to log file>" ?
This would be the standard notation of InstallShield.exe parameters. Not sure if the quotes are needed if there are no spaces in the path...
PJ
Not sure if the quotes are needed if there are no spaces in the path
Nope, they're not. Only if it's spaces in the path, but I have a habit of adding the quotes either way.
I've also noticed that in some cases (as Pieter have in his cmd line) you are required to add the log file switch, or the installation will fail.
It's a good idea to add the log file either way to get some pointers if install fails.
yes i tried everything i found on the internet. Nothing works, :(
I have the installation documentation of the sofware but, this also does not work...
Phil
Comments:
-
Dis you get anywhere with this in the end Phil - oreillyr 11 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
-psc_r (not /r) to record a response.ini (not .iss)
-psc_f2="path and filename" to specify a reponse.ini to record or use
-psc_s for a silent install with a response.ini
-psc_f2="path to file and name" for a log file - delap 10 years ago