MSIEXEC not executing working script at CustomAction point

Hi Folks,

I have a need to install multiple packages, each wrapped in .MSI files.  I could create a batch file that executes each from CD but would prefer to use a single .MSI file to install all three.  My understanding was that I could add the three .MSI files into the application folders then run a Custom Action (after commit), in this case a .vbs that executes MSIExec, to silently install the apps.

The issue I'm having, however, is that while the script runs - I've tested with displaying a msgbox - the MSIEXEC command does nothing at all.  The file extracts into the correct folder and the script is also there.  I've tried logging outputs, etc, but it just seems to do nothing.  I ought to mention as well that outside of the MSI wrapper the script runs as expected.  The script is as follows:

Help would be appreciated.

Thanks,

Jes
option explicit
on error resume next
Dim WshShell
Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run "msiexec /i ""TestApplicationForInstall_MSI.msi"" /qf"

Open in new window

JesGothAsked:
Who is Participating?
 
Vadim RappConnect With a Mentor Commented:
> I could add the three .MSI files into the application folders then run a Custom Action

It's bad idea. See http:Q_23498090.html for details.

As for vbscript, I would specify full path to the msi file in WshShell.Run  . You can run filemon (from sysinternals.com) to see if your msi file is actually opened.
0
 
ThinkPaperConnect With a Mentor IT ConsultantCommented:
in addition to vadimrapp1's comments, when running this line, eliminate the /qf switch and run a test on your machine. Does it pop up the install on your machine?

WshShell.Run "msiexec /i ""\\server\install\TestApplicationForInstall_MSI.msi"" "

0
 
smilingpolitelyConnect With a Mentor Commented:
The simple answer is that you can't run a nested MSI in that way.  The only way to run a nested Windows Installer package is using Custom Actions 7, 23 or 39.  Otherwise, the second installer sees another install is in process and fails.

Not only that, these features have been deprecated from the Windows Installer API.  

http://msdn.microsoft.com/en-us/library/aa368010(VS.85).aspx
0
 
JesGothAuthor Commented:
Thanks to all, hope you're happy with me splitting the points.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.