I have a.msi that I want to install (chain) with another.msi. I've created the new chained.msi package in Releases and selected the.msi through the Browse button (clicking yes to use streaming).
I've tried both leaving Install Condition as 'Not Installed' and changing it to 'True'. I built the.msi, and ran the install, but it never installs the chained package. There is no mention of it anywhere during the installation. I know that it's included, since the resulting.msi file size is appropriate. It's just not installing. Is there anything I'm missing? What else is required to install a chained.msi?
I'm working with an InstallShield basic MSI installer which has another MSI chained into it as well as a custom action. Installing our application as an administrator.
(I have manually installed Windows Installer 4. Ride Nowhere 20th Anniversary Rar more. 5). Code: MSI (s) (78:50) [13:16:56:734]: Doing action: ISChainPackagePrepare Action 13:16:56: ISChainPackagePrepare. Action start 13:16:56: ISChainPackagePrepare.
MSI (s) (78:50) [13:16:56:765]: Creating MSIHANDLE (3) of type 790542 for thread 3408 MSI (s) (78:C4) [13:16:56:765]: Invoking remote custom action. DLL: C: WINDOWS Installer MSI3FDC.tmp, Entrypoint: ISChainPackages MSI (s) (78:0C) [13:16:56:765]: Generating random cookie. MSI (s) (78:0C) [13:16:56:781]: Created Custom Action Server with PID 3040 (0xBE0). MSI (s) (78:54) [13:16:56:843]: Running as a service. MSI (s) (78:54) [13:16:56:859]: Hello, I'm your 32bit Impersonated custom action server. MSI (s) (78!BC) [13:16:56:968]: Creating MSIHANDLE (4) of type 790541 for thread 2748 MSI (s) (78!BC) [13:16:56:968]: Note: 1: 2205 2: 3: ISChainPackage MSI (s) (78!BC) [13:16:56:968]: Note: 1: 2228 2: 3: ISChainPackage 4: SELECT * FROM `ISChainPackage` ORDER BY `Order` MSI (s) (78!BC) [13:16:56:968]: Closing MSIHANDLE (4) of type 790541 for thread 2748 MSI (s) (78:C4) [13:16:56:968]: Closing MSIHANDLE (3) of type 790542 for thread 3408 Action ended 13:16:56: ISChainPackagePrepare. Return value 3.
Action ended 13:16:56: INSTALL. Return value 3. After Effects Portable Cs4 here. Any help would be appreciated.
By David Cole, Senior Software Engineer, IBM Introduction Install developers often need to include other products within their own setup. Flexera Software’s InstallShield 2009, coupled with Microsoft’s Windows Installer (MSI) 4.5, offers new options for chaining installs together while avoiding the problems associated with the existing options of merge modules and nested installs. This white paper describes using chained.msi packages in InstallShield 2009 and MSI 4.5 to componentize a setup. You will learn how to include other.msi packages within your own so that the result may be installed with the appearance of being a single product. The white paper also compares chained.msi packages with InstallShield prerequisites, which provide another method for including third-party setups.