2 Replies Latest reply on Oct 29, 2015 6:47 AM by Steve Cupp

    BL Package external command using "start wait"

    Steve Cupp

      In a BL package, we are using an external command to execute the following command:

      start /wait msiexec /P "101480.1\XA650W2K8R2X64R04.msp" /quiet /qn /norestart /lv %systemdrive%\log\XA65R04.log

      sometimes this installer will fail with a 1603 error for whatever reason. That 1603 error is shown in the log generated by the installer but does not appear to be passed through to the external command, since the job run log shows it completed successfully.


      I'm wondering if this is caused by the use of "start wait" to execute the msiexec or if something else is keeping the 1603 from being passed thru to the external command and failing the job.


      Thanks for the help.