Custom Action Scripting issue
I'm using Wise Package studio and I've pretty much created my entire windows installer - but I'm running into a slight issue with a custom action of installing an MSI.
Either I choose Install MSI from Destination, Installation or Relative path - I always come up with the same error - either 1721 or 1722 error code. I just can't get this msi to launch AFTER all the files are install (the msi I want to launch is a program that gets installed - or more like just copied to a certain directory). Can anyone guide me here? I don't think I've provided enough info and I'm not sure what else I should provide, so please ask, and I'll provide any info you need.
Thanks.
Either I choose Install MSI from Destination, Installation or Relative path - I always come up with the same error - either 1721 or 1722 error code. I just can't get this msi to launch AFTER all the files are install (the msi I want to launch is a program that gets installed - or more like just copied to a certain directory). Can anyone guide me here? I don't think I've provided enough info and I'm not sure what else I should provide, so please ask, and I'll provide any info you need.
Thanks.
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
Sathia
18 years ago
Have you ran the Package Validation tool to validate ICE of you MSI?
If you solved ICE Errors, You problem may be solved.
Else Send me the screen shot, I will try me level best to help you..
If you solved ICE Errors, You problem may be solved.
Else Send me the screen shot, I will try me level best to help you..
Posted by:
steve02a
18 years ago
I have it right before "InstallFinalize" - attempting to make it the very last thing the user does/sees before they click the finish button (since the MSI file has to get installed into the [INSTALLDIR] first (of course)).
Posted by:
brenthunter2005
18 years ago
Hello,
You need to place this action AFTER the 'InstallFinalize' action.
[8D]
You need to place this action AFTER the 'InstallFinalize' action.
[8D]
Posted by:
steve02a
18 years ago
I got it working now after I placed it AFTER "InstallFinalize" and I removed [INSTALLDIR] from the Property Settings field. What it does is just install the MSI and zips right though - no user intereaction required at all.
However, that's nice and all, but I'm intending to launch the MSI so the user has to go through a license screen, verify their virtual path and port # (the msi is a web-application and the msi is created from visual studio) - so I want the users to see those screens. So, here in Wise, I just see "Install" MSI from xxx..nothing about "Launch".
Any suggestions guys? and thanks for all your help so far....
However, that's nice and all, but I'm intending to launch the MSI so the user has to go through a license screen, verify their virtual path and port # (the msi is a web-application and the msi is created from visual studio) - so I want the users to see those screens. So, here in Wise, I just see "Install" MSI from xxx..nothing about "Launch".
Any suggestions guys? and thanks for all your help so far....
Posted by:
brenthunter2005
18 years ago
mmmmmm.....
At the end of the day, all Wise is doing is adding the .MSI to the Binary table and calling this MSI. You'd guess that the nested MSI would just "launch".
How about trying to add a custom action that simply calls "msiexec /I filename.msi"?
At the end of the day, all Wise is doing is adding the .MSI to the Binary table and calling this MSI. You'd guess that the nested MSI would just "launch".
How about trying to add a custom action that simply calls "msiexec /I filename.msi"?
Posted by:
steve02a
18 years ago
What custom action do I use where I can use "msiexec /I filename.msi" - I'm not seeing anything that would let me simply put that in, then add it to some sequence.
Posted by:
brenthunter2005
18 years ago
There are a couple of ways of doing it.
I think this is the best way: You can include the MSI package as part of your files (in the temp folder etc) and then at the end of the sequence "Execute Program from Path" and add the command-line into the Property table.
I think this is the best way: You can include the MSI package as part of your files (in the temp folder etc) and then at the end of the sequence "Execute Program from Path" and add the command-line into the Property table.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.