Resolving Installation Issues for Version 14.5 Connector Server upgraded from 14.4.2 CHF1
search cancel

Resolving Installation Issues for Version 14.5 Connector Server upgraded from 14.4.2 CHF1

book

Article ID: 385213

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

Overview

This article provides a step-by-step guide to resolving installation errors encountered during the upgrade to version 14.5.0 of the Connector Server. This issue typically arises due to outdated PKI libraries or improper installation procedures. Follow the instructions below to ensure a successful installation.

Problem Description

During the upgrade to version 14.5.0, users may encounter an installation error when updating the Connector Server. This issue can persist despite successful updates to the vApp.

im_connector_server_install.log contains these exception errors:

(Month Day, YEAR 4:49:12 PM), Install, com.ca.etrust.install.admin.connectorserver.SOAConfigureJCS, err, ProductException: (error code = 200; message="Java error"; exception = [java.lang.Exception: ERROR: Failed to connect to JCS, password not set. Reason: javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 19 - code 19 (CONSTRAINT_VIOLATION): failed to add entry uid=admin,ou=system: missing objectClass=]; remaining name 'uid=admin,ou=system'])
STACK_TRACE: 14
ProductException: (error code = 200; message="Java error"; exception = [java.lang.Exception: ERROR: Failed to connect to JCS, password not set. Reason: javax.naming.directory.InvalidAttributeValueException: [LDAP: error code 19 - code 19 (CONSTRAINT_VIOLATION): failed to add entry uid=admin,ou=system: missing objectClass=]; remaining name 'uid=admin,ou=system'])

Environment

Windows External Connector Server
Previous 14.4.2 CHF1
New: 14.5 

Cause

  • Installation fails with errors.
  • Logs indicate issues at the end of the installation process.

Resolution

Step 1: Update PKI Libraries

Ensure that the PKI libraries are updated to the latest version to avoid compatibility issues during installation.


Step 2: Install from Administrator Command Line

Execute the installation using an Administrator command line to ensure proper permissions.

  1.     Open the Command Prompt as Administrator.

  2.    Navigate to the setup directory.

  3.    Run the following command

C:\Users\me\Desktop\media\IM-1451.tar\IM-1451\ETPKI-1451.tar\ETPKI-1451\etpki>setup.exe install caller=IMPSSERVER verbose

Step 3: Validate Installation

After installation, verify the process using the log file.

  •     Check the etpki_install.log located at C:\Users\XXXXXX\AppData\Local\Temp\etpki_install.log.

  •     Ensure the log shows a return code of 0, indicating a successful installation.

Step 4: Verify Registry and DLL Version

Ensure the registry and DLL versions are correctly updated.
Registry Verification:

    Navigate to the following registry path:

My Computer\HEKY_LOCAL\MACHINE\SOFTWARE\wow6432Node\ComputerAssociates\Shared\CAPKIS\Dependencies\

    Check the following entries:
        `IMPSMANAGER` REG_SZ should be `5.2.14`
        `IMPSSERVER` REG_SZ should be `5.2.14`

DLL Version Verification:

    Verify the version of libcapki.dll located in:

    C:\Program Files\CA\SharedComponents\EPKI\CAPKI\CAPKIS\Windows\x86\32\lib

    This DLL should be version 5.2.14.0.

Additional Information

  • Always back up your system and important data before performing installations or upgrades.

  • If issues persist, consult the system administrator or reach out to technical support for further assistance.