IDM and Provisioning connectivity Issues during startup - Exception in configuring Auto Inbound: javax.naming.OperationNotSupportedException: [LDAP: error code 53

book

Article ID: 223819

calendar_today

Updated On:

Products

CA Identity Manager CA Directory

Issue/Introduction

We are getting following error while starting the IDM environment:

2021-09-08 12:41:51,948 ERROR [im.plugins.IMEnvironmentInitializerPlugin] (MSC service thread 1-3) Exception in configuring Auto Inbound: javax.naming.OperationNotSupportedException: [LDAP: error code 53 - :ETA_E_0007<MCF>, Configuration Object 'BLS Connectivity Configuration' modification failed: DB Modify failed: DSA is unwilling to perform (ldaps://server123:20391) ]; remaining name 'eTConfigName=BLS Connectivity Configuration,eTConfigContainerName=Configuration,eTNamespaceName=CommonObjects,dc=im,dc=eta': [facility=6 severity=3 reason=0 status=12 message=A JIAM operation failed..]
javax.naming.OperationNotSupportedException: [LDAP: error code 53 - :ETA_E_0007<MCF>, Configuration Object 'BLS Connectivity Configuration' modification failed: DB Modify failed: DSA is unwilling to perform (ldaps://server123:20391) ]; remaining name 'eTConfigName=BLS Connectivity Configuration,eTConfigContainerName=Configuration,eTNamespaceName=CommonObjects,dc=im,dc=eta'
        at com.netegrity.llsdk6.imsimpl.settings.ProvisioningDefinitionImpl.executeJIAMCommit(ProvisioningDefinitionImpl.java:697) [imsapi6.jar:]
        at com.ca.identitymanager.plugins.IMEnvironmentInitializerPlugin.startEnvironment(IMEnvironmentInitializerPlugin.java:218) [identitymanager.jar:]
        at com.netegrity.ims.businessprocess.IMSEnvironmentServiceImpl.startEnvironmentInternal(IMSEnvironmentServiceImpl.java:804) [ims.jar:]
        at com.netegrity.ims.businessprocess.IMSEnvironmentServiceImpl.startEnvironment(IMSEnvironmentServiceImpl.java:692) [ims.jar:]

 

 

Resolution

Run dxinfo to check for errors or problems with the Provisioning directories. 

In the above case, the directory logs indicated the impd-co DSA was out of space.

DB size on DSA was full. Resolved by increasing size.