ETA_E_0020<RAC>, Active Dir. Account 'account name' on 'Endpoint Name' read failed: Unable to connect to Connector Server after upgraded the Vapp and Connector Server
search cancel

ETA_E_0020<RAC>, Active Dir. Account 'account name' on 'Endpoint Name' read failed: Unable to connect to Connector Server after upgraded the Vapp and Connector Server

book

Article ID: 383340

calendar_today

Updated On:

Products

CA Identity Suite CA Identity Manager CA Identity Governance

Issue/Introduction

After upgrading Vapp and External Windows connector, External Tools from 14.4.2 to 14.5, MS AD endpoint is not connecting to connector server anymore. Getting this error when trying view properties of any MS AD account in Provisioning Manager.

ETA_E_0020<RAC>, Active Dir. Account 'account name' on 'Endpoint Name' read failed: Unable to connect to Connector Server.

Environment

14.5 GA

Cause

When updated the External Windows Connector Server for some reason the "CA Identity Suite Connector Server (C++)" was NOT renamed to "Symantec Identity Manager - Connector Server (C++) because was executed the file GEN0000000004497/ConnectorServer/setup.exe instead of start the setup by GEN0000000004497/install.cmd

Resolution

Solution 1: 

To only Service being yet as "CA Identity Suite Connector Server (C++)" can change the service name:

  • Open the Registry Editor. To do so, press the Windows + R keys to open the Run window, and then type regedit.
  • On the left, navigate to the section where Windows Services are recorded: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ ...
  • Find and highlight your service in the list.
  • Right-click the entry and choose Rename
  • Enter the new name "Symantec Identity Manager - Connector Server (C++)
  • Reboot your computer

Solution 2:

Try the solution from Article JCS running but not handling requests but remember that if you have any custom OSGi bundles that were previously deployed you will need to re-deploy them 

Solution 3:

- Uninstall the "Symantec IAM Connector Server", rebooted and installed again using GEN0000000004497/install.cmd
- Re-apply patches needed for Java Connector Server and C++ Connector Server again (i.e. SP, CHF, HF, etc)
- Open ConnectorXpress and map MS AD Connector Type to External Windows Connector CS Config.
- Note if you have any custom OSGi bundles that were previously deployed you can re-deploy them 
- Note if you have any custom certificates that were previously added you will need to re-add them again

Powered by Wolken Software