Job Queue Exit Code 1602

[areynolds1]

I am trying to install software via a Job Queue. I have used this Job Queue to deploy the same software to different hosts. Today when i went to deploy it i received this back from the log:

11/18 10:57:29> Job Queue: Sending email notification. Previous action failed with exit code: 1602
11/18 10:57:28> Job Queue: Initiating ‘If previous action failed/errored (returned non-0), send email notification’
11/18 10:57:28> Deployment: Exit Code: 1602

When I look at the application log on the host I see that it installed:

Event Log
EventID: 1033
EventType: Information
Source: MsiInstaller
User: xxxxx
Computer: xxxxx
TimeLogged: 11/18/2020 10:57:27 AM
EventMessage: Windows Installer installed the product. Product Name: PI API 2018 Patch 1 for Windows Integrated Security (64-bit). Product Version: 2.0.3.48. Product Language: 1033. Manufacturer: OSIsoft, LLC. Installation success or error status: 0.

EventID: 1033
EventType: Information
Source: MsiInstaller
User: xxxxx
Computer: xxxxx
TimeLogged: 11/18/2020 10:57:27 AM
EventMessage: Windows Installer installed the product. Product Name: PI API 2018 Patch 1 for Windows Integrated Security (32-bit). Product Version: 2.0.3.48. Product Language: 1033. Manufacturer: OSIsoft, LLC. Installation success or error status: 0.

The software is not being listed when I use BatchPatch to pull what applications are installed.

Thanks

Aaron

[doug]

1602 is returned by the MSI installer. It’s not a BatchPatch error per se. BatchPach just passes through the MSI return code to you.

MSI 1602 exit code means “User cancelled installation.” My best guess is that you have something, perhaps anti-virus software or similar, that is killing the installation. You might be able to get more info by adding the following to your parameters in the deployment.

/log c:\msi_installer_log.txt

See screenshot for illustration/example:

Alternatively you might be able to get more info by running the msiexec command at the cmd prompt manually on a target machine instead of through BatchPatch. So for example if you put the MSI file directly on the target computer and then you ran this command:

msiexec.exe /i "C:\someFolder\someInstaller.msi" /q

You should see it output more detail to the cmd prompt that might help you figure out what is happening.

[Author]

Posts