Creating a SIEBEL connector generates the error "Failed to activate connector on proxy connector server"
Article ID: 236659
Updated On:
Products
Issue/Introduction
When try to create a Siebel endpoint, generates the error:
JNDI: Failed to activate connector on proxy connector server: [LDAP: error code 1 - SBL Target: Siebel error code: 27123, Siebel message: SBL Session: Can't create an IDispatch interface object. Check if the programmatic identifier SiebelDataControl.SiebelDataControl.1 is registered.
Environment
Identity Manager 14.x & v15
Resolution
The error you are facing:
JNDI: Failed to activate connector on proxy connector server: [LDAP: error code 1 - SBL Target: Siebel error code: 27123, Siebel message: SBL Session: Can't create an IDispatch interface object. Check if the programmatic identifier SiebelDataControl.SiebelDataControl.1 is registered.
Is part of a much longer string of errors that starts with:
[ApacheDS Worker-thread-7] (com.ca.jcs.core:com.ca.jcs.DefaultConnectorManager:644) ERROR - The endpoint type eTNamespaceName=Siebel,dc=im,dc=etasa that was referenced in the request has not been activated
[ApacheDS Worker-thread-7] (com.ca.jcs.core:com.ca.jcs.osgi.exchange.router.MessageRouter:551) ERROR - A remote server returned an error: org.apache.directory.shared.ldap.exception.LdapNameNotFoundException: JCS@##########: The endpoint type eTNamespaceName=Siebel,dc=im,dc=etasa that was referenced in the request has not been activated
This is caused by the lack of the Siebel mobile web client or the Siebel dedicated web client being installed on the C++ connector server.
Oracle states this here:
https://docs.oracle.com/cd/B40099_02/books/OIRef/OIRefProgramming24.html
and where the install happens:
https://docs.oracle.com/cd/B40099_02/books/OIRef/OIRefProgramming8.html#wp1004115
Also, Our documentation states this here:
For Identity Manager 14.5.x
For Identity Manager v15
Please install the client on the C++ Connector server.
Feedback
