Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

New JRE7u55 (Upgrade) packages

Anyone else having a problem with the new JRE7u55 (Upgrade) packages? They came down from Solar Winds yesterday and I went to test them on my VMs today. I approved the packages to my test group and on both my XP VM and Win7 VM the updates showed up, I installed them successfully but they are still being advertised as needed. Even rebooted both and rescanned and they still showed as needed but I can see it is installed on both and tested it on Oracle's site.

If I try to install it a second time the package fails since it is already installed. Possibly a mistake in the detection logic for the package? I haven't analyzed the package yet to see if there is a problem.

I've upgraded both of these VMs to JRE7u51 using the Patch Manager packages in the past without any issues. But 7u55 is not cooperating.

Think I found the problem in the package. The package is looking for java.dll v7.0.550.14 but the java.dll in the JRE7u55 I'm downloading from Oracle is v7.0.550.13. I just downloaded them again from Oracle to make sure and they were still v7.0.550.13. I modified my packages to look for v7.0.550.13, republished and then ran update scans from my XP and Win7 VMs and the needed update disappeared. Now I'm a happy camper! :-)

Find more posts tagged with

Accepted answers

LGarvin

This is a known condition when the JRE installer is obtained from an incorrect location.

The Package Download Assistant has a built-in link to obtain the installer from the Oracle Technology Network.

http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html

and that's the binary that the package was tested with.

If you obtain the binary from JAVA.COM ... you'll get a binary with a different File Version number (and possibly also different functionality), and among other things, the Installed Rule will fail in the supplied packages because the build number is not correct.

There are, functionally, two ways to resolve this scenario:

1. You can uninstall the JRE7u55 package that used the wrong binary. Expire the package on the WSUS server. Run detections on all affected clients so they see the expiration, and then DELETE that package from the WSUS server. Download the correct binary from OTN and republish the JRE7u55 packages with the correct binary file.

2. Customize the existing JRE7u55 package (Do NOT create a duplicate package in this instance; a duplicate package will confuse it even further.) to test for the 7.0.550.13 build number in the JAVA.DLL and RE-publish that package as a revision. Force all clients to run detections, which will get them the updated metadata, and subsequently report that package as "Installed". However, note at this point you still have an incorrect JRE7u55 package deployed, which may or may not also have undesirable functionality. (The packages at JAVA.COM are designed for Single-User Consumer implementations.) Once clients have reported the package as "Installed", RE-publish the JRE7u55 packages with the correct binaries (the metadata will automatically correct at the next catalog sync event with SolarWinds). Approve the corrected JRE7u55 package and deploy the correct JRE7u55 binaries.

All comments

LGarvin

This is a known condition when the JRE installer is obtained from an incorrect location.

The Package Download Assistant has a built-in link to obtain the installer from the Oracle Technology Network.

http://www.oracle.com/technetwork/java/javase/downloads/jre7-downloads-1880261.html

and that's the binary that the package was tested with.

There are, functionally, two ways to resolve this scenario:

stcain

Okay, my bad. Followed your Step 1 and got everything back to the way it should be. Tested both my VMs and everything works fine.

Thanks Lawrence, have a great weekend!

LGarvin

Additional Information -- for those reading this after the fact.

Sometime yesterday (Mon Apr 21), Oracle 'updated' the contents of the binaries contained on the Oracle Technology Network JavaDownloads page... and didn't tell anybody. It's not the first time they've done this; it likely won't be the last.

As a result, several additional customers who correctly downloaded the binaries from the OTN then experienced this same behavior, because now they had the v7.0.550.13 JAVA.DLL.

The packages in the catalog have been updated as of 9:20am this morning. Please perform a manual synchronization to obtain the updated package, expire/delete the previously published packages, and republish the package with today's revision date, which will contain the correct metadata logic to test for the v7.0.550.13 JAVA.DLL file.

debs

I followed your instructions, expired the original package , downloaded the new package, and published it. Java appears to install successfully, but the Windows Update continues to pop up and show that JRE7u55 still is needed.

Any suggestions?