Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-7003660

Fully unattended silent installation hangs with a proxy credential prompt

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: P3 P3
    • None
    • 6u22
    • install
    • x86
    • windows_7

      FULL PRODUCT VERSION :
      java version "1.6.0_22"
      Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
      Java HotSpot(TM) Client VM (build 17.1-b03, mixed mode, sharing)

      ADDITIONAL OS VERSION INFORMATION :
      Windows 7 x64 Enterprise
      Windows Vista x86 Enterprise
      Windows Server 2008 R2

      EXTRA RELEVANT SYSTEM CONFIGURATION :
      Both 32-bit and 64-bit versions of JRE are doing this.


      A DESCRIPTION OF THE PROBLEM :
      The Windows Installer installation of JRE 6u22 is hanging on some systems when run in fully unattended mode because a custom action (RegUtils.dll) in the MSI installation package is prompting for proxy credentials in session 0.

      The Java installation is being triggered by a software distribution tool with with the following commandline:

      %SystemRoot%\System32\MsiExec.exe /i "C:\Temp\JRE\x86\jre1.6.0_22.msi" /qn /l* C:\Build\Logs\JRE6u22.log REBOOT=ReallySuppress JAVAUPDATE=0 IEXPLORE=1 MOZILLA=0 JU=0 WEBSTARTICON=0 EULA=0 AUTOUPDATECHECK=0 ALLUSERS=1 SYSTRAY=0

      Note that /qn above means COMPLETELY SILENT installation.

      If a debugger is attached to the hung msiexec process, it's apparent that
      the Java dll called RegUtils.dll is calling the function InternetErrorDlg in WinInet.dll (http://msdn.microsoft.com/en-us/library/aa384694(v=VS.85).aspx)

      This behaviour is inappropriate firstly because the installation is supposed to be running complete silently. Secondly, it appears that the Java installer is attempting to go out to the Internet when updates have expressly been disabled with AUTOUPDATECHECK=0 and JAVAUPDATE=0

      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      See above for the commandline, which is executed in the SYSTEM context by Microsoft SCCM.

      EXPECTED VERSUS ACTUAL BEHAVIOR :
      EXPECTED -
      A silent MSI installation must now throw any dialog boxes
      The installation must not attempt to check for updates when the autoupdate mechanism is expressly disabled.
      ACTUAL -
      A custom action in the installation throw a hidden dialog box in the SYSTEM context prompting for credentials. Debug dumps of MsiExec.exe process are available.

      ERROR MESSAGES/STACK TRACES THAT OCCUR :
      None - the installation just hangs because the dialog box is in session 0 where it's not visible.

      REPRODUCIBILITY :
      This bug can be reproduced often.

            billyh William Harnois
            webbuggrp Webbug Group
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: