I am attempting to put together a package for the silent (no user interaction) install and uninstall of an application using InstallShield. I did not create this application and don't have access to any kind of source for the installation. I created a response file using setup.exe /r for both the install and the uninstall, named install.iss and uninstall.iss respectively. When I run setup.exe /s /f1"%cd%\install.iss" with the program uninstalled, it runs just great. Trouble is, when I run setup.exe /s /f1"%cd%\uninstall.iss" with the program installed, I get an error code! (number 3) Did I not create this response file correctly? Why should it work with the install and not with the uninstall? Program is Teradata Manager 12.0, any input would be appreciated.
You are probably dealing with an installer that was built using "Custom" dialog boxes and scripts that do not support the silent mode install or uninstall.
You could try running the installer using this :
Which will create an MSI engine logging file. This is very verbose, but that might help you troubleshooting this issue. But this unlikely...
Unfortunately, I recently troubleshooted that same kind of issue in a setup I had the code for, and that "ErrorCode=-3" is pretty much useless, ranging from internal MSI variables not being set, to error messages being displayed by the installer and not being handled properly...
Since you're apparently using exe rather than windows installer, you might try using InnoSetup instead of InstallShield to package the install. We've had good luck with it for putting together complex installation packages, and it has /silent and /verysilent modes for unattended installs. It's free, so there's no risk in trying it out.
Big downside is that it can't make msi files for deploying w/ GPO, but it's great for exe installs.