SBL-SMI-00122





Applies to:


Siebel System Software - Version: 7.5.2 [16008] to 7.8 [19038] - Release: V7 to V7
z*OBSOLETE: Microsoft Windows 2000

Product Release: V7 (MidMarket)

Version: 7.5.2.100 [15252] MME

Database: Microsoft SQL Server 2000 SP 2

Application Server OS: Microsoft Windows 2000 Server SP 2

Database Server OS: Microsoft Windows 2000 Server SP 2



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



Symptoms


SBL-SMI-00122Hi
I am seeing following errors on Object Manager
logs:

"GenericLog    GenericError    1    2004-04-27
22:17:42    (somentry.cpp 9(285) err=28758 sys=0) GEN-28758: (somentry.cpp 9:
285) error code = 28758, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 =
(null)

GenericLog    GenericError    1    2004-04-27
22:17:42    (somentry.cpp 9(640) err=28758 sys=0) GEN-28758: (somentry.cpp 9:
640) error code = 28758, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null), msg4 =
(null)

GenericLog    GenericError    1    2004-04-27
22:17:42    (smimtpool.cpp 50(1483) err=2100122 sys=0) SMI-00122: Internal:
Error 28758 from SessionHandleMessage()"

I need to understand what it means.






Cause


.


Solution



Message 1


For the benefit of other readers:



The customer was seeing the following error messages in the Object Manager log files:



"GenericLog    GenericError    1    2004-04-27 22:17:42    (somentry.cpp
9(285) err=28758 sys=0) GEN-28758: (somentry.cpp 9: 285) error code =
28758, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null),
msg4 = (null)



GenericLog    GenericError    1    2004-04-27 22:17:42    (somentry.cpp
9(640) err=28758 sys=0) GEN-28758: (somentry.cpp 9: 640) error code =
28758, system error = 0, msg1 = (null), msg2 = (null), msg3 = (null),
msg4 = (null)



GenericLog    GenericError    1    2004-04-27 22:17:42    (smimtpool.cpp
50(1483) err=2100122 sys=0) SMI-00122: Internal: Error 28758 from
SessionHandleMessage()"



The “GEN-28758” error message is usually related to failing connections.
Bug ID 10448885 has been raised requesting more informative message
when this behavior happens.



The customer executed the environment verification tool (evt) on this
environment, and it requested to change some TCP parameters and the
SERVER_INACTIVE_CONN_TIMEOUT variable.



Please refer to "Environment Verification Tool (EVT) Overview (Doc ID
477105.1)" on My Oracle Support for further information regarding this
tool and "What is true benefit, if any, of changing TCP registry
parameters as recommended by EVT? (Doc ID 499134.1)" for details about
TCP parameters change.



After these, the customer re-started the Siebel Server machine and the messages have gone away.



Thank you.








Applies to:


Siebel System Software - Version: 7.5.3 [16157] to 8.1.1.4 [21225] - Release: V7 to V8
Oracle Solaris on SPARC (64-bit)

Product Release: V7 (Enterprise)

Version: 7.5.3 [16157]

Database: Oracle 9i

Application Server OS: Sun Solaris 8

Database Server OS: Sun Solaris 8



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



*** Checked for relevance on 04-May-2011 ***



Symptoms


SBL-SMI-00122Users are getting session timeout message randomly. The error in the task log
is:
SBL-SMI-00122: Internal: Error 28758 from SessionHandleMessage()

We need to fix
this ASAP.






Cause


Environment specific 


Solution


Customer determined the timeouts appear to be related to the application
object manager parameter, SISNAPI Connection Maximum Idle Time (alias
ConnIdleTime) which had been set to 0 and timing out after 30 seconds



Under 7.5.2, the behavior for ConnIdleTime = 0 or -1 meant, no timeouts.



Under 7.5.3, setting ConnIdleTime

- between 0 and including 30 = 30 seconds timeout.

- by setting it to -1, this means there is no timeout which is not
something you want either especially if a firewall is present.



It is recommended where there is a firewall between the application and
web server, and firewall timeout is set: the value should be set to a
value slightly less than the firewall timeout value.

Therefore, if firewall has a timeout value of 3600 seconds (1 hour),
then the ConnIdleTime parameter should be less than 3600 seconds. The
recommended value for the ConnIdleTime parameter is between 300 seconds
and 3600 seconds.



Your setting will be based on your business needs.



In summary:

1- Set it ONLY for Application ObjMgr's and EAIOBJMgr's

2- Set it ONLY when Resonate is being used for load balancing Siebel Server's

3- Do NOT set it for components that belong to "System Management" group.

4- Value should always be less than firewall timeout.

5- Optimal value lies between 300 and 3600



More information can be found on ConnIdleTime in BookShelf's Server Administration Guide for 7.5.3

תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of ...
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima...
המשך לקרוא

SBL-SVC-00150

Applies to: Siebel CRM - 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: IBM DB2/UDB 7.2 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: IBM AIX 4.3.3 This document was previously published as Siebel SR 38-1153677971. Symptoms SBL-SVC-00150In callcenter (development environment) Group News administration > All News, when the ‘Status’ field of a news story is changed from ‘Submitted’ to ‘Completed’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Completed’. Rule validation failed: ‘[Total Approvers] = 0’ (SBL-SVC-00150) When the status field of a news story is changed from ‘Submitted’ to ‘Pending Approval’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Pending Approval’. R...
המשך לקרוא