Version/Environment (if relevant):
This applies to installation of the Domino CLI on Mac OS
Issue:
Attempting to install the CLI, after downloading the .dmg then clicking the Domino Installer.app, the "Install4j Wizard" screen hangs:
Root Cause:
Initially there were no errors, but additional actions (see Notes below) led us to logs. A problem between Java, Install4j, and the MacOS was occurring with an error:
Caused by: java.lang.NoClassDefFoundError: com.install4j.runtime.beans.screens.SystemFormScreen
This error was part of a stacktrace involving java.awt and com.install4j.runtime.installer.frontend.GUIHelper.invokeOnEDT -- both indicators of a graphical user interface (GUI) problem.
Resolution:
To evade the error in components outside of Domino's code we installed via console-based / commandline, bypassing a GUI. From within the mounted dmg containing the installer .app, we opened a commandline and ran ./Domino\ Installer.app/Contents/MacOS/JavaApplicationStub -c
, this prompted for the laptop's admin name/password and then proceeded with the console-based install.
Notes:
To find logs containing errors we needed to set an environment variable prior to running the "Domino Installer.app". From commandline run:
launchctl setenv INSTALL4J_LOG=yes
Then run the .app in that same terminal, like:
~/Downloads/Domino\ Installer.app
Look for logging in ~/Downloads/install4jError.log and the MacOS system log by starting the "Console" application which is located in/Applications/Utilities
Comments
0 comments
Please sign in to leave a comment.