Nested Installation .msi Won't Install
Posted 02 January 2003 - 19:10
On a Win 98 machine, I'm getting this:
This Installation Package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
If I fire the nested .msi file by itself on this machine, independent of the calling installation, it works fine.
What could be the problem?
Posted 03 January 2003 - 17:03
I still can't understand why it works if run outside of my Parent install. This would tell me the database is OK, but for some reason, when called from the Parent install (Custom Action runs it from source) if bombs!
Posted 04 January 2003 - 15:22
If this is really a "nested installation" custom action (type 7, 23, or 39) it should be placed in the execute sequence between InstallInitialize and InstallFinalize.
Posted 06 January 2003 - 17:13
I get the same error if I run our installation from CD or from my InstallShield build directory, which I share then map to from the target machine. If I run the .msi file independent of our installation process, it works fine from either location.
Posted 07 January 2003 - 16:17
Maybe the path.
For this type of CA the property must be the full path to msiexec and the target field must hold /i and the full path to the msi file. Double check your paths.
Posted 08 January 2003 - 17:40
/i [SOURCEDIR]\myfile.msi .
I would think this is OK since it works on all other OS's.
This is a stumper!
Posted 09 January 2003 - 16:49
I just duplicated the CA and conditioned the two with Version9X to run on 9X systems without the trailing "\" after [SOURCEDIR] and Not Version9X to run on non-9X systems (has slash).
I then tried without the "\" on VersionNT systems and it seemed to work. So, back to one custom action without the "\"!
Thanks again, Stefan!!!!!