Systems Management Question

SMS *msi fails on some clients with '1603'; works on others

07/27/2006 12232 views

I've rolled out the msi from Macromedia for the flash 8 player. I've used exactly the same command line and procedures for all other software I have rolled out with no issues.

Some of the clients accept and it installs fine, but about 2/3rds come back with a failed message:

Last execution code: 1603

I can't see anything obvious and am a bit stumped - any ideaS?
0 Comments   [ + ] Show comments


Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

All Answers

Google the error "msi error 1603"
And the first return is from appdeploy with really good information :-D

In order to see just what the problem actually is you should enable Windows Installer logging which will allow you to view a log of all attempts and failures related to your installation.

Generally this problem revolves around SYSTEM account permissions on the target system, free disk space on the target system, or bad file download or locked/inaccessable file. For more help...

One member reports having received this error installing MSN Messenger 6.2. They were able to get it to install successfully (and eliminate error 1603) by de-activating Ad-Watch from Lavasoft.


Is one of them :-D
Answered 07/28/2006 by: Scanman
Senior Yellow Belt

I've experienced the same sort of issues with Macromedia Studio 8. I've also been having different problems with other apps, including Roxio 8
Answered 07/31/2006 by: leegend
Orange Belt

Verify if it's a InstallShield msi and if it uses the ISScript.Msi or the InstallShieldScriptingEngine merge module, in that case it will set the "InstallShield InstallDriver DCOM" component to "The Interactive user" which means that it will run under the logged in users context. If you user has administrative rights the installation will be okey otherwise it will fail with the 1603 error.

Locate the "HKCR\AppID\<GUID>\RunAs" and remove it from the registry table.
This will change the Identity from "The interactive user" to "The launching User".

Also make sure to delete this entry before launching the msi to ensure that no other installation has set the Identity to "The Interactive user".
Answered 07/31/2006 by: AngelD
Red Belt

Remove the entry for InstallShield or for Roxio? I'm thinking you mean InstallShield
Answered 07/31/2006 by: leegend
Orange Belt

Hi leegend,

I'm talking about either the ISScript.Msi, the InstallShieldScriptingEngine merge module (inside the product msi, not ISScript.Msi) or both.
Answered 07/31/2006 by: AngelD
Red Belt

Honestly if the application is Installshield and its using the ISS.msi file then the best bet you have is to convert it into a true MSI application.

Either import the project and correct the tables so the ISS.msi file is no longer required or you can because its not a true MSI file actually re-package it like you would any old exe install.

Then you will have a true MSI and you can set the keys for good self healing for a great per machine installation package.

Let me know if you need anything further regarding this, I can assist if you would like...
Answered 11/29/2006 by: Gechonet
Senior Yellow Belt

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ