cancel
Showing results for 
Search instead for 
Did you mean: 

?ERROR - JRE Source does not exist? on Mac OS X

?ERROR - JRE Source does not exist? on Mac OS X

Summary

The article talks about the 'JRE Source does not exist' error on Mac OS X.

Symptoms

The following error is seen in the installation log on Mac OS X:

Install Directory: /Applications/2013/jre
Status: SUCCESSFUL

Install JRE: /Applications/2013/jre
Status: ERROR
Additional Notes: ERROR - JRE Source does not exist

Install JRE:
Status: SUCCESSFUL

Install Directory: /Applications/2013/
Status: SUCCESSFUL
Additional Notes: NOTE - Directory already existed

Cause

The above error is seen with a project that is bundled with a JVM and configured to install bundled JVM even when not installing a LaunchAnywhere. This setting is configured in the installer project, at Project>JVM Settings>Installer Settings>Bundled/Downloaded Virtual Machine. In this setting, if the checkbox ?Only when installing a LaunchAnywhere? is not checked (as shown below), the error is written to the installation log on Mac OS X. However, the JRE is installed successfully and there is not any issue with the actual installation of the product.

User-added image

Resolution

This issue was resolved in InstallAnywhere 2017. Please upgrade to take advantage of this fix.
The resolved Issue# IOA-000084658 is listed under the Resolved Issues section in the InstallAnywhere 2017 Release Notes.

Workaround

There are two workarounds (listed as A and B below) to this issue that an installer developer can use depending on the installer use case:

A) If the project is configured to install a LaunchAnywhere
1) Enable the above ?Only when installing a LaunchAnywhere? checkbox to resolve the error in the log.

B) If the project is not configured to install a LaunchAnywhere
1) Enable the above ?Only when installing a LaunchAnywhere? checkbox.
2) Add a dummy LaunchAnywhere launcher to the installation phase by clicking on the ?Add Launcher? button in the Install sequence of the project.
3) Immediately after the launcher action, include an action to remove it.
4) The result is that the jre is installed and the end-user does not see the created dummy LaunchAnywhere.
Was this article helpful? Yes No
No ratings