1 this installation cannot be run by directly launching the msi package

1 This Ation Cannot Be Run By Directly Launching The Msi Package Install An Installshield

1 This Ation Cannot Be Run By Directly Launching The Msi Package Install An Installshield

This article discusses how to install an Installshield vendor MSI without using setup.exe.

To deploy a script-driven MSI using Active Directory (or another deployment method that requires the MSI format), you must configure the setup and the target system in the following manner.

At the time of writing, there are several versions of ISScript.msi; major versions 7, 8, 9, and 10, with attendant minor versions for each major release.

The property table of the MSI will often specify the required version of ISScript.msi and it is important to have the correct version for your application, otherwise it may not run.

Different versions of ISScript.msi appear to co-exist on target computers.

The ISScriptx.msi is located in the same folder as the MSI package and must be deployed on the target computer prior to the MSI.

This installs the InstallScript engine required by the MSI package during deployment.

In some cases, the MSI file contains no internal dialogs, and instead the setup.exe file handles user dialogs by interacting with custom actions in the MSI.

These custom actions will fail if setup.exe is not running.

There is no simple solution to this.

However, there are known custom actions to remove from MSI files exhibiting this behavior.

Removing these custom actions will give you a much greater chance of successfully freeing the MSI from its dependency on setup.exe The custom actions are.

Therefore when you run the main MSI which has ISScript.msi as a prerequisite, the main MSI does not have permissions to access ISScript.msi.

If you logged the ISScript install you would probably see a 1603 error.).

Then run up DCOMCNFG and look for Installshield items.

You should find a couple of entries.

Then toggle a user permission which SMS doesnt have access to the middle option of launching user.

Testing was carried out on an XP SP2 VMware virtual machine, reverting back to a clean build after each install, to avoid cross contamination by the different ISScript.msi files.

1 This Installation Cannot Be Run By Directly Launching The Msi Package