Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

CustomAction <action_name> returned actual error code 1603 in installshield

I'm using using Basic MSI to install my application.

I'm getting Error 1001 during installation and roll back action takes place. I've noticed in the installation log that I get this error:

"CustomAction returned actual error code 1603. Action ended InstallFinalize. Return value 3.

Custom Action dll is a .NET Installer Class and the property is set to True.

Does anyone have an idea what could be the problem?

like image 483
Vimal Avatar asked Aug 03 '11 16:08

Vimal


People also ask

How do I fix error code 1603?

Option 1: Restart your system and uninstall old versions Once you see the 1603 error, restart your system. Download and install the offline installer package. When prompted, choose Save in the download dialog box, and save the download package in a convenient place (e.g. save on the desktop).

What is installation error 1603?

Background: Error 1603 is a general Windows error that means the Sync installer failed to run. Next steps: Ensure you are running the Sync installer as an Admin User in Windows: Right-click the Sync installer and select Run as Administrator.

What is MSI error 1603?

You may receive this error message if any one of the following conditions is true: Windows Installer is attempting to install an app that is already installed on your PC. The folder that you are trying to install the Windows Installer package to is encrypted.


3 Answers

Your installation project includes a component with .NET Installer Class set to Yes. Using this option is an anti-pattern, as it can result in modal UI even in silent installations, and often tells you only "Error 1001". You can either look for the component with this setting, or take a verbose log and look for information shortly before the first or only return value 3.

like image 52
Michael Urman Avatar answered Oct 03 '22 21:10

Michael Urman


Error code 1603 is a Windows installer's generic error code when custom action throws any error/exception. Windows installer does not show actual error/exception in installer logs. To verify actual error/exception we have to debug the custom action.

Please verify if custom action is throwing any error/exception.

like image 24
Bhalchandra K Avatar answered Oct 03 '22 21:10

Bhalchandra K


A verified solution:

Error 1001 is due to a .Net framework mismatch. InstallShield uses RegAsm.exe and InstallUtilLib.dll to compile the installer, and these must match your application's target framework, and the target computer must also have it:

Error 1001 reason and solution discussed here

enter image description here

Open Installshield IDE -> Go to Tools menu -> Options and check the following settings as shown in the above screenshot:

like image 42
Munawar Avatar answered Oct 03 '22 22:10

Munawar