What is the 3rd party software you were installing?
That looks like an MSIExec standard exit code, but that is only true if you were installing something using an MSI or using an EXE that uses an MSI under the hood.
To further restate what @FatScottishGuy is saying, these exit codes do not come from BigFix, they are just reported by BigFix from whatever you ran with BigFix. BigFix itself does not technically have exit codes for it’s run/wait commands. The only exception is if there is a error invoking the executable referenced by the run/wait command, in which case the exit code actually comes from the process creation API from the operating system which is being used by BigFix. This happens if you give it a bad path or if the path is not readable.
See here for MSI Exit Code 1603: https://support.microsoft.com/en-us/topic/ccfda1f5-4601-0cbc-07b2-9ecc93f009be
I am just now realizing that @Jalimanchi didn’t even specify this was on windows, if it was not windows, then I have even less of a clue, I just assumed it was Windows because exit code 1603 is a common MSI exit code.
I need a lot more context to answer this question any more, like what the actionscript was, what the app being installed is, etc…
