Symantec Identity Manager C++ Connector Server (CCS) is returning error from Active Directory connector after applying 14.4CP2
search cancel

Symantec Identity Manager C++ Connector Server (CCS) is returning error from Active Directory connector after applying 14.4CP2

book

Article ID: 274158

calendar_today

Updated On:

Products

CA Identity Suite

Issue/Introduction

The customer upgraded their vApp environment to 14.4.2
After that they upgraded Windows based Connector server to 14.4.2 too.
After upgrade CCS server started crashing.
To fix the crash they installed this hotfix:
https://support.broadcom.com/web/ecx/solutiondetails?aparNo=99111794&os=WINDOWS-ALL
After the hotfix was installed CCS no longer crashes, but the AD connector returned errors like this one:

:ETA_E_0004<AAC>, Active Dir. Account 'XXXXXXXXXXXXX' on 'AD' creation failed: Connector Server Add failed: code 16 (NO_SUCH_ATTRIBUTE): failed to add entry eTADSAccountName=XXXXXXXXXXXXX,eTADSOrgUnitName=XXXXXX,eTADSDirectoryName=AD,eTNamespaceName=ActiveDirectory,dc=im,dc=etasa: JCS@IDM_Connector_Server: JNDI: [LDAP: error code 16 - Search of Global Catalog for proxyAddresses failed]: failed to add eTADSAccountName=Biikky Lal Karmacharya,eTADSOrgUnitName=PAM Users,eTADSDirectoryName=AD,eTNamespaceName=ActiveDirectory,dc=im,dc=etasa (ldaps://XXX.XXX.XXX.XXX:20411)

Also, sometimes the AD connector returns error 49:

:ETA_E_0060<MAC>, Active Dir. Account 'XXXXXXXXXXXXX' on 'AD' modification from Global User 'XXXXXX' failed: Connector Server Read failed: code 49 (INVALID_CREDENTIALS): failed on search operation: eTADSAccountName=XXXXXXXXXXXXX,eTADSOrgUnitName=XXXXX,eTADSDirectoryName=AD,eTNamespaceName=ActiveDirectory,dc=im,dc=etasa: JCS@IDM_Connector_Server: JNDI: [LDAP: error code 49 - Invalid Credentials] (ldaps://XXX.XXX.XXX.XXX:20411)

The credentials used to acquire are correct.

Environment

Release : 14.4

Resolution

New hotfix HF-DE575720.zip provided to rectify the problem.

Please contact Support to obtain the hotfix.