Adam Ruth
asked this on November 13, 2009 13:18
We are currently testing Admin Arsenal trial version and running tests in our environment for purchasing consideration. I receive an MSI Installer Error 1603 when I attempt to push an installation. As we monitor the progress of the installation, it starts with "copy install" then proceeds to "install". After 12 seconds, an error 1603 is returned.
The MSI is created with Advanced Installer 5.1.1 and is also a trial version. To isolate whether is was a bad MSI, we also tried to push source .exe without repackaging as an MSI. The reason for repackaing to an MSI is due to custom registry tweaks that we have to make to run the application. The source exe is what we use to manually install on desktops, so we know it's not a problem with the exe. However, when we attempt to push the exe through Admin Arsenal (on one desktop only) the job status progresses to "Installing..." but it has been over 17 hrs. and the job has not completed. We had to abort the task. Needless to say, the installation of the exe and msi did not go through.
What are your suggestions?
Comments
Error 1603 is a generic error, which usually is related to custom actions. If you run the MSI again with full logging and post the log, we should be able to track where it's dying. Use "/l*v c:\log.txt" in the other options to generate a full (and very detailed) log.
I was able to resolve this error by adding the serial number to the "ISX_SERIALNUMBER=