32bit JRE 8u65 on 64bit Win7/8.1

Topics: Configuration Issue, Misc., Publishing Issue
Nov 4, 2015 at 5:40 PM
First attempt at using WPP, and I'm using the PDF from the web site (Installing Java 7u21 without Java Auto Updater) as a guide.

WPP is installed on our Server 2012R2 (WSUS 6.3) server.

Attempting per subject line, because it works better with the ADP payroll app.

Publishing works, but seeing error codes on clients of 80131700 (mostly) and 6BA and one or two others.

I'm using jre-8u65-windows-i586.exe from http://java.com.

Have tried varying the product code from 32bit to 64bit, and also processor arch, with very poor results - it's only worked once or twice on my test machines, out of about 10 attempts.

I also tried the MSI file using a standard package insted of a custom package with even worse results.

I'll be happy to provide any settings/configurations required to help troubleshoot this, as I'm sure I'm missing something, but just can't figure it out.

Thanks,

Kurt
Editor
Nov 5, 2015 at 12:36 PM
Nov 5, 2015 at 12:56 PM
Edited Nov 5, 2015 at 12:59 PM
kurtbuff wrote:
First attempt at using WPP, and I'm using the PDF from the web site (Installing Java 7u21 without Java Auto Updater) as a guide.
Yes, its al little bit outdated, but the basics are the same.
WPP is installed on our Server 2012R2 (WSUS 6.3) server.

Attempting per subject line, because it works better with the ADP payroll app.
hm
Publishing works, but seeing error codes on clients of 80131700 (mostly) and 6BA and one or two others.


I'm using jre-8u65-windows-i586.exe from http://java.com.
correct.
Have tried varying the product code from 32bit to 64bit, and also processor arch, with very poor results - it's only worked once or twice on my test machines, out of about 10 attempts.
Dont make modifications. I have the same configuration ( Server + WSUS ) , and it is not nessasary to manipulate or creating rules if you use the extracted .msi
I also tried the MSI file using a standard package insted of a custom package with even worse results.
Ok. You get the the same result with the simpe .msi and the custom .msi + .mst . So, it is a more basis installation problem
What is happen if you start the msi manual on the client. Runs correct without interaction?
I'll be happy to provide any settings/configurations required to help troubleshoot this, as I'm sure I'm missing something, but just can't figure it out.

Thanks,
Yes....
ok, first... If you test your deployment, be sure that clients are clean, without old Java Installations and a clean registry. You dont want to have trouble with old offline / online and modificated installations from Java 7 - today.

Second. Deployment of .msi is recommended, and a little bit more comfortable like .exe deployment, and give you the possibillity to make configurations for your installation and deinstallation.

There is a tutorial and more information on my site based on JAVA 8 and LUP, but its the same in WPP. Im sorry, only in german, but your Name is Kurt, hmmm :-)
for .msi :
http://road-books.jimdo.com/2014/12/01/verteilung-von-java-8-umstieg-von-java-7-mit-local-update-publisher/
for .exe ( not recommended ):
http://road-books.jimdo.com/2014/12/03/exe-verteilung-von-java-8-mit-local-update-publisher/
Kurt
If I understand correctly, it works for 1-2 Clients, so it isnt a WPP problem or publishing problem.


80131700 is ERROR_INSTALL_FAILURE , so Installation start and failed. Why? Hm.

good luck,

Dec 12, 2015 at 12:12 PM
I have recently been able to deploy Java 8 Update 65 with WSUS Package Publisher to Clients. It work prefectly.
This tutorial contains Step by Step deployment Guide with Screenshots. I hope it can help you.
http://www.sthshare.com/wordpress/how-to-deploy-java-to-clients-using-wsus-package-publisher.html