JDK-4975888 : Could not lauch java control panel - fatal exception
  • Type: Bug
  • Component: docs
  • Sub-Component: guides
  • Affected Version: 5.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2004-01-09
  • Updated: 2007-01-15
  • Resolved: 2004-03-19
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.
5.0 beta2Fixed
Build tested: j2re1.5- build 31 and build 32
OS tested:    XP-Home/ XP-Pro/ win 2000 pro/ ME

Steps to reproduce:
1) Install j2re1.5-b32 onto the test system
2) Un-install j2re1.5-b32 from the test system
3) Install j2re1.5-b31 onto the test system

At this point, the test system shoud have j2re1.5-b31. Doing the java -version / java -fullversion should indicate so

Problem: Can not lauch the java control panel
either through Start --> Settings --> Control Panel (click on Java icon)
or execute C:\Program files\Java\J2re1.5.0\bin\javacpl.exe

Error Message: Java Virtual Machine Launcher
               Could not find the main class. Program will exit

Also, when trying to remove j2re1.5-b31 from the system (via Add/Remove program)
the fatal exception orrurred

Error Message:
Java Virtual Machine Launcher
Fatal exception occurred. Program will exit

Java(TM) WebStart1.5.0-beta
Bad installation. Error invoking Java VM (execv)
C:\\Program Files\Java\j2re1.5.0\bin\javaw.exe

Please fix it as this is a very common problem for users as build 31 is available from earlyAccess site.

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-beta2

PUBLIC COMMENTS A note has now been added to the jre installation instructions and to the release notes. ###@###.### 2004-03-18

EVALUATION This is a known backwards compatibility issue. Some of the properties in deployment.properties file have been changed between builds 32 and 31. The bug is reproducible only if you install b32 or later, then uninstall it, and then install b31 or older(before b31). External customers do not have access to build 32 and should not run into this compatibility problem. The problem has been fixed in the latest builds. In order to workaround the problem, please delete "deployment.properties" file - see the "Work Around" section of this bug for futher instructions. This bug will not be fixed. ###@###.### 2004-01-09 I believe this should be documented in the installation instructions and release notes, which are web docs that do not reside in the doc bundle. ###@###.### 2004-01-27 A note has now been added to the jre installation instructions and to the release notes. ###@###.### 2004-03-18

WORK AROUND The workaround is to delete deployment.properties file in "Documents and Settings"\<user name>\Application Data\Sun\Java\Deployment directory. ###@###.### 2004-01-09