Jump to content

Recommended Posts

Posted
Anyone having trouble deploying this via GPO. Done the usual things - installed java - found the msi and cab file then fired out by GPO. Only problem is that clients just hang on installation. Tried on more than one server with the same results. Nothing in event viewer. Is this just a bad release or is there something I'm missing.
Posted
Hi, yep I noticed this, it sat on the installer for a good 15 mins but it did finish and worked fine so didn't think much more of it.
Posted

kmount - haven't tried that yet.

torry loon - I'm installing from GPO. Never had to that before, but always open to ideas.

mossj - just install java on a computer and then search for the .msi - in different places depending on the OS. Make sure you copy the whole folder as later versions have a .cab file that needs to be with the .msi

Posted
kmount - haven't tried that yet.

 

Might be worth a go, also, with your GPO assignment are you telling it to upgrade an existing policy (with/without removal?) or just bumping it out over the top.

Posted
I usually take off the old policy (without uninstalling the previous version) and create a new one. I just wonder if I need to wait a bit longer. I'll try it on a machine next week and leave it for as long as possible to see if it eventually gets there.
Posted
Are there multiple Java versions in Add/Remove programs or multiple folders in the Program Files/Java directory? You may need to remove these first.

 

I'm not sure it would matter, my test box has U11, & 14 together.

 

I can imagine this only becoming a problem when you look in IE's plugin list it shows each version separately.

Posted
I usually take off the old policy (without uninstalling the previous version) and create a new one. I just wonder if I need to wait a bit longer. I'll try it on a machine next week and leave it for as long as possible to see if it eventually gets there.

 

It'd be worth trying that, but also trying to install it with msiexec/manually to see if it gives any reason for why it might fail.

 

When doing the previous version did you customise the MSI in any way? - Might be worth trying to uninstall it to see if it has a dodgy file removal issue.

Posted

Might not help but is it waiting for user input? Like a "Do you want to uninstall previous versions" or "Do you want a Yahoo toolbar". Sorry if you've already sorted those in the .msi just a thought.

 

I've had problems with U14 making web sites hang I'm thinking that it might be waiting for something but haven't yet worked out what.

Posted
Do you stop the 'Java Quick Starter' service before upgrading Java? Installation fails if it is still running.

 

This.

 

Error: 25099 during Java installation

 

The javaqs.exe file is in the Windows\system32 folder, so when a new version installs, it needs to be overwritten, unlike many of the Java files which can be installed side by side. If the service is running, it can't overwrite and the installer hangs. My experience is that when upgrading from 11 or 12, the service doesn't stop automatically during a GPO install and the installer throws a modal message box that you have to click on to dismiss... only you can't because message boxes don't appear during GPO deployment. In short, Sun's Java MSI not only has flawed logic but doesn't even conform to Windows Installer specification. I've even seen the service left behind if you uninstall the previous Java version first.

 

I think this is fixed from U13 onwards. My method for dealing with hung installs was to use pskill to remotely terminate javaqs.exe and then remotely delete the file. On the next reboot the U13 installer should run without incident.

  • Thanks 2
Posted
This.

The javaqs.exe file is in the Windows\system32 folder, so when a new version installs, it needs to be overwritten, unlike many of the Java files which can be installed side by side. If the service is running, it can't overwrite and the installer hangs. My experience is that when upgrading from 11 or 12, the service doesn't stop automatically during a GPO install and the installer throws a modal message box that you have to click on to dismiss... only you can't because message boxes don't appear during GPO deployment. In short, Sun's Java MSI not only has flawed logic but doesn't even conform to Windows Installer specification. I've even seen the service left behind if you uninstall the previous Java version first.

 

I think this is fixed from U13 onwards. My method for dealing with hung installs was to use pskill to remotely terminate javaqs.exe and then remotely delete the file. On the next reboot the U13 installer should run without incident.

 

Good find, didn't know about that, cheers.

Posted

There shouldn't be any problems installing Java 6 Update 14 over any other version. It'll just list both in Add/Remove Programs, but of course IE for example will use the latest files of Java.

 

Checking the event logs on the machines should give a clue as to why it's hanging. I'm not sure why it's happening as when I install it manually it has worked first time everytime. It could be permissions related on the distribution share, but I would have to agree, it's most likely a service or component on the workstation which is causing the installer to hang.

Posted
Might it be worth having a startup script that checks for the service that stops it and changes it to manual?

 

Good idea, and you don't even need a script; you can set it to Manual startup in Group Policy under Computer Configuration > Windows Settings > Security Settings > System Services.

  • Thanks 1
Posted
Didn't have much time on site to try this but sent out update 14 to a test station which had update 12 - hung. Uninstalled java completely from another test station and update 14 installed. I think Angry Technician is right regarding the service. Thanks again everyone.
  • 2 months later...
Posted
I wish I'd seen this thread before yesterday! I removed Java 6 Update 11 from GP on Thursday night and added Java 6 Update 16. When all the Curriculum PCs turned on approx 8am yesterday they basically locked up trying to uninstall. Many of the slower PCs took nearly 2 hours to "timeout/fail" and get to the login screen, and even then they ran incredibly slow, and if the PC was rebooted the whole saga began again. After the JavaQuickStarterService was disabled (i ran a recursive script using sc.exe to disable it on every PC) and the PCs rebooted they uninstalled the old, installed the new, and worked perfectly normally. Methinks I'll set it to manual in GP as per AngryTech's post in case future versions have the same bug...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...