Hi
Version: Developer 8.0
Probject type: Basic
Currently, I have 3 MTS package will create and each package needs its own DOM MSI to insatll.
I have problem to install MSI synchronously...I try
VBSCript try1:
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Install DCOM Application Proxy MSI Synchronously
Started by
MIB426
, Dec 02 2003 00:22
1 reply to this topic
Posted 02 December 2003 - 00:22
CODE |
Dim WshShell Dim Cmd1 Dim Cmd2 Dim Cmd3 Cmd1 = "msiexec.exe /i \\6578\Dump\NTBSPackageExport\CINET.MSI /q" Cmd2 = "msiexec.exe /i \\6578\Dump\NTBSPackageExport\CITG.MSI /q" Cmd3 = "msiexec.exe /i \\6578\Dump\NTBSPackageExport\CIVR.MSI /q" Set WshShell = CreateObject("Wscript.Shell") Call WshShell.Run(Cmd1, ,true) Call WshShell.Run(Cmd2, ,true) Call WshShell.Run(Cmd3, ,true) Set Cmd1 = Nothing Set Cmd2 = Nothing Set Cmd3 = Nothing Set WshShell = Nothing |
This approach wil work on my desktop but not with installshield probject. It desnt create error message but not install any MSI.
VBScript Try2:
CODE |
Dim WshShell Set WshShell = CreateObject("Wscript.Shell") WshShell.Run("msiexec.exe /i \\6578\Dump\NTBSPackageExport\CINET.MSI /q") WshShell.Run("msiexec.exe /i \\6578\Dump\NTBSPackageExport\CITG.MSI /q") WshShell.Run("msiexec.exe /i \\6578\Dump\NTBSPackageExport\CIVR.MSI /q") set WshShell = Nothing |
This approach will install one of MSI for me, but I need all MSI to insatll.
VBScript try3:
CODE |
Dim msi Set msi = CreateObject("WindowsInstaller.Installer") msi.UILevel = 2 msi.InstallProduct "\\6578\Dump\NTBSPackageExport\CINET.MSI", "" msi.InstallProduct "\\6578\Dump\NTBSPackageExport\CITG.MSI", "" msi.InstallProduct "\\6578\Dump\NTBSPackageExport\CIVR.MSI", "" Set msi = Nothing |
This approach is working on my desktop but it gave me error in installshield.
I am running out of ideas. Please help me if u can
Thank You
MIB
Posted 02 December 2003 - 09:01
You cannot run two or more installations at the same time - just think what happens when both installations detect they have to update the same file. Consider nested installations instead.
Your first and second attempts try to run synchronous installations, but also disable any output - try creating log files for more info (which will probably read that another installation is already running).
Your third example doesn't run synchronous installations, but consecutive installations. The true reason for failure is found in the error that was reported. Maybe the first or second installation needed a reboot.
Your first and second attempts try to run synchronous installations, but also disable any output - try creating log files for more info (which will probably read that another installation is already running).
Your third example doesn't run synchronous installations, but consecutive installations. The true reason for failure is found in the error that was reported. Maybe the first or second installation needed a reboot.