Hi,

When you run the .vbs manually it execute but when you deploy the msi which call the vbs it doesn't run.

Has anyone had this problem? The vbs contain multiple msi which run one after the other when execute.

Thanks!
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
You can only run one MSI at a time. Thus, your VBS's container MSI will not allow subsequent MSIs to run concurrently. If you enabled Windows Installer logging, you'd see a message to that effect in the log.

How are you deploying MSIs? Just about every system I can think of can cope with deploying MSIs in a sequence.
Answered 05/25/2010 by: VBScab
Red Belt

Please log in to comment
0
The vbs contain multiple msi which run one after the other when execute.

It's not going to work then, as you can only have one msiexec running unless you use chained install

http://support.microsoft.com/kb/306439

It's not recommended though
Answered 05/25/2010 by: timmsie
Fourth Degree Brown Belt

Please log in to comment
0
you can install a bunch of msi's via a vbscript (one install at a time) and create a log file to see success or failure

remember your msi engine will not recgonize the wscript object in your vbscript
Answered 05/25/2010 by: cygan
Fifth Degree Brown Belt

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