ALM 12 installation on SLES 11 fails.

  • KM00972946
  • 05-Jun-2014
  • 20-Jun-2014


This article describes the root cause for ALM12 installation failure on SLES 11.


When installing Application Lifecycle Management (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 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


ALM checks OS's hosts file for mapping IP. If server's IP is not present the error occurs.


Modify /etc/hosts by adding a new line

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

Rebooting the server might be required.

Note: It is important that ALM is uninstalled properly once the installation has failed. All available data from ALM Deployment and Installation folders should be removed prior starting the new installation.