CRoberts
CRoberts

Reputation: 326

MSI Installer Error - MSIExec failed: 1603

I am trying to install a Windows Service on a server and when running command line, as admin, and navigating to my InstalUtil.cmd file, and running it, I get error "msiexec failed: 1603", however the service does get installed and runs perfectly as expected. Any ideas/suggestions to fix the error message?

Upvotes: 3

Views: 23215

Answers (2)

Stein Åsmul
Stein Åsmul

Reputation: 42126

Reboot Required?: could this be a simple "reboot required issue". 1603 can mean "reboot required" in batch files.

  • Did you run the batch file with admin rights?
  • Does this MSI have any custom actions? If so, where are they located in the InstallExecuteSequence?
  • There are other possibilities (resurrected from WayBack Machine). Inlining the main section here for the future:

From link above: The following is a non-exhaustive list of known causes for this error:

  • Short file name creation is disabled on the target machine.
  • An Install Script custom action is prototyped incorrectly.
  • A file is locked and cannot be overwritten.
  • The Microsoft Windows Installer Service is not installed correctly.
  • The Windows Temp folders are full.
  • The setup was corrupted after installation and, therefore, fails with this error during un-installation.
  • An older version of Install Shield Developer is being used.
  • A general error occurred during the installation.
  • Print and File sharing is not installed or enabled when installing MSDE 2000.

Proposed solutions in linked document above: 1) Make sure short file name creation is enabled on the target machine, 2) Make sure Windows Installer is properly installed, 3) Empty all temporary folders, 4) Close all running applications and utilities, and launch the installation again - especially antivirus tools, and 5) a couple more options.

You need to gather more information - which leads to checking for logs:

Standard debugging:

  • Event Logs: What does the event logs say? (Windows + Tap R. type eventvwr and press OK). Check the different logs.

  • MSI Log File: Did you create an MSI log file?

  • There could be policies in effect to automatically create one. Check in the TMP folder, sort by date and check recent files for any *.log files.

  • Also check in the batch file if it hard codes a location for the MSI log file.

If you find an MSI log file, try searching for "value 3" (without the quotes) to find any actions that failed.


How to create an MSI log file:

Upvotes: 6

X zheng
X zheng

Reputation: 1971

While installing on windows sometimes get 1603 error because Visual C++ RunTime Library and Microsoft .Net problems.

Try reinstall Microsoft Visual studio redistributable package or uninstall original installed versions.

Upvotes: 0

Related Questions