SBL-SEC-00003: An error occurred checking the checksum of the security adapter library.

Applies to:

Siebel System Software - Version 7.7.2.6 [18372] to 8.2.2.2 SIA[23016] [Release V7 to V8]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

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

Symptoms

SBL-SEC-00003
I am having trouble with the security adapter checksum.

Background:

When using the URL http://<siebsrvr>/service_enu I get the ‘The server you are trying...’ message. Service_enu is using ADSI authentication.

The resultant web server log file contains: Login failed for Login name : GUESTCST. I have verified the GUESTCST login is working. The log file also contains: An error occurred checking the checksum of the security adapter. Log file is attached to this SR.

I reviewed Configuring Checksum Validation on the Siebel support website and generated. I updated the CRC value for the ADSISecAdpt in the Profile Configuration. I then synchronized the Siebel components, restarted the Siebel services, and performed an iisreset on the Siebel web server. But I am still getting the error message.

Questions:

I used the following to generate the checksum on the apps server: checksum –f sscfldap.dll
Is there a different dll that I should be using? Of course, I used the returned value and not the value in the Siebel SupportWeb example.

How else can I troubleshoot this issue?

Cause

Change Request 12-1JXJI1L has been opened as Documentation Enhancement Request

Solution

Message 1

For the benefit of other readers,


Customer was receiving the error message below in Siebel Web Server Extension and Siebel Object Manager log files for version 7.7.x after enabling Security Adapter Checksum (CRC):

“SBL-SEC-00003: An error occurred checking the checksum of the security adapter library. Please contact your system administrator for assistance.”

We were able to confirm that above error message was related with CRC by disabling checksum checking. This is possible by setting CRC parameter of Security Adapter profile to 0 (zero).

The following command was being executed:

checksum –f sscfldap.dll

This behavior was resolved by using the correct Security Adapter library. Customer was using Siebel ADSI Security Adapter, so the correct library is sscfadsi.dll, not sscfldap.dll. Here is the correct command:

checksum –f sscfadsi.dll

Customer noticed that document Security Guide for Siebel Business Application for version 7.7, Rev. A, chapter 6: Security Adapter Authentication, section Security Adapter Deployment Options, under Configuring Checksum Validation uses sscfldap.dll library, and it does not have any reference to sscfadsi.dll library or custom library.


Change Request 12-1JXJI1L has been opened as Documentation Enhancement Request to provide a note regarding which libraries to use based in the Security Adapter used.


Thank you,

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.

 

 

 

Applies to:

Siebel System Software - Version 7.5.3 [100] and later
Siebel Call Center - Version 7.5.3 [100] to 8.1.1 [21112] [Release V7 to V8]
Information in this document applies to any platform.
*** Checked for relevancy 30-Jan-2013 ***

Symptoms

Customer updated their Fix Pack level and now are getting the following error in both their SWSE and AOM logs:

SBL-SEC-00003: An error occurred checking the checksum of the security adapter library. Please contact your system administrator for assistance.

Customer has regenerated the checksum values as required and discussed in Bookshelf.

Cause

The checksum value was somehow being corrupted through the copy and paste process.  Manually entering in the generated value worked fine.

Solution

We found that the checksum command does not work properly when it is copied and pasted. When we typed it in manually, the command ran successfully and generated a new checksum value. When this checksum is entered into the CRC parameter in the security adapter profile and the Siebel services restarted, the application began working correctly.

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 System Software - Version: 7.7.2.8 SIA [18379] and later   [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2.8 [18379] Pub Sect
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

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

Symptoms

Hello there,

The following components stopped responding unexpectedly:

Business Integration Manager                
Communications Outbound Manager
Workflow Process Manager  
Workflow Recovery Manager
Workflow Process Batch Manager

This is hampering the testing of EAI release scheduled for Production soon. Please help.

Regards,
Venkatesh

Solution

For the benefit of other users,

The customer was reporting that a number of components in their environment were showing as Unavailable. This behavior only impacted a single Siebel Server where these components were running.

Initial discussions highlighted the fact that the components which were showing as Unavailable were all running on an LDAP Security Adapter. As the customer has had problems in the past with checksum validation on the LDAP Adapter they re-generated the checksum for the LDAP libraries and set this on the LDAPSecAdpt security adapter profile (in Administration - Server Configuration > Enterprises > Profile Configuration). This still did not resolve the behavior and the components continued to show as Unavailable following the Siebel Server startup.

In order to investigate further the customer was directed to increase the log levels for one of components and to then perform a shutdown/startup of the component through the srvrmgr utility. This was done but the component continued to show as 'Unavailable' and so the logs were reviewed. The following errors were identified :

SecMgrLog    Debug    5    0    2007-07-20 19:01:16    SECMGR: DBSecAdpt_SecAdptDllName=sscfsadbmfcext
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    stored CRC = '85600b19'
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    computed CRC = '1e12de85'
GenericLog    GenericError    1    0    2007-07-20 19:01:16    (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.
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    SecAdptName = DBSecAdpt
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    SecAdptMode = 0
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    SecAdptDllName = sscfsadbmfcext
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    PropagteChange = FALSE
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    computed checksum of security adapter library = '1e12de85'
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    HashUserPwd = FALSE
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    HashDBPwd = FALSE
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    HashAlgorithm = RSASHA1
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    bMFCShell = TRUE
SecMgrLog    Debug    5    0    2007-07-20 19:01:16    datasourcename = ServerDataSrc
GenericLog    GenericError    1    0    2007-07-20 19:01:16    (secmgr.cpp (2209) err=7000003 sys=0) SBL-SEC-00003: An error occurred checking the checksum of the security

This excerpt from the log file for the WfProcMgr component indicated that the component was actually using the DBSecAdpt (database authentication) rather than the expected LDAPSecAdpt. This was discussed internally and confirmed to be correct by the customer.

As the error messages indicated that the checksum being used on the profile was incorrect the customer regenerated this using the following command and set it on the DBSecAdpt profile :
checksum -f libsscfsadb.so

Note : Setting a checksum against for the DBSecAdpt is not supported as per the information in the Siebel Security Guide.

The checksum was generated against the sscfsadb.dll as this was the library which had been set against the 'Security Adapter Dll Name' parameter on the profile, however the above command returned the CRC value '85600b19'. This was the value reported in the log file as already being stored on the DBSecAdpt profile.

Closer inspection of the trace excerpt confirmed that whilst the profile was showing sscfsadb.dll as the Security Adapter dll, the log file was showing sscfsadbmfcext.dll as the library being used. In view of this the customer performed a checksum generation against this file instead (as library names are converted on UNIX) :
checksum -f libsscfsadbmfcext.so

This returned the value '1e12de85' which was being reported as the computed CRC in the log file.

The customer therefore set this as the CRC value on the DBSecAdpt profile, restarted the Siebel Server, and all of the previously unavailable components started correctly.

Three new Change Requests were raised as a result of this investigation :
CR #10528106    Documentation for the bMFCShell parameter
CR #10528107    Errata in Security Guide regarding UNIX libraries
CR #10528108    Implementing checksum validation for DBSecAdpt