JDK-4953793 : J2SDK 1.4.2_01, 1.4.2_02 fail to install (JVM currently running) on W2000 SP4
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 1.4.2
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2003-11-13
  • Updated: 2013-06-04
  • Resolved: 2004-02-03
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.
Other
5.0 b37Fixed
Related Reports
Duplicate :  
JDK-5104191 - Install Error on WIndows 2003 Server for non-standard home directory
Description

Name: gm110360			Date: 11/13/2003


FULL PRODUCT VERSION :
Can't give you this, because J2SDK versions 1_4_2_01 and 1_4_2_02 does not install on Windows 2000 SP4. Perhaps they do install on earlier Service Pack versions of Windows 2000; I cannot test this.

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows 2000 [Version 5.00.2195] SP4

EXTRA RELEVANT SYSTEM CONFIGURATION :
2 CPU (Pentium III) SMP machine

A DESCRIPTION OF THE PROBLEM :
 I am able to install the 1.4.2_02-b03 JRE package on Windows 2000 Pro (SP4).

However, the 1.4.2_02-b03 SDK package does not install: some way through the process (the file copy stage) a modal dialog is displayed:

"Warning - Java(TM) Update
---------------------------
Java(TM) Update (1.4.2_02-b03) cannot be installed on this machine because the Java(TM) Virtual Machine is currently running.

Please close all running Java(TM) applications, especially browsers.
---------------------------
Retry Cancel
---------------------------"

and when Cancel is clicked, the main MSI installer program displays an Error 1722 modal dialog ("A program failed to execute ...") and the main MSI program announces installation has failed, nothing has been installed, and so on.

No JVM is running.

The MSI log in the temp directory displays

"Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action patchsdk, location: C:\Program Files\Common Files\Java\Update\Base Images\j2sdk1.4.2-b28\patch-j2sdk1.4.2_02-b03\patchsdk.exe, command: -s "C:\Programs\Java\SDK\"
=== Logging stopped: 06/11/2003 23:53:02 ===
"

Examination of the installation directory (C:\Programs\Java\SDK in my case) shows that program files have been copied (and it looks complete), but the Java applet in the Control Panel does not show that the JRE in the SDK directory has been registered as a JRE choice (normally it is in the drop-down list of available JREs). The Windows registry has not be updated to show these choices.

So what can I do? Both 1.4.2_01 SDK and 1.4.2_02 SDK show this problem; 1.4.2 (FCS) does *not*. The problem also occurs with the IFTW installers.

Any solutions?

Some have suggested that I just try installing the SDK in the default path (C:\jdk_1.4.2_02), but I have that distaste for creating new root-level folders, I usually install programs in folders off c:\programs. Much neater.


STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
Download any one of j2sdk-1_4_2_01-windows-i586.exe, j2sdk-1_4_2_01-windows-i586-iftw.exe, j2sdk-1_4_2_02-windows-i586.exe, j2sdk-1_4_2_02-windows-i586-iftw.exe.

Execute one of these installation programs.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
J2SDK successful installation.
ACTUAL -
the 1.4.2_02-b03 SDK package does not install: some way through the process (the file copy stage) a modal dialog is displayed:

"Warning - Java(TM) Update
---------------------------
Java(TM) Update (1.4.2_02-b03) cannot be installed on this machine because the Java(TM) Virtual Machine is currently running.

Please close all running Java(TM) applications, especially browsers.
---------------------------
Retry Cancel
---------------------------"

and when Cancel is clicked, the main MSI installer program displays an Error 1722 modal dialog ("A program failed to execute blah blah...") and the main MSI program announces installation has failed, nothing has been installed, and so on.

No JVM is running.

The MSI log in the temp directory displays

"Error 1722.There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action patchsdk, location: C:\Program Files\Common Files\Java\Update\Base Images\j2sdk1.4.2-b28\patch-j2sdk1.4.2_02-b03\patchsdk.exe, command: -s "C:\Programs\Java\SDK\"
=== Logging stopped: 06/11/2003 23:53:02 ===
"

Examination of the installation directory (C:\Programs\Java\SDK in my case) shows that program files have been copied (and it looks complete), but the Java applet in the Control Panel does not show that the JRE in the SDK directory has been registered as a JRE choice (normally it is in the drop-down list of available JREs). The Windows registry has not be updated to show these choices.

So what can I do? Both 1.4.2_01 SDK and 1.4.2_02 SDK show this problem; 1.4.2 (FCS) does *not*. The problem also occurs with the IFTW installers.


ERROR MESSAGES/STACK TRACES THAT OCCUR :
See above

REPRODUCIBILITY :
This bug can be reproduced always.

CUSTOMER SUBMITTED WORKAROUND :
None found.
(Incident Review ID: 225487) 
======================================================================
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-b37 tiger-beta2
14-06-2004
SUGGESTED FIX Here is the new error message for the key in the ws: install/src/windows/patcher/PatchInstaller.rc IDS_ERROR_VM_RUNNING "Java Update cannot be installed on this\nmachine because the directory you have\nchosen to install is locked.\n\nPlease close any browser or application\nthat is using the directory you have\nchosen for installation." ###@###.### 2004-01-27
27-01-2004
EVALUATION Please retest the install using Java 1.4.2_02. We discovered a problem on our webserver and fixed it. Please confirm your install is now successful. ###@###.### 2003-11-19 I think the problem is that the user is installing into "C:\Programs\Java\SDK\" for both 1.4.2 and 1.4.2_01. My guess is that they installed 1.4.2 into that directory, and either had a dos-prompt open and the cwd was that directory or something else had it locked up. Then they tried to install 1.4.2_01 into the same directory. We will pop up that message because the patcher will fail if it cannot patch the target directory. We should either document that users should not install different jre/sdk releases over previously installed j2se releases, or we should stop them ahead of time when they are choosing the directory. ###@###.### 2003-11-25 We will give a better error message telling the user that there may be files or directories that are locked that aren't necessarily the JVM running. ###@###.### 2003-12-15 Committing to tiger-beta2. We been getting a lot of feedback about this. ###@###.### 2004-01-21 This is the error message we decided on: IDS_ERROR_VM_RUNNING "Java Update cannot be installed on this\nmachine because the directory you have\nchosen to install is locked.\n\nPlease close any browser or application\nthat is using the directory you have\nchosen for installation." ###@###.### 2004-01-27
27-01-2004
WORK AROUND Do not install into a directory that has the following characteristics: 1. Has other files or directories in it, or in it's sub-directories that are locked. 2. Is the same directory that the installer is running from. (The installer file would be a file that is locked, see #1) 3. Has had a previous installation of the same jre, that has left files behind and are still locked. 4. A commandline tool such as MSDOS is opened and the current working directory is a directory or subdirectory of the target installation directory. (This would lock the directory, see #1.) ###@###.### 2003-12-15
15-12-2003