Previous Topic: Cannot Log Into CA EEM Server with a Custom Created User EiamAdmin

Next Topic: Error Using Kerberos Authentication

Delegation Policies

Symptom:

When I delete or disable users who have delegated permissions (using delegation policies) to other users, I find that the delegated permissions remain effective.

Solution:

You must explicitly delete the delegation policies created by the deleted or disabled user.

Error in Custom Installation

Valid on Windows

Symptom:

When I install CA Directory and iTechnology in a customized location, I receive the following error:

Error Executing Specified program

Solution:

You may receive this error due to the restriction on the InstallShield command length.

On a computer with Microsoft Windows XP or Windows Server 2003, the maximum length of the string that you can use at the command prompt is 8,191 characters. With Microsoft Windows 2000, the maximum length of the string that you can use at the command prompt is 2,047 characters.

To avoid this error, use the cmdfile parameter:

EEMServer_[releasenumber].[builddate]_win32.exe -s -a /s /f1"location of response file" /z"cmdfile=location of cmdfile "

Example:

EEMServer_8.4.0.55_win32.exe -s -a /s /f1"c:\resp.iss" /z"cmdfile=c:\cmd.txt "

Important! For the cmdfile parameter, enter a single space character only before the end quotes.

The cmdfile contains the custom installation paths for CA Directory and iGateway as shown in the following example:

etdirpath=Custom installation path for CA Directory;igpath=Custom installation path for iGateway;

Error in CA EEM Server Installation

Valid on HP-UX

Symptom:

When I Install CA EEM Server, I receive a message 'One or more installation sanity tests failed' and the installation fails.

Solution:

You receive this error if the swlist binary file is not accessible. The swlist binary file is used to check for HP-UX patches.

To avoid this, update the PATH environment variable with the folder containing the swlist binary file using the export command. For example:

export PATH=/usr/sbin/:$PATH

After updating the path, restart the installation.

Error Using CA EEM Java SDK

Symptom:

When I use the CA EEM Java SDK on a computer with Tomcat 4.1, I receive the following browser error:

HTTP 404 Error

In the Tomcat log, I see the following exception:

org.apache.commons.logging.LogConfigurationException: Invalid class loader hierarchy. You have more than one version of 'org.apache.commons.logging.Log' visible, which is not allowed.

Solution:

To use the CA EEM Java SDK on a computer with Tomcat 4.1, do the following:

  1. Stop Tomcat Server.
  2. Delete the commons-logging-api.jar and commons-logging.jar files from the webapps/application_name/WEB-INF/lib/ directory.
  3. Restart Tomcat Server.