Upgrading seems to have a reasonably high success rate, but the way we deploy some of our java applications via Zenworks is by running the java. Re-download the update again from another computer, extract MSI, and use those files.same issue.īeen having a sort of similar problem with 6u20. So I thought, alright, skip SMS, let's try to push it out via AD. Try it one more time, it will be successful. After it breaks, and I try again.MAY break. If they have update 20, and I push update 20 again, it'll break. Now, here's how I can almost duplicate it. So here I am thinking it was a good deployment. My problem is that if it fails.everything reports back as successful. Installs fine.or breaks.Ĭase 2, machines have 1.6.0_18, installing _20. Not sure what it is.Ĭase 1, machines have different versions of 1.6.0_x. Java 6_20, SMS is reporting back high successful rate, but the more I dig into it.seems that my success rate may only be about 50-60%. That's fine, I'll just send a remote reboot and try again. Java 6_18 was pretty much a good 80-90% successful rate. Yeah, I pretty much just deploy it via SMS to all Windows XP clients. But it's hard for me to find out why since it's happening on random machines, but all reporting successful. Is it looking for the MST file? It's in the same folder as the rest of the setup files.ĭo I need to call for the MST within the command-line? And still though, the installation is not failing on all, just random. That usually means MSI is looking for a file, but can't find it. Reviewing the log.I'm seeing a bunch of -2147287038 errors. Looks like it was in the middle of installing, when it came down to extracting, it failed out, and just spit out Successful. SMS and Event log shows successful installation. I can post up the log.but it's 570kb worth of plain text, so that's quite a bit. Read the log, and I'm not sure what to be looking for since the log shows that the installation was successful. Pushed the following to my machine via SMS I was just able to duplicate the issue on my test workstation. \\smsshare\JAVA6_u20\jre-6u20-windows-i586-s.exe /s AgreeToLicense=YES IEXPLORER=1 MOZILLA=1 REBOOT=Suppress JAVAUPDATE=0 In the past, I had a manual script that did: Here is my command-line for the installation: \\smsshare\jre-6u20-windows-i586-s.exe /s AgreeToLicense=YES IEXPLORER=1 MOZILLA=1 REBOOT=Suppress JAVAUPDATE=0 I'm upgrading 1000+ users, and I don't know who else may be experiencing this. Only issue, I'm doing this via SMS, so I can't just stop what I'm doing to take care of 1 issue. Appears a fix for this is to uninstall and reinstall the application. SMS and Application Event Logs show that the install was successful. Registry has an entry that can be uninstalled. Add/Remove shows that it's an item that can be uninstalled. The bin and lib folders are pretty much empty. The installation appears to have been successful within SMS, but if you navigate to C:\Program Files\Java\jre6\ almost all the files are gone. I'm in the process of upgrading people from JAVA 1.6.0_18 to 1.6.0_20 and experiencing installation issues via SMS 2003.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |