Problems with deployment - Java 7.0.25 to 7.0.45 - interaktive Services
Hello,
i have problems with the deploy of Java.
We have installed 7.0.25 and i will install a update 7.0.45 as administrator
The bundles are correctly
I use Zenworks 11
when the msi would like to install, the old version is uninstalled.
I cant uninstalled the version 7.0.25. -> Installer.dll is missing
The users will get a notification - Detection of interactive services - and the message is missing installer.dll
Here's what I've tried:
Install java 7.0.25 again. Fail
Uninstall with msiexec. Fail
Uninstall with msi. Fail
Sorry for my bad english :(
Can you help me?
Thanks
Answers (3)
I've seen this error before when manually attempting to update Java, so I believe that the problem is likely with Java rather than with your Kace distribution package.
On one of the computers that you are seeing this error on, navigate to C:\Program Files\Java\... Try to access the JRE folders located here and see if you recieve any form of error when opening them (such as a permissions error). This indicates that the workstation needs to reboot prior to the installation of the new version.
This has only happened to us on a handful of our workstations, but likely what is happening is that an open browser may be preventing the old Java client from fully uninstalling during the update process. Rebooting should complete the uninstallation process and allow the update to proceed normally.
We had this exact same problem. It seemed that older versions were not uninstalling fully. Our solution was to take a two pronged approach. First, we created an uninstall script that uninstalled all versions of java and then rebooted the machine. The reboot made the difference in clearing out any .dll files the machine was hanging on to. Here's the uninstall script:
@echo off
start /wait MsiExec.exe /X{26A24AE4-039D-4CA4-87B4-2F83217011FF} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150000} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150010} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150020} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150030} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150040} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150050} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150060} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150070} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150080} /qn
start /wait msiexec.exe /x {3248F0A8-6813-11D6-A77B-00B0D0150090} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216010FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216011FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216012FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216013FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216014FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216015FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216016FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216017FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216018FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216019FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216020FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216021FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216022FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216023FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216024FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216025FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216026FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216027FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216028FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216029FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216030FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216031FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216032FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216033FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216035FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216036FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216037FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216038FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216039FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216040FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216041FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216042FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216043FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216044FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83216045FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217001FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217002FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217003FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217004FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217005FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217006FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217007FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217008FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217009FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217010FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217011FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217017FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217021FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217025FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217040FF} /qn
start /wait MsiExec.exe /X {26A24AE4-039D-4CA4-87B4-2F83217045FF} /qn
start /wait MsiExec.exe /X {32A3A4F4-B792-11D6-A78A-00B0D0170400} /qn
start /wait MsiExec.exe /X {32A3A4F4-B792-11D6-A78A-00B0D0170170} /qn
start /wait MsiExec.exe /X {32A3A4F4-B792-11D6-A78A-00B0D0170110} /qn
Once we verified that java had been uninstalled on the machine(s), we added the machine(s) to a managed install of the latest version of java. This worked very well.
I hope to get patching set up which would make this process obsolete, but in the meantime it works very well.
I`ve used this uninstall script with great succes.
@ECHOOFF START /WAIT /MIN WMIC product where "Name LIKE '%%J2SE Runtime%%'" call uninstall /nointeractive START /WAIT /MIN WMIC product where "Name LIKE '%%Java%%'" call uninstall /nointeractive exit 0
Comments:
-
We actually tried that one also, but I think it would need to be in a vbs script or something. When we pasted it directly into Kace's batch script editor the quotes would get changed when it ran and it would always fail. I'm sure there's a way around that, but we went with the surefire uninstall command for every java ever... well, almost. - lmland 10 years ago
-
We are running SCCM 2012 and i ran my commands with a .bat file. The problem i have with the other script above is if someone downloads and install a new version you will have to add another line to your script....everytime. - KevinViolette 10 years ago
-
Yeah, I understand that issue which is why I mentioned using patching solution to manage Java in the future. If you're not using KACE then your script probably works like a charm. We just ran into issues using it in Kace's environment. - lmland 10 years ago
