tracker issue : CF-4126629

select a category, or use search below
(searches all categories and all time range)
Title:

Installation of API Manager Add-on fails on 32-bit Windows 7, giving JVM error

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): A. Bakia / A. Bakia (A. Bakia)

Created: 03/09/2016

Components: API Manager

Versions: 2016

Failure Type: Unspecified

Found In Build/Fixed In Build: Alpha_v12 /

Priority/Frequency: Major / Unknown

Locale/System: English / Win All

Vote Count: 0

Duplicate ID:	CF-4056159

Problem Description: I am on 32-bit Windows 7. I updated my JDK to version 1.8.0_60. When I double-click on the installer to launch it, I get a Windows error prompt saying, "Windows error 2 occurred while loading the Java VM". 

Steps to Reproduce: Set the JAVA_HOME environment variable to point to C:\Program Files\Java\jdk1.8.0_60. Double-click on the installer, ApiManager_Alpha_091515_Addon_win.exe, to launch it.

Actual Result: LaunchAnywhere error prompt saying, "Windows error 2 occurred while loading the Java VM". 

Expected Result: Error-free installation of API Manager Add-on

Any Workarounds: None known.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	4126629

External Customer Info:
External Company: (withheld for privacy)
External Customer Name: A. Bakia
External Customer Email: A.BAKIG@CHELLO.NL
External Test Config:

Attachments:

Comments:

Adding BUG AUDIT TRAIL ********action: updated fieldName: Status newValue: Fixed oldValue: ToTest oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-10-15 10:40:32.0 action: updated fieldName: Closed By newValue: nitikum oldValue: Blank oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-10-15 10:40:32.0 action: updated fieldName: Date Fixed newValue: 2015-10-15 03:40:32.0 oldValue: Blank oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-10-15 10:40:32.0 action: updated fieldName: Fixed By newValue: nitikum oldValue: Blank oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-10-15 10:40:32.0 action: updated fieldName: Date Closed newValue: 2015-10-15 03:40:32.0 oldValue: Blank oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-10-15 10:40:32.0 action: updated fieldName: Reason newValue: Blank oldValue: Duplicate oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-10-15 10:40:32.0 action: updated fieldName: State newValue: Closed oldValue: Open oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-10-15 10:40:32.0 action: updated fieldName: Owner newValue: Blank oldValue: nitikum oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-10-15 10:40:32.0 action: updated fieldName: Fix By Product Milestone newValue: Beta oldValue: Blank oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-10-09 10:17:21.0 action: updated fieldName: Fix By Milestone newValue: Beta oldValue: Blank oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-10-09 10:17:21.0 action: updated fieldName: Owner newValue: nitikum oldValue: djha oprid: djha recordName: RQ_DEFECT timpestamp: 2015-10-05 12:23:36.0 action: updated fieldName: Duplicate Bug ID newValue: CF-4056159 oldValue: Blank oprid: djha recordName: RQ_DEFECT timpestamp: 2015-10-05 12:23:36.0 action: updated fieldName: Reason newValue: Duplicate oldValue: MustFix oprid: djha recordName: RQ_DEFECT timpestamp: 2015-10-05 12:23:36.0 action: updated fieldName: Status newValue: ToTest oldValue: ToFix oprid: djha recordName: RQ_DEFECT timpestamp: 2015-10-05 12:23:36.0 action: updated fieldName: Priority newValue: 3 oldValue: 0 oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-09-28 10:32:11.0 action: updated fieldName: Owner newValue: djha oldValue: nitikum oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-09-28 10:32:11.0 action: updated fieldName: Status newValue: ToFix oldValue: Unverified oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-09-28 10:32:11.0 action: updated fieldName: Reason newValue: MustFix oldValue: Blank oprid: nitikum recordName: RQ_DEFECT timpestamp: 2015-09-28 10:32:11.0 action: updated fieldName: Owner newValue: nitikum oldValue: inoel oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-09-28 06:52:49.0 action: updated fieldName: QE Assigned newValue: nitikum oldValue: inoel oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-09-28 06:52:49.0 action: updated fieldName: Dev Assigned newValue: djha oldValue: awdhesh oprid: vmannebo recordName: RQ_DEFECT timpestamp: 2015-09-28 06:52:49.0
Comment by CFwatson U.
3684 | March 09, 2016 04:19:38 AM GMT
Added By: PreRelease User User Name:A. Bakia Note Added: Please read 'launch' in place of 'lauch' Date Added :2015-09-24 15:40:55.0 Added By: PreRelease User User Name:A. Bakia Note Added: Found a workaround! Phew! I had already added %JAVA_HOME%\bin (that is, C:\Program Files\Java\jdk1.8.0_60\bin) to the system PATH environment variable. I now decided to add the JRE bin directory (namely, C:\Program Files\Java\jdk1.8.0_60\jre\bin) to the PATH variable. In other words, I replaced %JAVA_HOME%\bin in the PATH variable with %JAVA_HOME%\bin;%JAVA_HOME%\jre\bin. It worked! I could lauch the installer, ApiManager_Alpha_091515_Addon_win.exe, without any problems. You might want to add this information to the official documentation on installation on Windows. Date Added :2015-09-24 15:39:38.0 Added By: PreRelease User User Name:A. Bakia Note Added: Entered Bug. Date Added :2015-09-21 14:32:05.0
Comment by CFwatson U.
3685 | March 09, 2016 04:19:39 AM GMT