hristo_kacarov Outstanding Contributor.
Outstanding Contributor.

<QC/ALM Support Tip> ALM12.00 installation fails on Suse Linux Enterprise 11

Dear Customers,


When installing ALM 12 on Suse Linux Enterprise (SLES) 11 an error message is thrown at the final "Deployment" step which causes the installation to fail. The error can be seen below:


The installation failed

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file/..../ application/20qcbin.war/
SLF4J: Found binding in [jar:file:/..../application/20qcbin.war/
SLF4J: See for an
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Configuration failed
Failed to create/upgrade Site Admin Schema. By default, the output is saved in
<ALM repository path>\sa\DomsInfo
\MaintenanceData\out on your ALM server machine.:


ALM's Installation log shows the following error: <machine name>
    at Method)
     wrapped in


The issue is caused by the fact that ALM checks OS's hosts file for mapping IP. If server's IP is not present then the error occurs. Therefore in order t solve the issue you should modify /etc/hosts by adding a new line:

" <your-machine-ip> <your-machine-name> localhost "

Aftre performing the above change a reboot of the server might be required.

Note: This information can be found in this KB article:



Labels (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.