I am trying to distribute 32-bit Java to my 64-bit clients but it will not install through SCCM. I have tried putting it in the task sequence as well as "Run Advertised Programs" and it fails both ways. When I look at the ConfigMgr Status Message for the advertisement I get the following error:

The program for advertisement "IHR200AB" failed ("IHR0008C" - "Java 6 Update 19 x86"). A failure exit code of 1619 was returned. User context: NT AUTHORITY\SYSTEM Possible cause: Systems Management Server (SMS) determines status for each program it executes. If SMS cannot find or correlate any installation status Management Information Format (MIF) files for the program, it uses the program's exit code to determine status. An exit code of 1619 is considered a failure.

I use an identical advertisement for the 64-bit version of Java and it will install with no problems. The 32-bit version will install fine if I run the install script without SCCM. Any Ideas?
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
1619 means that the package couldn't be opened. See here for details. Check that the permissions on the DP include those for your 64-bit clients' machine accounts, remembering that SCCM executes installs using the local System account.
Answered 04/07/2010 by: VBScab
Red Belt

Please log in to comment
0
I fixed the problem by extracting the MSI and it worked great using msiexec /i jre1.6.0_20.msi /qn.

Follow these steps to extract the .msi file from the Sun JRE installer for deployment through SCCM:
1. Download and launch the Sun JRE Windows Offline Installation executable (.exe) file.
2. Navigate to LocalAppData folder (the user's Application Data folder). The location of the LocalAppData folder differs for each Windows platform.

Windows Vista/Seven
C:\Users\</user>\AppData\LocalLow\Sun\Java\jre1.6.0_20\jre1.6.0_20.msi

Windows XP
C:\Documents and Settings\</user>\Local Settings\ApplicationData\Sun\Java\ jre1.6.0_20\jre1.6.0_20.msi</user>

3. From there, you can use SCCM to distribute the Java Runtime Environment msi file to as many client Windows platforms as you want.
Answered 04/21/2010 by: rjgaul
Senior Yellow Belt

Please log in to comment
0
The location of the LocalAppData folder differs for each Windows platformUse %APPDATA% to show the path, since that will resolve correctly on most recent platforms.
Answered 04/21/2010 by: VBScab
Red Belt

Please log in to comment
0
Use %APPDATA% to show the path, since that will resolve correctly on most recent platforms.

I too prefer this guideline.
Answered 04/25/2010 by: plus2plus
Senior Yellow Belt

Please log in to comment
0
I'm also plagued by this error... If i go the MSI route:
-Do I need all the files that are created in the temp directory?
-How do I set the options usually done via the command line e.g. /s REBOOT=Suppress IEXPLORER=1 MOZILLA=1 JAVAUPDATE=0 JU=0 AUTOUPDATECHECK=0 SYSTRAY=0
-Are there any other command line options people are using?
-Does the MSI still uninstall previous versions of Java?

Cheers!
Answered 10/10/2010 by: NoDowt
Senior Yellow Belt

Please log in to comment
-1
- No, just the MSI
- Via a transform
- \_ Have you read the Package KB for JRE, or the myriad other posts about it?
- / There can't be too much more to say about it that doesn't already appear in one or both of those places.
Answered 10/11/2010 by: VBScab
Red Belt

Please log in to comment
1
Found out the reason for this 1619 error when using the exe installer on a 64Bit machine...

On 64-bit hosts installing the exe doesn't work. jre-6u17-windows-i586.exe is a 32bit app containing a msi, a cab and some other files. On a 32-bit host it unpacks in in c:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_17\. On a 64-bit host it unpacks in c:\Windows\SysWOW64\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_17\. The silent install on a 64-bit host is still looking for the msi in the *System32* directory.


It seems the reason it works when running manually is that it gets extracted to the users AppData folder, which doesn't change based on 32/64bit. Stupid Java exe installer...

Interesting to note that on this page - http://www.oracle.com/technetwork/java/javase/silent-136552.html it doesn't list the various autoupdate options anymore...
Answered 10/11/2010 by: NoDowt
Senior Yellow Belt

  • THANKS A LOT :)
    Tried with the msi, it worked without a problem !
Please log in to comment
0
I got the same error.  I'm running this as a script.  I changed the script to run as the logged in user and it worked fine.


Answered 11/14/2014 by: rcubed
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity