SBL-BPR-00162: Error invoking service 'Complex Product AutoMatch Service', method 'AutoMatch' at step 'Auto Match Port Ids'.

If you asset has sub-products which doesnt exist in the current product strucuture , this error will appear. Solution : Inactivate such product under the asset and try to perform the operation.

ORA-12520,SBL-SEC-10018,SBL-DBC-00107

SecAdptLog API Trace 4 0 2013-02-02 15:32:12 DB SecurityLogin with username=sadmin, parameters=2e53500. ObjMgrDBConnLog Create 5 0 2013-02-02 15:32:12 DataBase Connection Object was created at 84593f0; DB User: 'sadmin' DBCLog DBCLogDetail 4 0 2013-02-02 15:32:12 Unable to get environment variable: SIEBEL_ORA_BIND_PEEK, continuing with default "FALSE" ObjMgrLog Error 1 0 2013-02-02 15:32:12 (oracon.cpp (3150)) SBL-DBC-00107: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists. SQLParseAndExecute Execute 5 0 2013-02-02 15:32:12 ORA-12520: TNS:listener could not find available handler for requested type of server SecAdptLog API Trace 4 0 2013-02-02 15:32:12 Security DB user connect to DB "your DB" with username=sadmin returns err 22152 and connection 84593f0. SecAdptLog API Trace 4 0 2013-02-02 15:32:12 Security DB user delete DB connectoin 84593f0 ObjMgrDBConnLog Delete 5 0 2013-02-02 15:32:12 DataBase Connection was deleted at 84593f0 GenericLog GenericError 1 0 2013-02-02 15:32:12 (secmgr.cpp (2357) err=7010018 sys=0) SBL-SEC-10018: An Oracle database error has occurred. Please continue or ask your systems administrator to check your application configuration if the problem persists.(SBL-DBC-00107) ORA-12520: TNS:listener could not find available handler for requested type of server

SBL-SEC-00003 - Server busy error

secmgr.cpp (2278) err=7000003 sys=0) SBL-SEC-00003: An error occurred checking the checksum of the security adapter library. Please contact your system administrator for assistance. ObjMgrSessionLog ObjMgrLogin 3 0 2013-01-02 17:25:59 Login failed for Login name : sadmin Solution : set CRC value to "0" in the DBdatasource named subsystem

Login failed attempting to connect to siebel.tcpip.none.none

6: [SWSE] Open Session failed (0x56bf) after 224.6211 seconds. ProcessPluginRequest ProcessPluginRequestError 1 0 2013-01-26 22:09:58 36: [SWSE] Failed to obtain a session ID. Login failed attempting to connect to %1 ProcessPluginRequest ProcessPluginRequestError 1 0 2013-01-26 22:09:58 36: [SWSE] Set Error Response (Session: Error: 00022207 Message: Login failed attempting to connect to siebel.tcpip.none.none://VirtualServer/****/EAIObjMgr_enu) ProcessPluginRequest ProcessPluginRequestError 1 0 2013-01-26 22:09:58 36: [SWSE] Login failed.\nSBL-SSM-00005: Timeout occurred while opening SISNAPI connection. GenericLog GenericError 1 0 2013-01-26 22:14:11 (smconn.cpp (271) err=1801201 sys=145) SBL-NET-01201: Internal: connect() failed: Connection timed out Solution : Check if the SC broker and SR broker is running on all the siebel servers

CA SiteMinder Integration with Siebel

Here goes the steps to integrate siteminder with siebel

SitiMinder Siebel Connector Errors

22-4572 DBG: SecurityLogin8() calling AuthAzAndCollectResponse()
22-4572 DBG: AuthAzAndCollectResponse - Auth rejected
22-4572 DBG: Function return code is No
22-4572 ERR: User NOT authenticated!

32-6776 DBG: Checking for Anonymous user
32-6776 DBG: SecurityLogin8() calling AuthAzAndCollectResponse()
33-6776 DBG: AuthAzAndCollectResponse - Authentication ACCEPTED
3-6776 DBG: AuthAzAndCollectResponse - Authorization ACCEPTED
33-6776 DBG: Found response siebelcbg
33-6776 DBG: Found SIEBELUSER Response
33-6776 DBG: Usernames match

SiteMinder TroubleShooting - Siebel Server Issues

6876: _smiSarmFdrObj::Execute(43d204) for SARM, WaitTime=60

SisnTcpIp SisnSockDetail 4 00008f304d9e0d78:0 2011-04-08 05:02:59 10136: [LOCALTRANS-server] accept() timeout during get conn request

SisnTcpIp SisnSockDetail 4 00008f304d9e0d78:0 2011-04-08 05:03:04 10136: [LOCALTRANS-server] accept() timeout during get conn request

SisnTcpIp SisnSockDetail 4 00008f304d9e0d78:0 2011-04-08 05:03:09 10136: [LOCALTRANS-server] accept() timeout during get conn request Solution :Update the SiteMinderSecAdpt profile at Enterprise Level

SiteMinder TroubleShooting - Webserver Issues

WebServer Errors:
[SWSE] Set Error Response (Session: Error: 07668281 Message: The password you have entered is not correct. Please enter your password again.(SBL-DAT-00569))

Site Minder Implementation

1.Installation of security adapter.

a.Files from this Siebel Agent installationfolder\Siebel\bin folder should be copied into Siebel Server installation's bin directory.
The files present in the Siebel Agent installationfolder\Siebel\bin folder are :

SmSecurityProvider.dll
ProviderTest.exe
SmAgentAPI.dll
*These above files will be suffixed with corresponding version.
b.Copy the following initialization and configuration files from the Siebel Agent Installationfolder\Siebel\config\SecurityAdapter folder to the Siebel Server
installation's bin directory:

\SmSiebelSSO.ini
\SmSiebelSSO.conf

2.Configuring Security AdapterParameters can be edited in the \SmSiebelSSO.conf which is the configuration file.
To specify the log file path we need use this below parameter
LogFile=c:/logs/Test.log
To Edit the log level we need use this below parameter
LogLevel=3
Where # 0 None
# 1 Errors
# 2 Information
# 3 Debug
To communicate with the Policy server the below parameters should be configured:

PolicyServer=[
AgentName=
SharedSecret=
Resource=/SiebelConnector/



3.Changes in the Siebel configuration FileThese below lines should be modified
1.SecurityAdapter=SiteMinder
2.In the [SecurityAdapter] header
SiteMinder = SiteMinder (Should be Added)
3.At the End of the file add a new section similar to the following section (for your platform), updating the file paths as appropriate for your environment:
[SiteMinder]
DllName = C:\Program Files\CA\Siebel Connector\SmSecurityProvider.dll
ConfigFile = C:\Program Files\CA\Siebel Connector\SmSiebelSSO.conf

4. Create Named Subsystem for Custom Security Adapter

1.Create a named subsystem, SiteMinderSecAdpt, for the custom Security
Adapter.
2.Change the the below parameters for the named sub system.
CustomSecAdpt_SecAdptDllName=SmSecurityProvider
ConfigFileName=d:\siebel\bin\enu\SmSiebelSSO.ini
ConfigSectionName=SiteMinder for named subsystem SiteMinderSecAdpt
Note : The section name, SiteMinder, in this command to modify the ConfigSectionName, must match the section name defined in the SmSiebelSSO.ini file.

SBL-BPR-00162

SBL-BPR-00162 : Error invoking service 'EAI Siebel Adapter', method 'Query' at step 'BS Name'.

The active Siebel Repository is not in sync with the SRF or it might be pointing to some other SRF.Try recompiling the object definitions that has been created or changed in Tools.

SBL-DAT-00382

SBL-DAT-00382 : Siebel Tools Error : Check the Field Values.It should be unique.

SBL-EAI-04187

SBL-EAI-04187 : XML Tag '%1' in field '%2' of Integration Component '%3' has been defined differently in a previous field.

The Field "XML Tag" should have an unique Value or the Properties of the Field(DATA_TYPE) should be same.

SBL-EIM-00206: Failed to run initial process.

Check fo the job parameters in the EIM Job.
While running EIM jobs,we need to give a batch no and this batch no
should be given in the EXTENDED PARAMETERS field.