Software Deployment Question

Help with MSI 1603

01/23/2004 342170 views
Help with MSI (Microsoft Installer) error 1603: A fatal error occurred during installation.
0 Comments   [ + ] Show comments


Community Chosen Answer

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.
See InstallShield KB Article Q107182
See AppDeploy MSI FAQ
Answered 01/23/2004 by: AppDeploy.com
Red Belt

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

All Answers

While using NetInstall 5.8: I encountered error 1603 while trying to push Litronic NetSign CAC, which is a software package for reading smartcards. By using the verbose logging feature for MSI, I was able to determine that the installer was looking for the netsignconfig.ini file, but was reporting that the file does not exist, which resulted in the install failure. I was able to create the INI file by using the nsconfigwizard.exe which comes with the NetSign software. By reading the Litronic KB and making some educated guesses, I wrote a script that copies the INI file to the "%windir%\temp" folder, and then calls the necessary MSI. This resolved the error.
Answered 04/12/2006 by: al_depansieu
Yellow Belt

This was for a mass remote MS patch update installation with Altiris. Status "Error 1603 during script execution". The rights were fine. The XPSP2 PC had IE 7 , the update was for IE 6. Lame error code, thanks for nothing Microsoft! It should have said, "Error: No condition items exist." Cool Web Site!
Answered 05/24/2006 by: davidemcmurray
Yellow Belt

If your installation has a LaunchCondition defined and executed, and if it fails the LaunchCondition, the MainEngineThread will return a 1603. Look in your verbose log for info following "Action start HH:MM:SS: LaunchConditions"
Answered 11/01/2006 by: williamp
Orange Belt

I received this error while pushing out an msi through altiris deployment solution 6.8. Turns out the msi, which was created by Wise Package manager, required .NET Framework 2.0 or higher. Issue resolved after installing the updated .NET Framework.
Answered 01/31/2008 by: smpmet
Yellow Belt

Received Error 1603 deploying UGS NX 5 msi via Altiris Deployment Solution. Needed to run ISSCRIPT10.msi prior to UGS NX 5.0.msi to get it to install.
Answered 02/06/2008 by: smpmet
Yellow Belt

I encountered error 1603 on some workstations while attempting to deploy AutoCAD 2012 via SCCM. AutoCAD logs on the distribution share showed .NET 4.0 was not found on the workstations, and needed to be installed.
Answered 05/08/2011 by: trevor.piggott
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