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 CRM - Version 7.5.3.4 [16180] and later
Information in this document applies to any platform.
*** Checked for relevance on 29-JAN-2013 ***

Symptoms

Customer is trying to implement the LDAP security adapter (LDAPSecAdpt) for use with the Siebel application.  The application object manager is failing to bring up a login screen and the following error is appearing in the log file:

SBL-SEC-00102: Error loading the security adapter library. Please contact your system administrator.

The desired behavior is that the security adapter library should load successfully and a login page be presented to the user.

Cause

This behavior occurred because the server had to be physically rebooted after the installation of the IBM LDAP Client and/or GSKit software.

Solution

After some investigation, we determined that it is necessary to physically reboot the server after the installation of the IBM LDAP Client or GSKit software. Once this was done, everything worked correctly.

This requirement is not documented in the Siebel Bookshelf documentation.
Document Enhancement Request Bug:10575898/ 12-1UX6R4P to update the Security Guide with this information.

Applies to:

Siebel Financial Services CRM - Version 8.0.0.1 [20408] to 8.1.1.2[21215] [Release V8]
Information in this document applies to any platform.
***Checked for relevance on 03-Jan-2011***
***Checked for relevance on 23-Nov-2012***

Symptoms

We are trying to implement a Custom Security Adapter to perform application login authentication. We have downloaded the sample SDK from support web, compiled and deployed to our testing environment. We have also configured one of the AOM to test out the compiled security adapter. Unfortunately, we are unable to load the application login page. Based on the attached log file, the error message is as below:

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

Cause

Incorrect setup/configuration on the custom security adapter named subsystem and configuration file or security adapter library compilation issue.

Solution

Verify the following is correct.
- Parameter setting in custom security adapter named subsystem
- Setting in the configuration file reference in ConfigFileName parameter in custom security adapter named subsystem
- LIBPATH environment variable setting

Setup the sdk custom adapter authentication and configuration in-house and successfully reproduce the issue when using the same compiler (g++) and makefile as customer.
Further research on these and found the issue on the sdk compilation. The makefile from customer is like this.

libsampsdk.so: secsamp.o secutil.o
g++ secutil.o secsamp.o -o libsampsdk.so

secsamp.o: secsamp.cpp secutil.h ssecurity.h
g++ -c secsamp.cpp

secutil.o: secutil.cpp secutil.h ssecurity.h
g++ -c secutil.cpp

Note that after compiling the secsamp.cpp and secutil.cpp with g++ -c swtich and option, it will create the .o file. Once this dependencies (secsamp.o and secutil.o) for the shared object secsamp.so have been created, there is need to invoke the linker using additional switch and option to create a dynamic library. So modify the makefile as below and recompile the sample code.

libsampsdk.so: secsamp.o secutil.o
g++ -fPIC -shared secutil.o secsamp.o -o libsampsdk.so

secsamp.o: secsamp.cpp secutil.h ssecurity.h
g++ -c secsamp.cpp

secutil.o: secutil.cpp secutil.h ssecurity.h
g++ -c secutil.cpp

Using this newly compiled library file, object manager and application succesfully loaded and login works fine.

pplies to:

Siebel Communications Service - Version 8.0.0.2 [20412] to 8.1.1.8 SIA [23012] [Release V8]
Information in this document applies to any platform.

Symptoms

Siebel version 8.0 application does not start when the LDAP security adaptor is configured at enterprise level, although the mandatory IBM LDAP client version 6.0 has been installed. The following error messages are logged as a result,
a) SBL-SEC-00102: An error occurred loading the security adapter library. Please contact your system administrator for assistance.
b) SBL-DAT-00562: An error occurred loading the security adapter library. Please contact your system administrator for assistance.

Cause

The Siebel security adaptor library aka. libsscfldap.so could not be loaded because of the installation and configuration (LD_LIBRARY_PATH) of the 64bit libraries that are part of the IBM LDAP client software.

Solution

Ensure that the LD_LIBRARY_PATH in the siebenv.sh shell script only references the 32-bit libraries of the IBM LDAP Client version 6.0 because this ensures that the Siebel modules, which are based on 32-bit processing - do not conflict with the 64-bit library versions of the IBM LDAP Client software - as documented in Siebel Bookshelf version 8.0 > Siebel Security Guide > Security Adapter Authentication > Installing LDAP Client Software > Configuring the siebenv.csh and siebenv.sh Scripts for the LDAP Client - where it states, "Siebel supports only the IBM 32-bit LDAP Client so you can use only the 32-bit LDAP Client libraries with your Siebel applications."

Please follow the following steps, also outlined in the Siebel Bookshelf reference,
1) Navigate to the Siebel server root installation directory
2) Open a text editor on your UNIX system e.g. vi
3) For both the shell script files; SIEBENV.SH and SIEBENV.CSH edit them and ensure that ONLY the location to the IBM LDAP Client 32bit libraries are referenced.

NOTE: The 64-bit libraries can be explicitly identified from the directory path naming convention - that is,
32-bit  =  /opt/IBM/ldap/V6.0/lib
64-bit  =  /optIBM/ldap/V6.0/lib64

Applies to:

Siebel CRM - Version 8.0.0.1 SIA [20408] and later
Information in this document applies to any platform.

Symptoms

Siebel Login Page fails to display

ERRORS
1) 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.[08:22:46]
2) SBL-SEC-00102: An error occurred loading the security adapter library. Please contact your system administrator for assistance.

Cause

The IBM LDAP Client installation on UNIX defaults to /opt/ibm/ldap/V6.0.
The environment variables in the SIEBENV.SH referenced the wrong directory for the IBM LDAP libraries - namely /opt/ibm/ldap/v6.0/lib as opposed to /opt/ibm/ldap/V6.0/lib.
Because the resolution of filename paths on UNIX systems is case sensitive the difference between v6.0 and V6.0 caused the error.
Bug 14651929 has been logged requesting that the Security Guide be updated accordingly under Security Adapter Authentication > Process of Installing and Configuring LDAP Client Software > Configuring the siebenv.csh and siebenv.sh Scripts for the LDAP Client.

Solution

Modify the SIEBENV.SH to reference /V6.0/lib as opposed to /v6.0/lib

Applies to:

Siebel CRM Call Center - Version: 8.1.1.5 [21229] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

=== ODM Issue Clarification ===
This is in relation to a 8.1.1.5 siebel enterprise environment deployed on a RHEL 5.5 linux platform (64-bit).


When accessing the EAIObjMgr_enu component fails when using an external Java based command line utility, which is accessing the EAI component via EAI_enu SWSE web server.

Looking at the EAIObjMgr component we can see mainly authentication errors like the following error messages:
"An error occurred loading the security adapter library. Please contact your system administrator for assistance.(SBL-DAT-00562)" and before this error ".....err=4587622....SBL-SEC-00102..."

Cause

=== ODM Cause Determination ===

Executed: strace against start_server and EAI OM PID. There was no evidence that <custom adapter>.so lib was loaded.

Executed: file <custom adapter>.so
This showed: ELF 64-bit LSB shared object, AMD x86-64, version 1 (SYSV), not stripped

Executed: ldd -v <custom adpater>.so
This showed:
>>>
      libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002b536dd51000)
      libm.so.6 => /lib64/libm.so.6 (0x00002b536e051000)
      libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002b536e2d4000)
      libc.so.6 => /lib64/libc.so.6 (0x00002b536e4e3000)
      /lib64/ld-linux-x86-64.so.2 (0x0000003d04c00000)

      Version information:
      ./cdetsnopassword.so:
              libc.so.6 (GLIBC_2.2.5) => /lib64/libc.so.6
...
<<<

=== ODM Cause Justification ===

Looking at the file and ldd output, we can see that 64-bit libraries are used:

Siebel product is only 32-bit and will only work with 32-bit libraries.

Solution

=== ODM Solution / Action Plan ===

Compile the custom security adapter as per SDK documented compile commands.
Also ensure that modifications are implemented as per published article: 1062497.1 - Changes to Siebel Custom Security Adapter SDK in Siebel 8.1.1
Also, if on a 64-bit operation system,  ensure to modify the compiler instructions to compile in 32-bit mode. There could be different ways this can be done pending on the OS vendor. For any clarification please consult with the OS vendor support.

In this specific case the following compiler instructions helped to resolve the issue.
g++ -m32 -c -fPIC secsamp.cpp
g++ -m32 -c -fPIC secutil.cpp
g++ -m32 -fPIC -shared secutil.o secsamp.o -o <custom security adapter>.so
Please note, Oracle  is providing the SDK and compiler instructions solely as a convenience to our customers and
Oracle  makes no warranties or representations of any kind regarding the
results customers may achieve by using the SDK. Siebel is not responsible
for any failure of any security adapter written using the SDK.

Check with file and ldd command (library dependency check on Linux) to ensure no 64-bit library is being used.
For example in this case the output after compiling in 32-bit mode confirmed that there was no 64-bit library involved.
$ ldd <custom security adapter>.so
linux-gate.so.1 =>  (0xffffe000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xf7e82000)
libm.so.6 => /lib/libm.so.6 (0xf7e5b000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf7e4f000)
libc.so.6 => /lib/libc.so.6 (0xf7d09000)
/lib/ld-linux.so.2 (0x00473000)

Stop the siebel application server service.
Replaced this on the siebsrvr/lib
Start the siebel application server service

Test the siebel application authentication process.

Applies to:

Siebel Wireless - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Server SP 4
Database Server OS: Compaq Tru64 UNIX

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

Symptoms

SBL-SFR-00118We tried to synchronize handheld device with mobile client for the first time and got error message as follow:

10:52:03     INFO: 2003 m. spalio 21 d. 10:51
10:52:03     INFO: Attempting to login using Companion Sync.
10:52:03     INFO: User = gvilius
10:52:04     INFO: TXN Error Level = 1
10:52:05     INFO: Connected to device. : Message ID = 304
10:52:05     INFO: Checking for Local Database
10:52:05     INFO: C:\sea752\client\bin\ENU\salesce.cfg
10:52:05     INFO: ENU
10:52:06     INFO: Cfg file is loaded. : Message ID = 291
10:52:06     INFO:     Data Source = Local
10:52:06     INFO:     Connect String = C:\sea752\client\local\sse_data.dbf -q -m -x NONE -gp 4096 -c40m -ch60m
10:52:07     ERR: A newer version of software is required. Press Yes to upgrade now or press No to continue.

Component Version Information:
Component: Siebel Sales CFG__ENU, Current Version: 0.0, Minimum Version: 100, Maximum Version: Any Version
(SBL-SFR-00118)

Cause

Configuration/ Setup

Solution

Message 1

For the benefit of other readers:

The customer tried to synchronize handheld device with mobile client’s local database for the first time and received the following messages:

10:52:06     INFO: Cfg file is loaded. : Message ID = 291
10:52:06     INFO:     Data Source = Local
10:52:06     INFO:     Connect String = C:\sea752\client\local\sse_data.dbf -q -m -x NONE -gp 4096 -c40m -ch60m
10:52:07     ERR: A newer version of software is required. Press Yes to upgrade now or press No to continue.

Component Version Information:
Component: Siebel Sales CFG__ENU, Current Version: 0.0, Minimum Version: 100, Maximum Version: Any Version
(SBL-SFR-00118)

Per the error messages, a new upgrade kit had been distributed and the version checking avoided the synchronization. As this was a Development environment, the customer commented the “ComponentName” parameter in the [Siebel] section of the *.CFG file to avoid the version checking functionality.

After this, the customer received the following messages in the Syncmanager_Log.txt file:
...
15:41:50     WARN: Could not read AppBinDir from device registry. Proceding with install using default install directory.
...
15:42:43     INFO: Processing transactions. : Message ID = 26
15:42:44     ERR: Rapi retured S_FALSE.
15:42:44     ERR: CreateProcessFailed
15:42:44     ERR: Error detected while communicating with the device. Sync cannot continue.
Please close sync, disconnect from the device and reconnect.
Perform sync again.

<Continued 1/2>

Message 2

<Continued 2/2>

15:42:45     ERR: One or more of your handheld transactions have failed. Please make the necessary changes and synchronize again. : Message ID = 13

The first warning message indicated that the Siebel Handheld Application was not installed successfully in the handheld device. And the remaining error message indicated that the communication between the synchronization program in the client machine and the handheld device could not be established successfully.

The customer re-installed the Siebel Handheld Application in the handheld device and the synchronization worked fine.

Thank you.

Applies to:

Siebel Remote - Version: 8.0.0.5 SIA [20420] to 8.1 [21039] - Release: V8 to V8
Information in this document applies to any platform.

Symptoms

The requirement was to use Siebel anywhere to distribute new srf to local users.
To accomplish that we followed following steps:
Created an upgrade kit, Siebel Client Repository File__ENU 1, having Upgrade Kit Components Siebel Client Repository File__ENU and having Upgrade Kit Items Titled: 1. Install Siebel SRF file(ENU) and 2. Generate browser script and having Upgrade Kit Item Parameters 1. File Name and 2. Destination


After that I created Upgrade configuration Siebel Client Repository File__ENU 1 and added Upgrade Component : Siebel Client Repository File__ENU, added an employee USER1 and distributed it.

Now when I login as USER1 to dedicated client I do get a message A newer version of software is required. Press Yes to upgrade now or press No to continue.
When I press Yes nothing comes up and when I press no I get read only client

Cause

Based on the log file attached we and see that it properly detects the upgrade kit:

Upgrade Component: Siebel Client Repository File__ENU, Min Version: 1, Max Version: 1, Current Version: 0
UpgradeLog UpgradeInfo 3 000000024b700668:0 2010-02-08 16:43:14 An upgrade to the component (Siebel Client Repository File__ENU) is requires upgrade. Its current version is 0. The required new version should be 1.
ObjMgrSessionLog Error 1 000000024b700668:0 2010-02-08 16:43:15 (upgchkvr.cpp (184)) SBL-SFR-00118: A newer version of software is required. Press Yes to upgrade now or press No to continue.

Component Version Information:
Component: Siebel Client Repository File__ENU, Current Version: 0, Minimum Version: 1, Maximum Version: 1
And it properly locates the kit:

The above error message indicates there was an issue with the filesystem.

Solution

The problem was due to incorrect filesystem.
They were able to to resolve the issue by changing the File System
FileSystem = C:\PROGRA~1\Siebel\8.0\WEBCLI~1\bin\att

To

FileSystem = \\ps001\FS\att

After making the above changes they were able to download the upgrade kit.

References

NOTE:475727.1 - My client is getting unable to download the upgrade kit... why do I get these error messages when attempting to download an upgrade kit?
useful document

Applies to:

Siebel Remote - Version: 7.7.2.6 [18372] and later    [Release: V7 and later]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2.6 [18372]
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Sun Solaris 8

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

Symptoms

SBL-SFR-00117, SBL-SEC-10001Hi,

We're about to introduce Danish mobile web clients but we ran into some problems. From a fresh client installation, I open up the danish login window, enter username and password and choose to connect to "Local". (I have not yet downloaded a local dbf file). I get the error message "Wrong user name and password. Please check the spelling and try again." The log file displays the following:
2021 2006-09-04 13:30:06 2006-09-04 13:30:20 +0200 00000004 001 003f 0001 09 siebel 3984 1324 C:\Sea770\client\log\siebel.log 7.7.2.6 [18372] DAN

ObjMgrLog    Error    1    0    2006-09-04 13:30:06    (wccon.cpp (2025)) SBL-SFR-00117: Den lokale Siebel-database blev ikke fundet. Vil du tilslutte til Siebel Remote-serveren for at initialisere den lokale database?

GenericLog    GenericError    1    0    2006-09-04 13:30:06    (secmgr.cpp (2288) err=7010018 sys=126) SBL-SEC-10018: 1%

GenericLog    GenericError    1    0    2006-09-04 13:30:06    (secmgr.cpp (2360) err=7010001 sys=0) SBL-SEC-10001: Der opstod en intern fejl i godkendelsesundersystemet i Siebel-programmet. Kontakt systemadministratoren for at få hjælp.

I'm expecting the message "Local database was not found, do you wish to connect and download? YES/NO". It works fine for our ENU, SVE and ITA clients, but not the Danish. We have tested on several different computers, but the error is the same.
Please advise.

Cause

Change Request #12-1FZ5FBC

Solution

Message 1

For the benefit of other readers

The customer was using the Danish 7.7.2.6 Mobile Web Client. When connecting to the Local Database for the first time, it failed to perform the synchronize steps to download the local database.

Change Request #12-1FZ5FBC has been opened to address this as a Product Defect.

The workaround is to initialise the Local Database by running the Remote Icon that executes the ‘siebelsync.exe’ executable.

Regards,

Applies to:

Siebel Tools - Version: 7.7.1 [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server
Database Server OS: Microsoft Windows 2000 Advanced Server

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

Symptoms

SBL-SFR-00117, SBL-DCK-00182, SBL-SEC-10001Hi,

We are facing issues with the tools after initializing the local extract. We were able to connect Tools to sample database and once we initialized the local extract , we were not able to connect Tools to the Sample Database or Local Database.
Afetr starting the tool, it will ask for username/ password and then it opens for a moment and disappears immediately.


Other info:

Oracle Version : 9.2.0.4 (Server & Cleint)
Siebel Version - 7.7.1 with Hotfix

Thanks,

Solution

For the benefit of other readers

The following workaround has been found for the Tools crash.

1) Edit the "SSD Local Db default instance" DSN
2) Put some junk characters in the "Database name" under Database Tab. Please find the Screen Shot attached.
3) Once Connected with the tools remove the junk characters for the Check-in/check-out.

Investigations have shown that Tools 7.7 makes a ODBC connection during startup. This was not the case for previous versions.

In a working env the ODBC connection will connect to the server db. In the customer case with the error Tools tries to connect with the ODBC to the local db and crashes then.


As this issue was not reproducible inhouse, no change request has been logged. If you are affected by this error, please log a service request in Oracle Support

Thank you

Applies to:

Siebel System Software - Version: 8.0 [20405] and later   [Release: V8 and later ]
Information in this document applies to any platform.
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Sybase 11
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-3417423501.

Symptoms

Hello together,

I have problem loging to the Local Database. It is working with the Sample.
I can start the Tools application, but not the Client Application.
There is an Error message like:
"08001 (-82): [Siebel Database][Adaptive Server Anywhere] Unable to conect to the database server: Unable to start the specified Database: failure code 16"

Similar message comes when trying to test the connection from the ODBC Driver:
Connection failed: Unable to start the specified Database: failure code 16

Thanks in advance

Solution

For the benefit of other users,

The customer was reporting that their application was returning errors when they attempted to logon. The customer was reporting the presence of the following error message in their client .log files :
"08001 (-82): [Siebel Database][Adaptive Server Anywhere] Unable to conect to the database server: Unable to start the specified Database: failure code 16"

Following discussions it was confirmed that the customer was able to login to their Tools installation and to their Sample database but any attempt to login to their extracted local database returned an error. The error had changed in nature and now appeared as a username/password failure. It was established that the local database could be started and logged into using the supplied username/password and so increase logging was put in place as per <DocID 475587.1 - How should client-side logging be set ?>.

Viewing the log file generated from the fresh login attempts showed the following new error messages :

Checks were made for the SSCASTRL.DLL in the %SIEBEL_CLIENT_ROOT%\BIN directory an on the \BIN directory of the server. The customer was directed to test with a vanilla .srf after they indicated that they had enabled Audit Trail in the current siebel.srf. When running with the vanilla .srf, effectively backing out the enabling of Audit Trail through Siebel Tools, it was confirmed that they could login correctly without encountering this error.

A review of Siebel Bookshelf confirmed that Audit Trail functionality is now enabled through the setting of the EnableAuditTrail system preference rather than through Tools changes to the Audit Trail Business Service as per the information in the Application Administration section of Siebel Bookshelf prior to Siebel 8.0.

From Siebel 8.0 onwards the Application Administration guide accurately reflects the change in implementation methods for Audit Trail.


Jon Mayall
Oracle Global Product Support
Keywords : SBL-DAT-00227, Audit Trail, mobile, client, login, error, business, service, EnableAuditTrail

Applies to:

Siebel Tools - Version: 7.7.1 [18306] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.1 [18306]
Database: Oracle 8.1.7
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP-UX 10.0

This document was previously published as Siebel SR 38-1594391212.
Checked for Relevance "Feb-14-2011"

Symptoms

Hi
after upgrading from 7.5.2 to 7.7.1 we experienced difficulties with accesing any of the configured views through the web client. We could access all of the views from the dedicated client but got server experiencing difficulties through the web client. The vanilla views worked fine through either.
We have now turned scripting off on the server and are working our way through the scripts but we still cannot access accounts. When we access accounts we get the server experiencing difficulties error and are thrown out to the login screen we have enclosed the server 2003 application event logs and the siebel logs.
Thanks

Cause

Script on Query event with scripting disabled causes crash.

Solution

For the benefit of other users:

This customer was encountering two different problems

1) Testing with scripting enabled – the application was failing to start.
Using increased logging on the object manager via the event parameter, it was found that there was scripting on the Application_Start event which was failing

ObjMgrLog    Error    1    0    2004-11-24 19:22:40    (app.cpp (1520)) SBL-EXL-00151: Please Contact Your System Adminstrator They must define the Help File Path in the LOV LIST
ObjMgrSessionLog    Warning    2    0    2004-11-24 19:22:44    (physmod.cpp (8658)) SBL-SFR-00116: The user has cancelled the logon request.

Once the customer reviewed their requirements and corrected the scripting logic, the problem was resolved.

2) Testing with scripting disabled – when any Account view was access, the object manager or dedicated client crashed.
This was found to be a product defect - if there is scripting in the BusComp_Query event of a business component (in this case the Account business component) and with scripting disabled in the cfg file (when testing with the dedicated client), the application crashes when you navigate to the Account views. Change Request 12-QZ09RD has now been logged to report this.
This is the call stack generated as a result of the crash.

- CALL STACK -
sscfel +0x4c9f = CSSELIface::ForwardEvent() +0x1f
sscfel +0x4e4c = CSSELIface::ForwardEvent() +0x3c
sscfel +0xac3c = CSSELBusCompIface::OnQuery() +0x3c
sscfom +0x288bc = CSSBusComp::EventQuery() +0xec
sscfom +0x2bf7d = CSSBusComp::Execute() +0x69d
sscaswbc +0x4eb3a = CSSSWEFrame::Populate() +0x48a


keywords: script, scripting, VB, eScript, EnableScripting, Query, BusComp_Query

Applies to:

Siebel Tools - Version 8.1.1.7 SIA [21238] and later
Information in this document applies to any platform.

Symptoms

We have upgraded our Siebel application from version 7.5.3.17 to version 8.1.1.7. When we use a dedicated client and a standard SRF file we are able to log in Siebel Financial Service application without issue. However when we try to launch our customized Siebel application using our customized SRF file we cannot log in. We get the following error:
- - -
The user ID or password that you entered is incorrect.
Please check the spelling and try again.
- - -

A review of the log file reveals the following errors:
- - -
ObjMgrSRFLog Warning 2 000000024fa20dc0:0 2012-05-03 08:54:57 (cdf.cpp (2614)) SBL-DAT-00144: 'Class' nommé 'CSSAuditTrailService' introuvable. Cet objet est inactif ou inexistant.

GenericLog GenericInfo 3 000000024fa20dc0:0 2012-05-03 08:54:57 [AUDIT_LOG]: Session audit cache cleaned.

ObjMgrSRFLog Warning 2 000000024fa20dc0:0 2012-05-03 08:54:57 (model.cpp (5970)) SBL-DAT-00144: '' nommé '' introuvable. Cet objet est inactif ou inexistant.

ObjMgrSessionLog Warning 2 000000024fa20dc0:0 2012-05-03 08:55:37 (physmod.cpp (9452)) SBL-SFR-00116: Demande de connexion annulée par l'utilisateur.
- - -

Cause

CSSAuditTrailService is the class on which is based the business service 'Audit Trail Engine'. However this BS is obsolete in version 8.0 and higher. This matter is discussed in Note 739988.1.

In their repository the customer had a custom application object and this one had an active application service event child object that called this obsolete BS:
- - -
Name: Start
Event Name: Start
Business Service: Audit Trail Engine
Method Name: Start
Inactive: FALSE
- - -

It was the cause of the issue observed.

NOTES:

- In a standard Siebel repository version 8.1 SIA the class CSSAuditTrailService is inactivated ('Inactive' property set to TRUE).
- If you review standard Siebel application objects, for example 'Siebel Financial Services' or 'Siebel Automotive' you will see that have a similar application service event child object but this one is inactive.

Solution

The issue was resolved when the 'Start' application service event child object defined for the custom Application object was inactivated.
NOTE: Since version 8.x, Audit Trail can be enabled or disabled using the EnableAuditing system preference in the System Preferences view (Site Map > Administration - Application > System Preferences). This matter is documented in the Bookshelf (Siebel Applications Administration Guide > Audit Trail > Enabling and Disabling Audit Trail).

References

NOTE:739988.1 - Unable to create the Business Service 'Audit Trail Engine'