Why is the behaviour of a vendor msi different when chained in InstallShield?
Problem - vendor msi fails to start a service (error 1920 insufficient privileges) when chained msi installation.
I have a 'parent' msi with 2 chained msi's:
Package1=32bit - installs ok.
Package2=64bit - fails to start a service (error 1920 insufficient privileges).
Package2 installs fine standalone , only when chained does it fail.
I am logged in as local admin (Win7x64) when installing the parent msi.
Process Monitor appears to show that required .dll's are not installed when the chained msi attempts to starts the service.
Why is the behaviour of a vendor msi different when chained? How can I resolve this error?
Answers (5)
Maybe calling the absolute path of the installer for the x64 package might help?
c:\windows\system32\msiexec /i package1.msi /q
C:\Windows\SysWOW64\msiexec /i package2.msi /q
Hi,
Using chained MSI is not the best practise,suggest you to use a batch file or Vb script to execute these MSI one by one.
Managing the installation as well Uninstallation would be easier for you.
If this approach is really necessary then go through the following link
Do not chain a 64 bit installer in a 32 bin MSI. 32 bit MSI do not have the capability to run anything which is 64 bit. MSI would be the least thing it could run.
Best would be to install it one after the other and there are a lot of ways to do it. Do not overcomplicate these small things while packaging.
It might be problematic starting a 64bit instance of msiexec.exe from a 32-bit installer..
Not sure though since I've been fortunate enough to avoid chaining installers so far.
