SBL-SVC-00208: Please Loin First

Applies to:

Siebel System Software - Version 7.8.2.3 [19221] and later
z*OBSOLETE: Microsoft Windows Server 2003

Product Release: V7 (Enterprise)

Version: 7.8.2.3 [19221]

Database: Oracle 9.2.0.1

Application Server OS: Microsoft Windows 2003 Server SP1

Database Server OS: Microsoft Windows 2003 Server SP1



This document was previously published as Siebel SR 38-3114862154.



***Checked for relevance on 05-Feb-2013***

Symptoms

SBL-SVC-00208


Unable to startup new/fresh install (not an upgrade) of Siebel
7.8.2.3. I will post a follow up of this initial SR with details and
attachments of our efforts to date.

Cause

An error occurred checking the checksum of the security adapter library.

Solution

Message 1

For the benefit of others,

The Customer was unable to startup a newly installed Siebel Server 7.8.2.3

*Errors seen in Object Manager logs ('SFSObjMgr_enu_9307.log') included:

GenericLog    GenericError    1    0    2006-08-11
13:50:49    (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.

ObjMgrCTLog    Error    1    0    2006-08-11 13:50:49    (ctxtmgr.cpp (3435)) SBL-SVC-00208: Please login first.

*Other errors seen in the SWE log included:

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-08-11
13:45:32     3580: [SWSE] Failed to obtain a session ID. An error
occurred checking the checksum of the security adapter library. Please
contact your system administrator for assistance.

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-08-11
13:45:32     3580: [SWSE] Set Error Response (Session: Error: 00023181
Message: SBL-SEC-00003: An error occurred checking the checksum of the
security adapter library. Please contact your system administrator for
assistance.)

ProcessPluginRequest    ProcessPluginRequestError    1    0    2006-08-11
13:45:32     3580: [SWSE] SBL-SVR-00040: Internal: Informational,
encrypted parameter.

GenericLog    GenericError    1    0    2006-08-11
13:48:14    (smconn.cpp (271) err=1801020 sys=1300230) SBL-NET-01020:
Internal: unknown hostname

Message 2

*Initial research around these error messages suggested that the
recommendations offered in following documents - published on SupportWeb
– might well apply:
(1) Siebel Error Message SBL-DAT-00563: An error
occurred checking the checksum of the security adapter library. Please
contact your system administrator for assistance
(2) 38-3097108425 - SWSE does not work after upgrade to 7.7.2.6

******Resolution******

As customer had configured DB authentication and not ADSI, the resolution entailed
re-generating
the checksum on the DLL used for DB Authentication and entering this
value into the CRC for the Enterprise Profile Configuration.

Applies to:

Siebel Field Service - Version: 8.1.1.5 SIA [21229] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

The browser displays following error message when a user attempts to
launch an application via the Web Client which uses the LDAP Security
Adapter authentication:

The server you are trying to access is either busy or
experiencing difficulties. Please close the Web browser, open a new
browser window, and try logging in again.

Detailed
Object Manager log which is set via the srvrmgr with a command "change
evtloglvl %=5 for comp <Object Manager Name>" shows the following
error:

2021 2011-12-02 08:53:17 2011-12-02 08:53:18 +0900
00000678 001 003f 0001 09 SFSObjMgr_jpn 10485770 6008 2104
D:\app\sba\siebsrvr\log\SFSObjMgr_jpn_0010_10485770.log 8.1.1.5 [21229]
JPN

SecMgrLog Debug 5 000000024ed81de4:0 2011-12-02 08:53:18 applicationuser = uid=appusr,cn=Users,dc=dev,dc=abc,dc=co,dc=jp
SecMgrLog Debug 5 000000024ed81de4:0 2011-12-02 08:53:18 applicationpassword = appusr

SecAdptLog
API Trace 4 000000024ed81de4:0 2011-12-02 08:53:18 Ldap Utility:
BindAsAppUser failed due to invalid password, please check the value of
ApplicationPassword parameter,
SecAdptLog 3rdpartyTrace 3 000000024ed81de4:0 2011-12-02 08:53:18 ldap_unbind(3b61960) returns 0.

GenericLog
GenericError 1 000000024ed81de4:0 2011-12-02 08:53:18 (secmgr.cpp
(2751) err=4597521 sys=0) SBL-SEC-10001: An internal error has occurred
within the authentication subsystem for the Siebel application. Please
contact your system administrator for assistance.

ObjMgrSessionLog
Error 1 000000024ed81de4:0 2011-12-02 08:53:18 (physmod.cpp (9377))
SSBL-DAT-00565: An internal error has occurred within the authentication
subsystem for the Siebel application. Please contact your system
administrator for assistance.

ObjMgrSessionLog ObjMgrLogin 3 000000024ed81de4:0 2011-12-02 08:53:18 Login failed for Login name : ANONUSR

ObjMgrCTLog Error 1 000000024ed81de4:0 2011-12-02 08:53:18 (ctxtmgr.cpp (4553)) SBL-SVC-00208: Please login first.

Although
it shows "BindAsAppUser failed due to invalid password, please check
the value of ApplicationPassword parameter" message, Application User's
password is a correct one.

Note that the customer is implementing
SharedDBUsername and SharedDBPassword LDAP Security Adapter profile
parameters that has a corresponding Siebel Employee record by referring a
Doc ID 475380.1.

Cause

The IBM LDAP search utility ldapsearch returned "Invalid credentials" error as follows:

C:\Documents and
Settings\Administrator>ldapsearch -h srvrA -p 389 -D
"uid=appusr,cn=Users,dc=dev,dc=abc,dc=co,dc=jp" -w appusr -b
"cn=Users,dc=dev,dc=abc,dc=co,dc=jp" -d 7 "(CN=appusr)" >
c:\ldapsearch.txt
...
ldap_simple_bind: Invalid credentials

It
was found that Application User Distinguished
Name:"uid=appusr,cn=Users,dc=dev,dc=abc,dc=co,dc=jp" was incorrect. Once
it changed to "cn=appusr,cn=Users,dc=dev,dc=abc,dc=co,dc=jp",
ldapsearch ran successfully.

Solution

Modified the ApplicationUser LDAP Security Adapter profile parameter to
"cn=appusr,cn=Users,dc=dev,dc=abc,dc=co,dc=jp" from
"uid=appusr,cn=Users,dc=dev,dc=abc,dc=co,dc=jp" and restart Siebel
Server service resolved an authentication issue.

Please determine
the correct Distinguished Name in the Directory Server before you set
values to the LDAP Security Adapter profile.

Applies to:

Siebel CRM - Version: 8.1.1.1 SIA [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

New Object Manager has been created by copying the existing object manager record.
If 
Application Name parameter is set  to "Siebel Sales Enterprise"
(standard value) , we can connect to that Application with the new
object manager.
If another value is set, for instance "Siebel Power Communications", getting below errors.
"SBL-SVC-00208: Please Loin First".
when trying to connect to the URL getting "Login failed for Login name : GUESTERM"

Cause

Issue is caused by additional parameters for the new object manager are not set correctly.
when copying the object manager the values are again set to defalut. It will not take new values which are already modified.

Solution

As a solution you need to manually modify the object manager parameter
values. Enhancement request is addressing the behavior of not taking new
parameters when we copy the object manager.Thanks.

Bug 10643141  : [CR#12-1SFP95X][FR#12-1SFP96J] TO CLONE/COPY OBJECT MANAGER PARAMETERS SETTING

It
is currently a P4 enhancement, meaning it's not scheduled in the
foreseeable future. Current target is 9.0. Unless there is some
compelling reason to implement this.

Applies to:

Siebel System Software - Version 7.7.2 [18325] and later
Oracle Solaris on SPARC (64-bit)

Product Release: V7 (Enterprise)

Version: 7.7.1 [18306] Com/Med

Database: Oracle 9.2.0.2

Application Server OS: Sun Solaris 5.8

Database Server OS: Sun Solaris 5.8



This document was previously published as Siebel SR 38-1448301611.

***Checked for relevance on 04-Feb-2013***

Symptoms

Customer reported the following:

The Siebel CRM development
environment was moved from one machine to another. After a complete
re-install to be sure the new IP addresses are correct the 'new'
environment is up and running but we can not connect to it by Siebel web
client (the Siebel dedicated client works fine).


The following errors appeared in Siebel logs.

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.
GenericLog    GenericError    1    0    2004-08-17
14:36:18    (secmgr.cpp (2265) err=7010018 sys=0) SBL-SEC-10018: An
Oracle database error has occurred.

ORA-12154: TNS:could not resolve service name

SBL-SEC-10001:
An internal error has occurred within the authentication subsystem for
the Siebel application. Please contact your system administrator for
assistance.
ObjMgrCTLog    Error    1    0    2004-08-17 14:36:19    (ctxtmgr.cpp (3291)) SBL-SVC-00208: Please login first.

Cause

A mismatch between "Data source default user name" - which was null in the 'Gateway Datasource Profile Configuration'.
The
"Data source Connect String" in the 'Server Datasource Profile
Configuration' was set to 'siebsrvr_bexdev' (the ODBC datasource)
instead of pointing to the TNS-service name (in this case BEXDEV1).

SBL-SVC-00208, SBL-SEC-10018, SBL-SEC-10001

Solution

For the benefit of other readers:

Changing the ODBC Data Source Connect String to point to the correct TNS service name solved the problem

 

 

 

Applies to:

Siebel System Software - Version 7.7.1 [18306] to 8.2.2.2 SIA[23016] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (Enterprise)

Version: 7.7.1 [18306]

Database: Oracle 9.2.0.2

Application Server OS: Microsoft Windows 2000 Server SP 4

Database Server OS: Sun Solaris 2.8



This document was previously published as Siebel SR 38-1460698962.



***Checked for relevance on 13-Mar-2013***

Symptoms

SBL-SVC-00208, SBL-SEC-10018, SBL-SEC-10001


We currently working on enabling SSL using LDAP Authentication. We are currently experiencing Issues running GSK6IKM.

We are using IBM JDK 1.31. In addition, we are running JRE 1.42 on the Siebel Server.

Cause

Incorrect setup

Solution

For the benefit of other users:

The primary error from the object manager logs is as follows:


SecAdptLog    3rdpartyTrace    3    0    2004-09-08
14:15:14    ldap_ssl_client_init(D:\APPS\sea77\siebsrvr\SSLFiles\key.kdb,
NULL) returns 113.

Ldap_ssl_client_init is a function call in
the IBM LDAP Client (GSKit). It is supposed to associate the key.kdb
file with the current application (object manager). However a return
code of 113 (binary 0x71) indicates “LDAP_SSL_INITIALIZE_FAILED     0x71
- SSL initialization call failed”.

Since the second parameter
(the keyfile password) is being passed as NULL to the
ldap_ssl_client_init function, it is essential that the key.sth file
which contains the keyfile’s password be copied to the same directory
where the key.kdb is stored (D:\APPS\sea77\siebsrvr\SSLFiles). After
copying the key.sth file correctly to this directory, the customer was
able to correctly connect to the LDAP server using SSL.

Applies to:

Siebel System Software - Version 8.0.0.1 [20408] to 8.2.2.2 SIA[23016] [Release V8]
Information in this document applies to any platform.

Product Release: V8 (Enterprise)

Version: 8.0 [20405]

Database: Oracle 10.1.0.4

Application Server OS: Red Hat Linux 4.0

Database Server OS: Sun Solaris 9



This document was previously published as Siebel SR 38-3467659813.

Symptoms

Hi, we're trying to setup a PoC of Siebel 8.0 on Linux Redhat 4.0 and
had encountered issue while trying to config LDAP authentication and an
error had ocurred in the OM log file. IBM LDAP 6.0 Client is installed
and is using OID 10.1.2 as the LDAP Server.

We have repreatedly verified LDAPparameters many times and believed we have setup the right parmeters.

We got the following error in the log file:

SBL-SEC-00102 An error occurred loading the security adapter library. Please contact your system administrator for assistance.

SBL-DAT-00562 An error occurred loading the security adapter library. Please contact your system administrator for assistance


Btw, logfile and siebns are attached for your reference..

Cause

Change Request 12-1LDF7SJ

Solution

Message 1

Please assign this SR as soon as possible. This is becoming critical for the customer .

Many Thanks

Message 2

For the benefit of other readers

The customer was implementing LDAP authentication with Siebel 8.0 on Red Hat Linux 4.0 with Oracle Internet Directory.


After configuring the LDAP Adapter and restarting the Siebel Server the
Object Manager startup would fail with the following errors:


GenericLog GenericError 1 0000000646fb2542:0 2007-09-27 20:38:39
(secmgr.cpp (2407) err=4587622 sys=0) SBL-SEC-00102: An error occurred
loading the security adapter library. Please contact your system
administrator for assistance.
ObjMgrSessionLog Error 1
0000000646fb2542:0 2007-09-27 20:38:39 (physmod.cpp (9244))
SBL-DAT-00562: An error occurred loading the security adapter library.
Please contact your system administrator for assistance.

ObjMgrSessionLog Error 1 0000000646fb2542:0 2007-09-27 20:38:39
(model.cpp (5867)) SBL-DAT-00562: An error occurred loading the security
adapter library. Please contact your system administrator for
assistance.
ObjMgrCTLog Error 1 0000000646fb2542:0 2007-09-27 20:38:39 (ctxtmgr.cpp (4492)) SBL-SVC-00208: Please login first.


The customer confirmed that the IBM LDAP Client 6.0 was already
installed. After further investigation it was found that the LDAP Client
libraries needed to be added to the LD_LIBRARY_PATH set in
/siebsrvr/siebenv.sh. siebenv.sh was modified as follows:

[....]

Message 3

[....]

if [ a${LD_LIBRARY_PATH} = ${LD_LIBRARY_PATH}a ] then

LD_LIBRARY_PATH=${SIEBEL_ROOT}/lib:${SIEBEL_ROOT}/lib/odbc/merant:/opt/ibm/ldap/V6.0/lib:${MWHOME}/lib:${SQLANY}/lib:/usr/lib

else
LD_LIBRARY_PATH=${SIEBEL_ROOT}/lib:${SIEBEL_ROOT}/lib/odbc/merant:/opt/ibm/ldap/V6.0/lib:${MWHOME}/lib:${SQLANY}/lib:/usr/lib:${LD_LIBRARY_PATH}
Fi

After making this change LDAP Authentication worked correctly. Change Request 12-1LDF7SJ was logged for a documentation defect.

Applies to:

Siebel System Software - Version 8.1.1.1 SIA [21211] to 8.1.1.8 SIA [23012] [Release V8]
Information in this document applies to any platform.

Microsoft Windows 2008 R1 and R2

Symptoms

LDAP Security Adapter fails when configured for SSL in Siebel 8.1 on
Windows 2008 (specifically). This platform is officially supported (see Document 781428.1).
Attempting to connect to the Siebel application associated with the
LDAP Security Adapter produces the following error message:


"The server you are trying to access is either busy or experiencing
difficulties. Please close the Web browser, open a new browser window,
and try logging in again."

ERROR MESSAGES
ldap_ssl_client_init(key.kdb, ...) returns 113.
ldap_ssl_init(10.123.456.789, 636, ...) returns 0.
Ldap Utility: GetLdapHandle returns 3
LDAP SecurityFreeErrMessage8, ErrMessage=e368d48.

SBL-SEC-10018: ldap_ssl_init failed

SBL-SEC-10001: An internal error has occurred within the authentication
subsystem for the Siebel application. Please contact your system
administrator for assistance.
SBL-DAT-00565: An internal error has
occurred within the authentication subsystem for the Siebel application.
Please contact your system administrator for assistance.
SBL-SVC-00208: Please login first.

STEPS
Follow Bookshelf Security Guide instructions to configure LDAP Security Adapter with SSL. This requires the following:
1. Root CA certificate from the directory server
2. Client keyfile generated using IBM GSKit and adding the above certificate

3. Configuring the LDAP Security Adapter by setting the parameters Port
(636 for secure LDAP by default) and SslDatabase (pointing to the .KDB
file generated by GSKit)
4. Restart the Siebel server and attempt to login to the application

NOTE: The IBM LDAP search utility LDAPSEARCH runs
successfully *only* when Compatibility Mode is set to Windows 2003
Service Pack 1. Applying this setting to the SIEBMTSHMW executable does
not have the same affect - and the LDAP Security Adapter still fails.

Cause

Behavior is the result of a bug.  Fixed in 8.1.1.9.

Solution

1. Install Siebel 8.1.1.9 (when available)
2. Configure the ADSI Security Adapter as per Siebel Bookshelf to secure LDAP communications using the UseSsl parameter
3. Associate this security adapter with your Siebel application

Applies to:

Siebel System Software - Version: 7.7.2 SIA [18325] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003

Product Release: V7 (Enterprise)

Version: 7.7.2 [18325] Life Sci

Database: Oracle 9.2.0.6

Application Server OS: Microsoft Windows 2003 Server

Database Server OS: Microsoft Windows 2003 Server



This document was previously published as Siebel SR 38-2649586771.

Symptoms

SBL-DAT-00144, SBL-DAT-00227, SBL-DAT-00411, SBL-SVC-00208, SBL-SEC-10018, SBL-SEC-10001We have experienced some strange behavior after installing the 7.7.2.4 patch.

After
installing the patch for the Siebel Server/Gateway/SWEApp - following the steps in the 7.7.2.4
guide - it was only possible to access the application using the dedicated client. After
uninstalling the 7.7.2.4 patch the application is still only accessible through the dedicated
client and we have seen crashes on the server every time we reboot the macine (the siebmtshmw.exe
process). The crashes disappear after a while.

We would appreciate your assistance in
getting the environment back in better shape and some advice (and any known issues) regarding
patch 7.7.2.4.

Cause

Configuration/ Setup

Solution

Message 1

For the benefit of other users:



Original Issue:

Customer encountered application crashes with the following call stack after applying MR 7.7.2.4:



- CALL STACK -

sslcshar +0x17c5c = SSstring::operator=() +0xc

sscfdm +0x916ac = CSSSqlBCDef::AddIdField() +0x2fc

sscfdm +0x9182e = CSSSqlBCDef::AddJoinSystemFields() +0x9e

sscfdm +0x4aeeb = CSSFieldList::ResetBCFieldIndexes() +0x205eb

sscfdm +0x54287 = CSSFieldList::ResetBCFieldIndexes() +0x29987

sscfdm +0x54448 = CSSFieldList::ResetBCFieldIndexes() +0x29b48

sscfdm +0x8e479 = CSSSqlBCDef::ValidateSqlFieldDef() +0x69

sscfdm +0x51b4c = CSSFieldList::ResetBCFieldIndexes() +0x2724c



Solution:

The behavior has been replicated using the Siebel dedicated client against the customer Local DB.



Upon further investigation of the log file, crash file and FDR file, it
was determined that incorrect configuration was causing these crashes.



The Siebel client log file included the following error messages just before the crash occurred:



ObjMgrSRFLog    Warning    2    0    2005-12-08 12:18:19    Invalid
Configuration: Cannot Specify Validation on Multi-Valued Field
(Condition Amount) for BusComp (INS Vehicle)



ObjMgrQueryLog    Warning    2    0    2005-12-08 12:18:19    (query.cpp
(11594)) SBL-DAT-00411: The 'IFF' function is not supported.



ObjMgrSRFLog    Warning    2    0    2005-12-08 12:18:20    (cdf.cpp
(2607)) SBL-DAT-00144: Could not find 'Table' named 'S_EMPLOYEE'. This
object is inactive or nonexistent.





Upon taking the following changes in Siebel Tools the crash was no longer encountered:



- Removing the validation ">=0" from the Condition Amount field in BC INS Vehicle

- In Siebel Tools > Flat Tab, please search for all Calculated Fields
that include the following in the Calculated Expression: "IFF"

> Please change IFF to IIF

- Run a validation for the Service Request BC

> There a couple of errors that needs to be verified. One of them is a
join referencing the S_EMPLOYEE table which is inactive.



Keywords:

Crash, 7.7.2.4, sslcshar +0x17c5c = SSstring::operator=() +0xc, sscfdm +0x916ac = CSSSqlBCDef::AddIdField() +0x2fc

Applies to:

Siebel System Software - Version: 7.8.2.3 [19221] to 8.1.1 [21112] - Release: V7 to V8
Information in this document applies to any platform.

Product Release: V7 (Enterprise)

Version: 7.8.2.3 [19221]

Database: Microsoft SQL Server 2005

Application Server OS: Microsoft Windows 2003 Server SP2

Database Server OS: Microsoft Windows 2003 Server SP2



This document was previously published as Siebel SR 38-3395412005.

*** Checked for relevancy on 13-MAR-2012 ***

Symptoms

Customer reported a Siebel Server (test environment) stopped responding,
while the production environment is working fine, with no recent
changes implemented in the test environment.

While troubleshooting the issue, the following actions were manually performed:

• Stopped and restart the Siebel application service


• Stopped and restarted the MS SQL the database server


• Cold booted the Siebel application server, database server and Websphere application server.

After
performing these actions in the test environment, the following error
message is presented during a web session login attempt to the sales_enu
application using the SADMIN or GUESTCST user accounts:

The server you are trying to access is either busy or
experiencing difficulties. Please close the Web browser, open a new browser window, and try
logging in again.

Cause

This is caused by a setup or configuration issue in the customer environment.

Solution

The object manager files provided by the customer contained the following information:

SBL-DBC-00105: An error has occurred executing a Sql statement.
CAUSE: A SELECT SQL statement failed to be executed against the database server.
CORRECTIVE
ACTION: Review the error message returned by the database, which should
be logged in the Siebel log files. It is important to obtain the
failing SQL statement as well but SQL statements are not logged unless
SQL tracing is enabled.


SBL-DAT-00178: The Locale Code is
invalid. Please check the value of the parameter LocaleCode for this
component. A row corresponding to the Locale Code must exist in the
S_LOCALE table.
SBL-DAT-00587:An error occurred setting the default locale for the session.
CAUSE: Could be caused by programming logic error or misconfiguration.
CORRECTIVE ACTION:Ensure the server parameter "Locale Code" is set to a valid 3 letter locale code.

SBL-SVC-00208:Please login first.

Two possible workaround solutions may resolve this issue, which can be checked by the database administrator:

1. Check
   database user GUESTCST, and confirm if it has "sse_role" enabled.  If
   not, grant this guest user the "sse_role", restart Siebel services and
   see if this resolves the issue.
   


2. Check the GUESTCST
   account and confirm if it has the "db_denydatareader" enabled. If so,
   disable this parameter (or simply remove any value assigned to it),
   restart Siebel services and see if this resolves the issue.

---

NOTE: 
Refer to << DOCUMENT 1411824.1>>  for more information on
the Siebel object manager log files and enabling enhanced tracing. 

Applies to:

Siebel Call Center - Version 7.8.2.10 SIA [19241] to 8.2.2.1 SIA[23012] [Release V7 to V8]
Siebel CRM - Version 7.8.2.10 SIA [19241] to 8.2.2.1 SIA[23012] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003 R2 (32-bit)

Symptoms

Users facing issues while accessing Siebel  Thin client, via Internet explorer and when LDAP/ADSI is in use.
Generic
Error is displayed : 'The server you are trying to access is either
busy or experiencing difficulties. Please close the Web browser, open a
new browser window, and try logging in again.[05:25:20] '.

The
web server, gateway server and siebel servers will be up and running and
even when bounced all the servers the thin client doesnt show login
page. or shows above error.

Changes

No changes made

Cause

It is possible that error is caused due to directory search from BaseDN causing the administrative locks on the userid.
 Any possible causes for adminitrative locks on user accounts in LDAP/ADSI can also cause this issue.


The logs may be similar to :

SecAdptLog Debug 5 0 2008-10-03 11:10:33 LDAP SecurityLogin8 step 1: initialize ldap server connection
SecAdptLog 3rdpartyTrace 3 0 2008-10-03 11:10:33 ldap_init(ldap.cisco.com, 389) returns d24be0
SecAdptLog Debug 5 0 2008-10-03 11:10:33 LDAP SecurityLogin8 step 2: initial bind to ldap server
SecAdptLog
3rdpartyTrace 3 0 2008-10-03 11:10:34 ldap_simple_bind_s(d24be0,
uid=HRSiebelLogin,ou=applications,o=cisco.com, *) returns 0
SecAdptLog Debug 5 0 2008-10-03 11:10:34 LDAP SecurityLogin8 step 3: check for single sign on
SecAdptLog Debug 5 0 2008-10-03 11:10:34 LDAP SecurityLogin8 step 4: check for trust token if SSO is on.
SecAdptLog Debug 5 0 2008-10-03 11:10:34 LDAP SecurityLogin8 step 5: set siebeUsername/siebelUserDn
SecAdptLog
API Trace 4 0 2008-10-03 11:10:34 Ldap Utility: Get User DN.
Username=HRSiebelLogin, Attribute=uid, BaseDN=o=cisco.com
SecAdptLog
3rdpartyTrace 3 0 2008-10-03 11:10:36 ldap_search_s(d24be0, o=cisco.com,
LDAP_SCOPE_SUBTREE, (uid=HRSiebelLogin), 244e080, 1) returns 11.
SecAdptLog Memory Mgmt Trace 5 0 2008-10-03 11:10:36 LDAP SecurityFreeErrMessage8, ErrMessage=6e92fc0.
GenericLog
GenericError 1 0 2008-10-03 11:10:36 (secmgr.cpp (2357) err=7010018
sys=0) SBL-SEC-10018: Administration limit exceeded
GenericLog
GenericError 1 0 2008-10-03 11:10:36 (secmgr.cpp (2429) err=7010001
sys=0) SBL-SEC-10001: An internal error has occurred within the
authentication subsystem for the Siebel application. Please contact your
system administrator for assistance.
ObjMgrCTLog Error 1 0 2008-10-03 11:10:36 (ctxtmgr.cpp (3435)) SBL-SVC-00208: Please login first.

Solution

Set the basedn to root and do not have any restrictions and make sure
that applicationuserid has complete read,execute access to all user
groups or OU.
Check for any administrative locks on user accounts in LDAP/ADSI.
This changes must be done at LDAP/AD level in consultation of your admin only.
If you still face issues after making this changes, log a SR under Siebel Security Auth-> ADSI

Applies to:

Siebel Call Center - Version: 7.7.2.6 SIA [18372] to 7.7.2.10 SIA [18385] - Release: V7 to V7
Information in this document applies to any platform.

Symptoms

When I changed Propagate Change parameters to False on the DB Security
Adapter profile and restarted a Siebel Server service, I could not login
via the Web Client and got "The server you are trying to access is
either busy or experiencing difficulties. Please close the Web browser,
open a new browser window, and try logging in again." message. This
Object Manager uses Database Authentication.

Object Manaer log file showed following errors:

2021 2011-12-17 13:05:12 2011-12-17 13:05:13
+0900 00000006 001 003f 0001 09 SCCObjMgr_jpn 19492 4960 4936
D:\sea77\siebsrvr\log\SCCObjMgr_jpn_19492.log 7.7.2.6 [18372] JPN

GenericLog
GenericError 1 0 2011-12-17 13:05:12 (secmgr.cpp (1888) 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 2011-12-17 13:05:12 Login failed for Login name : GUESTCST

ObjMgrCTLog Error 1 0 2011-12-17 13:05:13 (ctxtmgr.cpp (3298)) SBL-SVC-00208: Please login first.

Cause

The CRC(checksum) value was somehow being corrupted. Note that setting a
CRC(checksum) for the DB Security Adapter is not supported.
For more
details, please see "Security Guide for Siebel eBusiness Applications
Version 7.7, Rev. A May 2005 > Security Adapter Authentication >
Security Adapter Deployment Options > Configuring Checksum
Validation".

Solution

Please disable a CRC for the DB Security Adapter by following steps:

1. Take a backup of siebns.dat file under the <$Gateway Server>\admin.
2.
Login via the Dedicated Client and navigate to the Administration -
Server Configuration > Enterprises > Profile and query with "DB
Security Adapter".
3. On the Profile Parameters view, set Value = 0 for the CRC parameter.
4. Restart Siebel Server service.