CA Embedded Entitlements Manager installation fails during CA Directory installation and configuration phase.

Document ID : KB000008775
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:


CA Embedded Entitlements Manager installation fails during CA Directory installation/configuration phase with the following error logged in the /tmp/eiam-install.log file.

 

20 Sep 2017 03:08:42 FATAL ConfigureCADirectoryAction - CA Directory configuration failed
java.io.IOException: Command [dxmodify -a -c -H ldap://<CAEEM-Server-FQDN>:509 -f "C:\Users\<user>\AppData\Local\Temp\481569.tmp\setup\cadir\itechpoz.ldif"] failed with error code [1]
    at com.ca.eiam.common.dsa.DXServer.runDxTools(DXServer.java:295)
    at com.ca.eiam.common.dsa.DXServer.modify(DXServer.java:259)
    at com.ca.eiam.installer.customcodeaction.ConfigureCADirectoryAction.install(ConfigureCADirectoryAction.java:162)
    at com.zerog.ia.installer.actions.CustomAction.installSelf(Unknown Source)
    at com.zerog.ia.installer.InstallablePiece.install(Unknown Source)
    at com.zerog.ia.installer.InstallablePiece.install(Unknown Source)
    at com.zerog.ia.installer.InstallablePiece.install(Unknown Source)
    at com.zerog.ia.installer.GhostDirectory.install(Unknown Source)
    at com.zerog.ia.installer.InstallablePiece.install(Unknown Source)
    at com.zerog.ia.installer.Installer.install(Unknown Source)
    at com.zerog.ia.installer.LifeCycleManager.consoleInstallMain(Unknown Source)
    at com.zerog.ia.installer.LifeCycleManager.executeApplication(Unknown Source)
    at com.zerog.ia.installer.Main.main(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at com.zerog.lax.LAX.launch(Unknown Source)
    at com.zerog.lax.LAX.main(Unknown Source)

Environment:
CA Embedded Entitlements Manager r12.51+ on all supported platforms.
Cause:

The EEM installer retrieves the fully qualified domain name (FQDN) of the system/host machine using the Java method getCanonicalHostName() of the java.net.InetAddress class. Hence, the FQDN of the EEM host should be resolvable.

Resolution:

Please ensure the EEM host server's FQDN is resolvable. The ping command should work with the FQDN.

You may have to add the FQDN in the hosts file (On Windows: %SYSTEMROOT%\System32\drivers\etc\hosts, On Linux/UNIX: /etc/hosts) of the server if the FQDN is not registered in the Domain Name Server (DNS).

Additional Information: