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 :
ObjMgrMiscLog Warning 2 0000000246ba0340:0 2007-08-09
12:00:27 (objdef.cpp (7413)) SBL-DAT-00170: The DLL 'SSCASTRL.DLL'
could not be loaded.
ObjMgrLog Error 1 0000000246ba0340:0 2007-08-09
12:00:27 (model.cpp (3963)) SBL-DAT-00227: Unable to create the
Business Service 'Audit Trail Engine'
ObjMgrBusServiceLog Warning 2 0000000246ba0340:0 2007-08-09
12:00:27 (model.cpp (5878)) SBL-DAT-00227: Unable to create the
Business Service '<?>'
ObjMgrSessionLog Warning 2 0000000246ba0340:0 2007-08-09
12:11:43 (physmod.cpp (9318)) SBL-SFR-00116: The user has cancelled
the logon request.
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
Hiafter 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 laterInformation 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).
No comments:
Post a Comment