Hello All,

I am trying to install JRE 8.0_25, I have a batch file that I am pushing via SCCM as a deployment package and everytime it fails to install.  I have also tested to install this application as a Task Sequence and that seems to work fine.  I need to have it passed as a standard deployment also.  Please see the cmdline that I am using in batch file.

Msiexec /I "%~dp0x86\jre1.8.0_25.msi" TRANSFORMS="%~dp0x86\jre1.8.0_25_x86.mst" JAVAUPDATE=0 JU=0 AUTOUPDATECHECK=0 SYSTRAY=0 EULA=0 /QN /L*V %WINDIR%\Temp\jre1.8.0_25_x86_Install.log

Error in log file is 1602,1603,1633.  These are the errors that were logged into log files on different machines that I have tested this.
 
I have tried installing it manually and it works flawleslly.

Any feed will be greatly appreciated.

Thanks,
AK
Answer Summary:
Cancel
3 Comments   [ + ] Show Comments

Comments

  • If you have an MST, why would you then configure public properties on the command line? Put them in the transform. Why use a batch file when SCCM can handle the MSI command line directly?
    • // Why use a batch file //
      I commonly deploy a command file with my SCCM jobs. It enables me (and others) to run the same command that the system would if I have to troubleshoot an installation issue.

      I too wondered what all that junk was doing outside the transform! ;-)
  • Agreed, initially. But I have noticed that not all those properties were applied to the package, so just to make sure I have also provided them on cmdline. Secondly, batch file is the way that our environment has decided to work with.
  • Ok, so with the further investigation I was able to see the error that was causing this install to fail, and it reads:
    "There is a problem with this Windows Installer package. A program required for this install to complete could not be run."

    So what puzzles me then is that why does the same install runs when I right click and run it as as admin?
Please log in to comment

Community Chosen Answer

1
Thanks for all your feedback looks like that answer was in the cmdline.  Switches that I was passing were being written into config file that was not present.  Once that was fixed now this works great.  Once again thank you all.

AK
Answered 03/16/2015 by: 786_ak
Second Degree Green Belt

Please log in to comment

Answers

0

1602 - user cancelled
1603 - a generic "something went wrong" error
1633 - This installation package is not supported on this platform.

Are your target machines 32-bit or 64-bit

Here's a list of MSI error codes.

Answered 03/06/2015 by: VBScab
Red Belt

  • Thanks, but I know those error codes and also do have that list but still not sure what's the problem. I have looked into that but not quiet sure why this happens only on deployment and not with Task Sequence or Manual installs. Targets are 64-bit boxes, but on those I am installing both 32 & 64 bit jre. Previously, I never had issues with this but in this version it's different, as I mentioned above.
Please log in to comment
0
Did you see this post
http://www.adminarsenal.com/admin-arsenal-blog/beat-java-error-1603-when-deploying


Answered 03/06/2015 by: jagadeish
Red Belt

Please log in to comment
0
When troubleshooting a 1603 error, create the verbose log file as you are and scroll to the middle of the file.  You'll have to hunt around a bit, but you'll find entries that indicate the installation, a line or two indicating the actual problem which sets the 1603 code, then lines showing the removal of everything that was installed.  Not sure why they can't make 1603's easier than they are . . .
Answered 03/08/2015 by: vjaneczko
Seventh Degree Black Belt

  • Ok, so with the further investigation I was able to see the error that was causing this install to fail, and it reads: "There is a problem with this Windows Installer package. A program required for this install to complete could not be run." So what puzzles me then is that why does the same install runs when I right click and run it as an admin?

    Any thoughts?
Please log in to comment
0

Try this:

msiexec.exe /i "jre1.8.0_40.msi" AUTOUPDATECHECK=0 IEXPLORER=1 JAVAUPDATE=0 JU=0 MOZILLA=1 /qn Reboot=ReallySuppress /l*v %windir%\logs\Java_8_40x86.log

Edit the msi filename as I'm using the latest version. I originally had issues with Java 8. The secret is: Reboot=ReallySuppress

I believe the process is hanging on install and wont release unless that switch is there. Had no issues since adding the reboot switch.

Thanks

Answered 03/10/2015 by: davidthebourne
White Belt

  • This didn't work. Thanks anyways.
    • Does it work if you run my command line without the batch file and .mst file? Java is fragile enough as it is so I wouldn't try and double up on an mst and a batch file, as well as putting things in the command line. Try my command line as is and see if that works.
      • I just ran what you have suggested for a test on my command line, no batch file, no .mst.
      • Failing that what I did to work out what wasn't working for me was to pull it all back to the start. msiexex /I "jre1.8.0_40.msi" /l*v etc. see if that works. If it does start adding more of the switches in till it fails. And so on. That's how I got my command line. Of course if it doesn't run just the msi via a command line (admin rights) then download and extract the package again.
        Cheers
Please log in to comment
Answer this question or Comment on this question for clarity