I sent the Java 6u29 fixlet to 40+ machines. All reported “executed successfully” but on 10 it uninstalled the previous version and didn’t install the new one. In the summary is an exit code 1603.
For those with the exit code 1603: Action script - first 12 items - ‘completed’, 13th item - failed, 14th item - nothing reported.
I wouldn’t mind if it reported as failed and I would know to resend but this reporting as successful when it isn’t is a real nuisance. Plus it’s a problem for my users when they go to open a site that needs Java and it doesn’t work, which makes it an emergency install for me.
questions
why does this happen?
is there a way to export the action to include the exit code?
Although the installation of jre fails the action completes successfully (with an exit code 1603). The next item is to check whether or not the specific version of jre has been installed on the system or not. If not the “InstallingJava” key is not deleted from the registry. This registry check in the relevance clause causes the fixlet to report as fixed although jre is not installed. This means that the system is in a corrupt state with respect to jre installation. We use this method to trigger the corrupt fixlet for the corresponding jre fixlet.
However in your case it seems that this method would also fail since the previous version of jre is uninstalled without installing the current version which would make both the normal and corrupt fixlets non-relevant on the system.
Could you try running the action script command:
waithidden __Download/jre-6u29-windows-i586.exe /s /norestart /L
{name of drive of system folder
}\jreSetup.log
in he action tab of fixlet debugger on one of the affected system to see what exactly is causing the installation to fail? The above command will create a detailed log of jre installation in the “C:\jreSetup.log” file.