Why does Exit Code 1603 did not show Failed Status

1

Hi All,

I keep seeing deployment status show “Completed” on some of the clearly failed installs.
In this case, Exit Code 1603 is a Fatal Error. Because BigFix is showing “Completed” status, the retry on failure didn’t take place.
This issue is not limited to exit code 1603, but a few others. exit code 1 …etc.

Thanks.

2

BigFix has a number of different configurable methods that can be used to determine success or failure for a given action. Typically, if you’re seeing a ‘Completed’ status, that simply means that all lines of the actionscript were executed successfully (this is not an indication that for instance a binary that the actionscript executed successfully performed its work). This is different than a scenario where the action status might return ‘Fixed’, where typically that would indicate that the original relevance conditions have actually been addressed (i.e. applicability relevance evaluates to False).

For the scenario you describe above, there are at least 2 different approaches to consider:

  1. Assuming your applicability relevance properly returns True/False based on the existence of an issue, you can set the success criteria to ‘the applicability relevance evaluates to false’.

  2. You can add an additional command at the end of your actionscript that checks the exit code, and fails out if not 0 (or some other similar logic). An example of that might be something like:

    continue if {exit code of action = 0}

Here’s another potential approach as well: https://developer.bigfix.com/action-script/reference/flow-control/exit.html

Please see https://help.hcltechsw.com/bigfix/10.0/platform/Platform/Console/Dialogs/success_criteria_tab.html for more details.