JDK-6659450 : JDK install fails with Error 1723 caused by missing getlogfile
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 6u10
  • Priority: P1
  • Status: Closed
  • Resolution: Fixed
  • OS: windows
  • CPU: x86
  • Submitted: 2008-02-05
  • Updated: 2010-09-17
  • Resolved: 2008-02-20
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6 JDK 7
6u10 b12Fixed 7Fixed
Related Reports
Relates :  
Relates :  
Description
Rakesh's comment

clean_3 fails due to installation issue, MSI file shows some error..

MSI (s) (0C:FC) [04:23:16:671]: Running as a service.
MSI (s) (0C:FC) [04:23:16:671]: Hello, I'm your 32bit Elevated custom action server.
MSI (s) (0C:A8) [04:23:16:718]: Closing MSIHANDLE (46) of type 790536 for thread 3340
MSI (s) (0C:0C) [04:23:16:734]: Note: 1: 1723 2: getlogfile 3: MSIGetLogFileName 4: C:\Program Files\Java\jdk1.6.0_10\regutils.dll

http://oklahoma.east/automation_results/results/1.6.0_10/pit/6.0-Install_windows_i586-2008-02-05-05-58-49-0464/tester.Windows_XP.x86/clean_3/clean_3.PNG
http://oklahoma.east/automation_results/results/1.6.0_10/pit/6.0-Install_windows_i586-2008-02-05-05-58-49-0464/tester.Windows_XP.x86/clean_3/logs/MSI1F66B_57296.log

Comments
SUGGESTED FIX The cause of the problem is that MSIGetLogFileName is no longer exported by RegUtils.dll. Previously (e.g. 6u4), LOGFILE was not being set by MSIGetLogFileName() because a deferred custom action cannot set an MSI property. The custom actions have been resolving to "[bin]\unpack200.exe" -r -v -l "" "[INSTALLDIR]\jre\lib\jsse.pack" "[INSTALLDIR]\jre\lib\jsse.jar" with the log output being lost. This change does not changed the output being lost. CR 6657295 will have to. My change is to get rid of the getlogfile custom action from the JDK install and the call to the non-existing, previously non-functioning, MSIGetLogFileName, which cause the Error 1723. CR 6647280 removed MSIGetLogFileName from RegUtils.dll because the deferred custom action cannot set an MSI property such as LOGFILE. CR 6657295 exists to fix logging of zipper.exe and unpack200.exe in the JDK install. webrev: http://sa.sfbay.sun.com/projects/deployment_data/6u10/6659450.0 testcase: http://oklahoma.east/deployment/www/tests/1.6.0_10/6659450/6659450.txt
06-02-2008

EVALUATION My regutils.dll change for 6647280 broke the JDK install. The fix is to remove calls to getlogfile (that did not work anyway) from the jdk InstallExecuteSequence. 6657295 will fix the actual logging.
06-02-2008