I have gone through the process of creating a custom action and calling an .msi. (nested .msi) The problem that I have is that the nested msi does not get removed during uninstall. How can I correct that?

Thanks in advance.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
http://www.wise.com/KBArticle.aspx?articleno=1769&keywords=call+msi+custom+action
Answered 05/25/2005 by: bheers
Second Degree Blue Belt

Please log in to comment
0
I am using Admin Studio. I do not know how to create the nested .msi uninstall similar to what is being said here within the Wise documentation.
Answered 05/26/2005 by: terranceallen
Orange Belt

Please log in to comment
0
http://support.installshield.com/kb/view.asp?articleid=q105706

To add a custom action that launches the installation of a child setup:

Select the Custom Actions view.

Right-click on Custom Actions and select the Custom Action Wizard.

In the Basic Information panel, enter a name and comment for your action and click Next to continue.

In the Action Type panel, select Launch another .msi package from the Type field and select Stored on the Source Media or Included within your Main Setup as the Location. Click Next.

In the Action Parameters panel, select your MSI package from the machine. In the Target field, you can specify command-line switches to pass to the child installation. For example, to install all the features of the child installation with their default settings and to use the same value for the ALLUSERS property used by the parent installation, type the following into the Target field:
ARPSYSTEMCOMPONENT=1 ADDDEFAULT=ALL ALLUSERS=[ALLUSERS]
Click Next and select the default options on the Additional Options panel and click Next until you finish the Wizard.
To create a custom action that launches the uninstall of the child setup:

Select the Custom Actions view.

Right-click on Custom Actions and select the Custom Action Wizard.

In the Basic Information panel, enter a name and comment for your action and click Next to continue.

In the Action Type panel, select Launch another MSI package as the Type and An application that is advertised or already installed as the Location. Click Next.

In the Action Parameters panel, select the MSI package in the Source field and specify REMOVE="ALL" in the Target field.
Answered 05/26/2005 by: bheers
Second Degree Blue Belt

Please log in to comment
0
I'm not sure how IS Admin Studio handles this but in Wise you also need to add a condition to your Removal custom action so that the action only takes place on removal (IF Installed AND REMOVE)
Answered 06/01/2005 by: BobTheBuilder
Purple Belt

Please log in to comment
0
Hi,
I need some help so bad. I'm getting hiberfil.sys error when I run my .exe. I create a package in installshield and pushing it through sms installer. Google solution is control panal->performance and maintainse-->Power Option and under hibernation uncheck enable. I did that and recomiple my script but I'm still getting the same error. If I make the change in the machine then it gives me page.sys is not able to opened. Please let me know how to fix it. This project has to go tommorow..
THanks
Answered 06/23/2005 by: Result
Orange Belt

Please log in to comment
0
result there is no way on earth that you should include either hiberfil.sys or page.sys in your msi. Remove them both and see how you go because they are OS files that you shouldnt include in your capture.
Answered 06/24/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
HI jim,
It is not included in my project at all. But after building a project when I try to install it it gives me that hiberfil.sys message. If I getaway with it then it gives me pagefile.sys message. I know it is an OS file. No absolutly not it is not included in the package.
Please send me more ideas..
Thank you
Answered 06/24/2005 by: Result
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity