InstallAware

My platform: IAx13/Win 10 H202

On one dev machine, I am suddenly getting the error, 1603/"Fatal error during installation" on one dev machine, when calling: Install/Remove MSI Package $PRODUCTCODE$[REMOVE=ALL] (get result into variable REMOVEOLD) to remove my previous installation or trying to remove through the OS add/remove programs.

Inside the log file ( attached), I see the following error messages:

====
...
MSI (s) (AC:00) [09:16:47:862]: Note: 1: 1725
MSI (s) (AC:00) [09:16:47:862]: Note: 1: 2205 2: 3: Error
MSI (s) (AC:00) [09:16:47:862]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1725
MSI (s) (AC:00) [09:16:47:862]: Note: 1: 2205 2: 3: Error
MSI (s) (AC:00) [09:16:47:862]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (AC:00) [09:16:47:862]: Product: MyoVision Software -- Removal failed.
...
MainEngineThread is returning 1603
===

Again, it seems to be something with this machine specifically that has changed as previously, it worked just fine.

What I have tried:
1) Manually removing the installation in the registry and reinstalling, and then uninstalling as above. Same result.
2) Removing the %TEMP% files. Same error condition.

Any ideas what to try next?

Please have a look at the following threads.
https://www.installaware.com/forums/viewtopic.php?f=2&t=11283&hilit=1603
https://www.installaware.com/forums/viewtopic.php?f=2&t=10980&hilit=1603

Hope this helps you.

Hi,
Thanks for the quick response. Unfortunately, while your two links touch on the issue I am having, they do not specifically apply to my situation.

In my case, my installation is always set to All Users. Further, prior to just recently, it worked fine on my dev machine and, it has always worked on other machines. That is why I feel it is something that changed, or hung around, during my debugging install/uninstall of my installations.

Any further suggestions? Does the log file help?

Most of the case (if not all), error code 1603 indicates that a file or a component is being held in use by another process. Due of this, I suggest you to verify if your installer is trying to install/uninstall "something" which seems to be currently in use.

Unfortunately often in such cases, the Windows Installer log doesn't indicate which component is causing the issue.

Hope this helps you.

Hi Francesco
OK. Your narrowing the variables down to the most likely root cause being a component sharing issue gives me a place to start.

Have a good weekend.

Michael