/build/static/layout/Breadcrumb_cap_w.png

Problems installing jre-6u30-windows-i586.exe on a Windows 7 x64 system

When I try to install jre-6u30-windows-i586.exe on a Windows 7 x64 system using the NT Authority\System account, I get a 1619 error ( http://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx) returned to the starting process.  I've run the installation using SCCM and using PSEXEC -S and both ways return the same errors. 

Command line used: jre-6u30-windows-i586.exe /s /v "/qn /norestart /lvx C:\temp\JRE630.log ADDLOCAL=ALL IEXPLORER=1  REBOOT=Suppress JAVAUPDATE=0 INSTALLDIR=\c:\Program Files (x86)\Java\jre6\"  SOURCEDIR=\"C:\temp\AppData\LocalLow\Sun\Java\jre1.6.0_30\""

When I enable verbose logging I see the following:

=== Verbose logging started: 5/16/2012  21:09:52  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\Windows\SysWOW64\msiexec.exe ===
MSI (c) (D0:A4) [21:09:52:691]: Resetting cached policy values
MSI (c) (D0:A4) [21:09:52:691]: Machine policy value 'Debug' is 0
MSI (c) (D0:A4) [21:09:52:691]: ******* RunEngine:
           ******* Product: C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_30\jre1.6.0_30.msi          ******* CommandLine: **********
MSI (c) (D0:A4) [21:09:52:691]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (D0:A4) [21:09:52:691]: Grabbed execution mutex.
MSI (c) (D0:A4) [21:09:52:706]: Cloaking enabled.
MSI (c) (D0:A4) [21:09:52:706]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (D0:A4) [21:09:52:722]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (38:04) [21:09:52:722]: Running installation inside multi-package transaction C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_30\jre1.6.0_30.msi
MSI (s) (38:04) [21:09:52:722]: Grabbed execution mutex.
MSI (s) (38:64) [21:09:52:737]: Resetting cached policy values
MSI (s) (38:64) [21:09:52:737]: Machine policy value 'Debug' is 0
MSI (s) (38:64) [21:09:52:737]: ******* RunEngine:
           ******* Product: C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_30\jre1.6.0_30.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (38:64) [21:09:52:737]: Note: 1: 2203 2: C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_30\jre1.6.0_30.msi 3: -2147287037
MSI (s) (38:64) [21:09:52:737]: MainEngineThread is returning 3
MSI (s) (38:04) [21:09:52:737]: User policy value 'DisableRollback' is 0
MSI (s) (38:04) [21:09:52:737]: Machine policy value 'DisableRollback' is 0
MSI (s) (38:04) [21:09:52:737]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (38:04) [21:09:52:737]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (38:04) [21:09:52:737]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (38:04) [21:09:52:737]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (38:04) [21:09:52:737]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (38:04) [21:09:52:737]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (s) (38:04) [21:09:52:737]: Restoring environment variables
MSI (c) (D0:A4) [21:09:52:737]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (D0:A4) [21:09:52:737]: MainEngineThread is returning 3
=== Verbose logging stopped: 5/16/2012  21:09:52 ===

 

This looks like it is attempting to extract the MSI to "C:\Windows\system32\config\systemprofile\AppData\LocalLow\Sun\Java\jre1.6.0_30" but it is not able to extra the MSI from the executable so the installation fails.  Is there any way to get this to work?

 

Thanks in advance,

Keith


0 Comments   [ + ] Show comments

Answers (3)

Posted by: piyushnasa 12 years ago
Red Belt
1

Why don't you exdtract the MSI and then customize it with a transform and then install it?

Posted by: mazessj 12 years ago
Blue Belt
0

The following parameters are not necessary and some of them may in fact be screwing things up:

ADDLOCAL=ALL IEXPLORER=1  REBOOT=Suppress INSTALLDIR=\c:\Program Files (x86)\Java\jre6\"  SOURCEDIR=\"C:\temp\AppData\LocalLow\Sun\Java\jre1.6.0_30\"

ADDLOCAL is superfluous since all features are installed by default. Specifying browser support is redundant as long as the browsers are present beforehand; the installer autodetects. INSTALLDIR specification is not necessary as JRE already knows where it belongs. SOURCEDIR is not a standard parameter here (not in any JRE deployment guide I've read); I have no idea why you're specifying it. Also, JRE is not likely to extract to that path. Additionally, I don't think you need escape characters (\) when executing from SCCM.

Posted by: sothpaw 12 years ago
White Belt
0

Here's what I found to be the easiest way to install every version of Java whether it's the x86 or x64 versions.  

1. Download the offline file from Java.com

2. Run the jre-7u4-windows-i586.exe (or any past versions)

3. once installed, go to this folder locatoin: C:\Users\your_username\AppData\LocalLow\Sun\Java

4. if you have installed the both x86 & x64 versions, there will be a folder for each version (jre1.7.0.04 for the x86 jre1.7.0_04_x64) go into each folder and there should be a MSI file that you can then move into SCCM with the proper switches.

5. If you are not seeing these files please remember to go into the folder options to put a dot next to "Show hidden files, folders, and drives"

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ