Installation / Configuration Problems

This section describes installation and configuration-related problems.

Installation Problems

This section handles server or agent installation related problems.

Determining which Agents are Installed

Indication:

You are not sure which agents are installed on the different servers of a distributed DirX Identity domain.

Reason:

  • Complex changes in your configuration.

  • An agent in a distributed workflow does not run on the target machine.

Solution:

  • In the DirX Identity Manager Expert View, select Configuration → DirX Identity Servers.

  • In the relevant DirX Identity server object, click the Agents tab and check the installed agents.

  • Start an update installation on the machine where the problem occurs. Go to the step in the installation where the agents are selected. The installation step shows the agents that are installed on this machine.

  • Compare the installation list with the list in the DirX Identity server object.

  • If something differs, perform an update installation on the relevant server and select the correct agents.

Master Setup and JRE on 32-bit Windows

Indication:

Installing the JRE from installation medium on a Windows machine with 32-bit architecture does not work using the related master setup menu item.

Reason:

The menu item is supported for 64-bit architecture only.

Solution:

Use Windows Explorer in order to navigate into the subfolder Installation\Windows\Oracle of the installation medium, and then select the suitable JRE to be installed.

Windows Installation Complete but Errors Occurred (Read-Only Files)

Indication:

The product installation (upgrade or update installation) ends with the following message:

"The installation of Atos DirX Identity is complete, but some errors occurred during the install. Please see the installation log for details."

Sample installation log:

...
Summary
---------
Installation: Successful with errors.
... SUCCESSES
0 WARNINGS
... NONFATAL ERRORS
0 FATAL ERRORS
...
Install File:             D:\Program Files\DirX Identity\bin\libdirxapi.dll
                         Status: ERROR
                         Additional Notes: ERROR - Flexeraakt: Target file was read only or did not have write permissions and was not overwritten
...
Install File:             D:\Program Files\DirX Identity\bin\libdirxapi_md.dll
                         Status: ERROR
                         Additional Notes: ERROR - Flexeraakt: Target file was read only or did not have write permissions and was not overwritten
...
Install File:             D:\Programme\DirX Identity\bin\metacp.exe
                         Status: ERROR
                         Additional Notes: ERROR - Flexeraakt: Target file was read only or did not have write permissions and was not overwritten

Reason:

Some files were read-only and have not been overwritten. As a consequence, said files are not up-to-date in your installation.

Solution:

Review the installation log and search for the string ERROR (case-sensitive). If the number of errors is 15 or higher, inform DirX Identity technical support about the problem. If related errors can be fixed by removing the read-only flag from said files or by similar actions regarding access right flags perform the indicated actions. Repeat the installation.

Installation Complete but Errors Occurred (Other Reasons)

Indication:

The product installation ends with the following message:

"The installation of Atos DirX Identity is complete, but some errors occurred during the install. Please see the installation log for details."

Sample installation log:

...
Summary
---------
Installation: Successful with errors.
... SUCCESSES
0 WARNINGS
... NONFATAL ERRORS
0 FATAL ERRORS

Reason:

Errors occurred during installation.The installation log file provides details about the errors occurred.

Solution:

Review the installation log file and search for the string ERROR (case-sensitive).If the error reasons are obvious from the related error messages fix them.If the indicated problems resulted in failures regarding creating or updating files or folder repeat the installation.If the problem persists, inform DirX Identity technical support about the problem.

Configuration Problems

This section describes problems that occur during DirX Identity configuration and how to solve them.

Admin or Password Not OK

Indication:

The message Admin or password not ok is displayed when the Directory Administrator account is tested.

Reason 1:

  • (indication) the error occurs only on Windows Server machines where Active Directory is installed in parallel.

  • When Active Directory and the Meta Directory Server use the same port (389), the account test will go to the Active Directory and the indicated error message results.

Solution 1:

  • Reconfigure the LDAP server of the Meta Directory Server to another free port.

  • Try the DirX Identity configuration again with the new port value.

Reason 2:

The Directory Administrator account contains an umlaut.

Solution 2:

  • Change the LDAPConfiguration attributes LCCQ and LCCS to LATIN1:

    Run dirxcp

    Bind as admin via DAP and type the following commands

    modify /cp/CN=LDAPConfiguration -rem LCCQ –add LCCQ=LATIN1
    -modify* /cp/CN=LDAPConfiguration -rem LCCS –add LCCS=LATIN1

    where cp is the context prefix; for example o=pqr.

    If the message Attribute or attribute value doesn’t exist is displayed, do not use the –rem option in the commands

  • Configure DirX Identity

  • Change the LDAPConfiguration attributes LCCQ and LCCS to UTF-8:

    Run dirxcp

    Bind as admin via DAP and type the following commands

    modify /cp/CN=LDAPConfiguration -rem LCCQ –add LCCQ=UTF8
    modify /cp/CN=LDAPConfiguration -rem LCCS –add LCCS=UTF8

Bind Error during Schema Configuration

Indications:

  • The following error occurs during configuration of the DirX Identity schema:
    BIND '/dxmC=DirXmetahub/cn=admin' failed: 'Invalid parameter passed as an argument.'

  • The error happens only with DirX.

Reason:

metacp reports a problem (for example, duplicate attribute definitions in the DirX abbreviation files).

Solution:

  • You can obtain the specific error message if you start metacp with the same command by hand.

  • Check the stdout message and resolve the problem.

Creation of DirX Identity C++-based Service Fails

Indication:

  • The creation of the C++-based service fails during configuration.

  • The error occurs only on Windows servers.

Reason:

An open Services or Event Viewer window prevents the creation of the service.

Solution:

  • Close all Services and Event Viewer windows.

  • Configure the C++-based Server again.

Long lasting configuration

Indication:

The configuration lasts a long time (20 min and more).

Reason:

If the directory contains 100,000 entries and more, the installation of the configuration database requires a long time.

Solution:

Be patient until the configuration has finished.

Initial Configuration Loops

Indication:

The initial configuration loops.

Reason:

The environment variable DIRX_IDM_PDU_TRACE is set and the directory already contains configuration data (for example from a previous aborted configuration).

Solution:

Reset the variable and start the initial configuration again.

Configuration on Linux Virtualized on VMWare ESX

Indication:

When running the configuration or initial configuration on RedHat Linux ES 5, virtualized on VMware ESX, some input fields, like password and path for key store or trust store are read-only what blocks completion of the configuration.

Reason:

Software problem during initial creation of the relevant input fields.

Solution:

The solution depends on the related configuration step:

  • If you cannot enter a password in the step “Directory Server for Connectivity”, then click the input field for the port, then the input field for the password.

  • If you have selected SSL in the step “Java-based Server” and cannot enter a password here, first un-check “Use SSL”, then check it again.

  • If you cannot enter a trust store password in the step “Java-based Worker” first open the file-dialogue for “Trust Store File” and close it after suitable file selection.

Schema Setup Problems after Upgrading DirX

Indication:

DirX Identity does not start due to schema error problems indicated by the message unknown abbreviation.

Reason:

You have upgraded your old DirX installation to another DirX version.It was necessary to uninstall the old DirX version before installing the new one because the database of the new DirX version is incompatible with the old one.

DirX Identity uses project-specific abbreviation files (dirxabbr-ext*) that are copied to the DirX installation subdirectory $DIRX_INST_PATH/client/conf when performing DirX Identity configuration.When uninstalling a version, DirX removes all files from its installation directory $DIRX_INST_PATH.

Solution:

Copy all dirxabbr-ext* files from the directory $DIRX_METAHUB_INST_PATH/client/conf to the directory $DIRX_INST_PATH/client/conf or re-run the DirX Identity Configurator to ensure that the files are copied.

Schema Installation Problems

This section handles schema installation problems that occur during DirX Identity Server or DirX Identity Schema Extension parts.

Invalid Parameter Passed

Indication:

The configuration fails on a DirX directory server during the schema configuration procedure.The corresponding message during the first call of metacp is:

BIND '/dxmC=DirXmetahub/cn=admin' failed: 'Invalid parameter passed as an argument.'

Reason:

A duplicate definition of an attribute abbreviation exists in the schema.

Solution:

  • To find out which abbreviation is duplicated, start metacp interactively with the necessary scripts and parameters.This action results in a stderr output to the console that reports the problem, as follows:

    "Error: Duplicate Attribute abbreviation "abbreviation".- Error in schema file file"

  • Correct the problem and restart the configuration procedure.

Uninstall and Unconfiguration Problems

This chapter handles uninstalling/unconfiguration problems that occur during DirX Identity uninstallation and unconfiguration.

Some Libraries Cannot be Removed

Indication:

When uninstalling DirX Identity on Windows platforms, some libraries, for example, libdirxutil.dll, cannot be removed.

Reason:

DirX Manager is open and uses the libraries due to the order specified in the PATH environment variable.

Solution:

Close DirX Manager.

Objects Remain after Unconfiguration

Indication:

After an unconfiguration, the root node dxmc=DirXmetahub together with the attribute DSET='' remains in the configuration database.

The error occurs only on DirX.

Reason:

You cannot delete the node dxmc=DirXmetahub via LDAP.

Solution:

To delete root node dxmc=DirXmetahub:

  • Start dirxadm and enter the command:

    modify ldap_root_dn -removeattr LNCO={/DXMC=DirXmetahub}

    For example: modify /O=pqr/CN=LdapRoot -removeattr LNCO={/DXMC=DirXmetahub}

    Alternatively, you can use DirX Manager to delete /DXMC=DirXmetahub in the attribute LDAP-Naming-Contexts.

  • Perform the dirxadm command:

    modify / -removeattr DADM={/DXMC=DirXmetahub/CN=admin}.

    Alternatively, you can use DirX Manager to delete /DXMC=DirXmetahub/CN=admin in the attribute DirX-Administrators

Now the node /DXMC=DirXmetahub is completely removed.

Unable to Remove Registry Key

Indication:

Message:

"Unable to remove registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment"

Reason:

The installer could not remove the Identity specific parts of the PATH variable.

Solution:

You can ignore this message if you intend to reinstall the product.

Alternatively, delete the DirX Identity-specific parts of the PATH variable by hand.

Uninstallation Hangs

Indication:

Uninstallation hangs in 'Registry' section.

Reason:

The file C:\Program Files\Zero G Registry\.com.zerog.registry.xml is available due to a previously erroneous operation.

Solution:

  • Delete the file C:\Program Files\Zero G Registry\.com.zerog.registry.xml

  • Start the uninstallation again.

Uninstallation on 64-bit Windows

Indication:

Uninstall fails while trying to stop running DirX Identity services.

Reason:

This issue is related to 32-bit custom code during uninstallation.

Solution:

Stop all DirX Identity services, including the one for the ActiveMQ message broker manually before uninstalling.

Update and Upgrade Installation Problems

This section describes problems that relate to DirX and DirX Identity update and upgrade installations and how to solve them.

Overwritten Agent Batch Files

Indication:

Workflows no longer run after update / upgrade installation.

Reason:

During the DirX Identity installation the agent batch files in the bin directory of the installation path are overwritten. If you changed something in these files (for example more memory for the Java processes) this information is lost.

Solution:

To avoid this problem, you should copy the agent batch file before you perform the changes. To use the copied and changed files, create new agent objects that use the new agent batch files and set links from all relevant jobs to these agent objects in the Connectivity configuration database.

In a distributed environment be sure that all DirX Identity servers where this agents shall run have copies of the changed files.

Overwritten SSL Certificate Stores during Upgrade

Indication:

After an upgrade installation and configuration, the SSL messaging no longer runs. A possible indication can be that the self registration processes fail.

Reason:

The upgrade installation overwrote the SSL Certificate stores.

Solution:

Re-import the server certificates to dxi_java_home/lib/security/cacerts

Overwritten cert8.db File

Indication:

SSL connections no longer work after upgrade or update installation and configuration.

Reason:

During an update or upgrade installation the cert8.db file is written again. If you used this default file for your certificates they are lost.

Solution:

To prevent such type of errors in the future, use another filename for your certificates and set the corresponding environment variable.

Windows Services Temporarily not Visible

Indication:

After an upgrade installation some or all of the Windows Identity services are not visible.

Solution:

Simply perform a reboot.