SBL-GEN-00003

pplies to:

Siebel CTI - Version: 7.5.3.11 [16199] and later   [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.5.3.11 [16199] DEU
Database: Oracle 9.2.0.6
Application Server OS: Sun Solaris 2.8
Database Server OS: Sun Solaris 2.8

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

Symptoms

We get Errors when we connect to Siebel-CTI with the CTI Toolbar. Sometimes it works, but sometimes (ca. 10%) not.

GenericLog    GenericError    1    2006-03-01 08:49:52    (srbroute.cpp 52(6729) err=5700061 sys=0) Prozess CommSessionMgr auf Siebel Server dab-cti01 beendet
GenericLog    GenericError    1    2006-03-01 08:49:52    (srmconn.cpp 2(2976) err=5700061 sys=0) SBL-SRB-00061: Prozess (null) auf Siebel Server (null) beendet
GenericLog    GenericError    1    2006-03-01 08:49:52    (srmconn.cpp 2(2630) err=5700061 sys=0) SBL-SRB-00061: Prozess (null) auf Siebel Server (null) beendet
GenericLog    GenericError    1    2006-03-01 08:49:52    (srmconn.cpp 2(2244) err=5700061 sys=0) SBL-SRB-00061: Prozess (null) auf Siebel Server (null) beendet

I looked for the Task ID of the crashed Communications Session Managers (Error code SBL-GEN-00003) in order to check out the Logfiles at the CTI Server Machine, but there are no logfiles for the specified Task ID at the CTI Server! Nor for this one Crashed Task, eihter for the other crashed tasks.

Cause

Customer had set a higher value (greater than 1) to MaxMTServer and MinMTServer parameters for the Communication Session Manager component. They were encountering the behaviour where when the agent logs into the Application with Communication Toolbar enabled, it would throw error. This was intermittent. Customer was using the Aspect CTI Driver.

Solution

The Aspect driver can not handle more than one process. Expert Services suggested the customer to set MaxMTServer = 1, MinMTServer =1 and MaxTasks = 200. Once after re-setting these parameters on the Communication Session Manager component, the error was resolved.