Unable to start installation of sso agent update
Article ID: 74850
Updated On:
Products
CA Single Sign On Secure Proxy Server (SiteMinder)
AXIOMATICS POLICY SERVER
CA Single Sign On SOA Security Manager (SiteMinder)
CA Single Sign-On
Issue/Introduction
Unable to run installer.
Invocation of this Java Application has caused an ExceptionInInitializerError. This application will now exit. (LAX)
Installing in console mode returns error:
==================================
Installer User Interface Mode Not Supported
Unable to load and to prepare the installer in console or silent mode.
==================================
Invocation of this Java Application has caused an ExceptionInInitializerError. This application will now exit. (LAX)
<Please see attached file for image>
Installing in console mode returns error:
==================================
Installer User Interface Mode Not Supported
Unable to load and to prepare the installer in console or silent mode.
==================================
<Please see attached file for image>
Cause
This seems to be a problem with the default FONTs package (stix-fonts) comes with RHEL 7.4, which over-writes the Java default font.
Maybe you can refer and suggest the solution mentioned in the below link.
“Warning: Missing charsets in String to FontSet conversion Preparing to install…” and was able to workaround it by running export LC_ALL=C (example):
Maybe you can refer and suggest the solution mentioned in the below link.
“Warning: Missing charsets in String to FontSet conversion Preparing to install…” and was able to workaround it by running export LC_ALL=C (example):
Environment
Policy Server 12.52 on RHEL 7.4
Resolution
RHEL v7.4 (upgraded from v7.3 or fresh install) comes with package stix-fonts.
When this package is installed, the default font changed from Utopiato STIX So, java now default fonts are mapped to STIX, including thesans-seriffont family For whatever reason, the STIX fonts does not seem to play well with java (openjdk+ IBM JDK) and cause exceptions and bad calculated artefacts positionning when using java.awt, which is the case with JasperReports We ended creating a file name /etc/fonts/local.conf with this in order to force back Utopia as the default font, used by java..
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> <fontconfig> <alias> <family>serif</family> <prefer><family>Utopia</family></prefer>
</alias>
<alias>
<family>sans-serif</family>
<prefer><family>Utopia</family></prefer>
</alias>
<alias>
<family>monospace</family>
<prefer><family>Utopia</family></prefer>
</alias>
<alias>
<family>dialog</family>
<prefer><family>Utopia</family></prefer>
</alias>
<alias>
<family>dialoginput</family>
<prefer><family>Utopia</family></prefer>
</alias>
</fontconfig>
#######################################
When this package is installed, the default font changed from Utopiato STIX So, java now default fonts are mapped to STIX, including thesans-seriffont family For whatever reason, the STIX fonts does not seem to play well with java (openjdk+ IBM JDK) and cause exceptions and bad calculated artefacts positionning when using java.awt, which is the case with JasperReports We ended creating a file name /etc/fonts/local.conf with this in order to force back Utopia as the default font, used by java..
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'> <fontconfig> <alias> <family>serif</family> <prefer><family>Utopia</family></prefer>
</alias>
<alias>
<family>sans-serif</family>
<prefer><family>Utopia</family></prefer>
</alias>
<alias>
<family>monospace</family>
<prefer><family>Utopia</family></prefer>
</alias>
<alias>
<family>dialog</family>
<prefer><family>Utopia</family></prefer>
</alias>
<alias>
<family>dialoginput</family>
<prefer><family>Utopia</family></prefer>
</alias>
</fontconfig>
#######################################
Additional Information
Attachments
Feedback
Yes
No
Powered by
