nested msi problem, Wise for Windows Installer
i have my main installation file which calls a nested msi in the folder structure like this:
->main.msi
->folderA\appA.msi
i am using Install MSI From Relative Path to call this nested msi by filling Installation to Run as "folderA\appA.msi", now when I set up a button to call this action and click it i get fatal error saying installation ended prematurely! any ideas why?
doing Run->Log created log file with this error near the end:
Action ended 17:00:23: installApp. Return value 3.
DEBUG: Error 2896: Executing action installApp failed.
Internal Error 2896. installApp
where installApp is the custom action that calls the nested msi. here are my settings :
Custom Action Name: installApp
Installation to Run: folderA\appA.msi
"No Sequence" is checked and i dint change anything in Properties.
double clicking the nested msi works just fine..PLZ HELP
->main.msi
->folderA\appA.msi
i am using Install MSI From Relative Path to call this nested msi by filling Installation to Run as "folderA\appA.msi", now when I set up a button to call this action and click it i get fatal error saying installation ended prematurely! any ideas why?
doing Run->Log created log file with this error near the end:
Action ended 17:00:23: installApp. Return value 3.
DEBUG: Error 2896: Executing action installApp failed.
Internal Error 2896. installApp
where installApp is the custom action that calls the nested msi. here are my settings :
Custom Action Name: installApp
Installation to Run: folderA\appA.msi
"No Sequence" is checked and i dint change anything in Properties.
double clicking the nested msi works just fine..PLZ HELP
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
brenthunter2005
18 years ago
Calling a nested MSI requires that the action is placed in the correct sequence. Nested installation actions should be placed between the InstallInitialize action and InstallFinalize action.
And if need be, remember to condition the custom action so that it only installs at install time.
And if need be, remember to condition the custom action so that it only installs at install time.
Posted by:
iori
18 years ago
it works if place it between the actions u mentioned EXCEPT its run as part of the main msi without any user input(i guess thats how nested msi work). what i was thinking is how can i display a dialog that can have buttons that can call any other msi's separately and then after those appz are installed continue with the main installation.
Posted by:
brenthunter2005
18 years ago
OK, the first idea that comes into my head is to create a new dialog in your main installation with checkboxes etc for your nested applications, and then condition those nested installations of the values of the checkboxes.
Posted by:
iori
18 years ago
this way will it let the user to input any required data for the child msi's? i think not as it will be called as a nested msi with no dialogs..right?
Posted by:
brenthunter2005
18 years ago
That is correct, but again, you could create a dialog that the user can enter these values in, and then pass those values as public properties to the child MSI.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.