We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

Dietrich
Posts: 2
Joined: Mon Jun 03, 2013 3:15 pm

Return codes

Hello,

I'm currently evaluating your product for possible future use within our organization. Most scenarios are easily solved with this software although I cannot seem to find any information on the problem I have below.

I've received an MSI from our devs which installs an Outlook add-in. I've made some small adjustments to it using the Advanced Installer MSI editor. I've added 2 prerequisites; Acrobat reader & Outlook 2010 should be installed. Also added a check to see if Outlook is running or not (custom action). All these checks give a messagebox with appropriate feedback if one of them fails.

This all works great when running the MSI manually although when I try to push it through our deployment system with /qr as parameter not all the checks are displayed on the screen. The custom action to see if Outlook is running is not displayed and a generic 1603 error is returned to the deployment system.

Can I set the return code to something else than 1603 when my custom action check fails?
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Return codes

Hello and welcome to Advanced Installer forums,

Thank you for your interest in Advanced Installer.

I'm afraid I don't fully understand your scenario. Can you please give us more details about your scenario (maybe exemplify)? Also, can you send us the .AIP (project file) and a verbose log of the installation launched with reduced UI to support at advancedinstaller dot com so we can investigate them?

Please keep in mind that custom actions must return a value of 0 for success. The installer interprets any other return value as failure. Also, in order to continue with the installation even the custom action returns a value other then 0, you can uncheck the “Fails installation if custom action returns an error” option from “Custom Actions” page (by default it is checked).

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Dietrich
Posts: 2
Joined: Mon Jun 03, 2013 3:15 pm

Re: Return codes

Dan,

Thanks for your reply. I'll try to simplify with a basic scenario:

I have an MSI that checks if a process is running or not. If it is running the check should normally display a message on the screen and fail the installation. Although when I run it through our deployment system this check runs in the background but the message (which is a custom launch condition) is never displayed because it is being run silently.

The only feedback as to why the package failed to execute is a 1603 code, which is a fatal error. If an IT worker would deploy this package he would not know that the package is failing to run because the outlook is currently active.

In our deployment system we can catch unknown exit codes and attach a string value to it (example: Outlook is running, close it before pushing this application).

So I was wondering if it's possible to set an own exit code if the outlook check fails or are there other ways to do this? I'm fairly new to packaging so I might be going at this at a very wrong way, any advice is appreciated.

Kind regards,
Dietrich.
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Return codes

Hello Dietrich,

Please keep in mind that the 1603 error code is a generic error value returned by the installation process. In order to see what fails during the installation project you should search for return values of the standard and custom actions of the installation process. When an action fails in the log file it will be written a return value of 3.

If your installation package fails due to a launch condition, then in the log file you will see that "LaunchConditions" action (which evaluates the launch conditions) will have a return value of 3. Also, the description message of your launch condition it is written in the log file just before the line containing the "LaunchConditions" action return value.

If you have any questions let us know.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Building Installers”