SBL-SVR-00028: No more tasks available for this component.

Applies to:

Siebel System Software - Version: 7.8.2 [19213] and later   [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Server Common Layers - SVR
Version:Siebel 7.8

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-SVR-00028: No more tasks available for this component.

Scope

This document is informational and intended for any user.

SBL-SVR-00028: No more tasks available for this component.

Explanation

The specified component is running the maximum number of tasks configured for this server.

Corrective Action

Review the value of MaxTasks set for the component. If necessary, increase the number, shutdown the server and restart it. Or start the task on a different server.

Applies to:

Siebel System Software - Version 5.0.1 to 8.0.0.13 SIA [20448] [Release V5 to V8]
Information in this document applies to any platform.
Area(s):System Administration
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Keywords:Siebel, Thin, Clients, cannot, connect, MaxTasks, Max MT Servers, MTServers

Description

Siebel Web clients (also referred to as Siebel Thin Clients) connect to the Siebel application via the Siebel Object Manager. When configuring the Siebel Object Manager, there are parameters that can affect how many Siebel Web clients can be supported by the Siebel Object Manager. For the purpose of this Alert, the parameters that are applicable are:

• Maximum Tasks
• Maximum MT Servers

Depending on the Siebel version you are running in your Siebel environment, your users may encounter different errors and symptoms which are documented under the Possible Symptoms section below.

Occurrence

The behaviors documented in this Alert will likely occur if the Siebel Object Manager's parameters are set incorrectly.

Symptoms

For all Siebel versions 8.0:

Users who are unable to connect will encounter the following error message:

The server you are accessing is either busy or experiencing difficulties. Please close the web browser, start a new one and try logging in again.

SCBroker log will show error:

SBL-SCB-00014: All component processes are maxed out

For all Siebel versions 7.x:

Users who are unable to connect will encounter the following error message:

SBL-SVR-00028: No more tasks available for this component

and
         SBL-SWP-00121: The server you are accessing is either busy or experiencing difficulties. Please close the web browser, start a new one and try logging in again. For further support, please copy and send     the full message text to your system administrator.
or

SBL-SWP-00121: 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.

Displayed at the Siebel application level.

For all Siebel versions 6.x:

Users who are unable to connect will encounter the following error messages:

SBL-SVR-00028: No more tasks available for this component

and

We detected an Error which may have occurred for one or more of the following reasons:

We're sorry, the username or password you entered was incorrect. Please try again.

For all Siebel versions 5.x:

Users who are unable to connect will encounter the following error messages:

SBL-SVR-00028: No more tasks available for this component

Which is detailed within the .log file for the appropriate Siebel Object Manager (located under the $SIEBEL_HOME\siebsrvr\log directory.
or
The Siebel component becomes unavailable with the following error messages:

SBL-SMI-00033: The client exited without closing the SISNAPI connection

and

SBL-OSD-00098: Internal: The process exited abnormally and the Operating System could not get the exit code.

Additionally, displayed at the Siebel application level, the user might receive the error message:

Error: Unauthorized Access or Application Error.
The information you have entered is incorrect. Please try again.

Workaround

These behaviors are encountered when the Siebel Object Manager's component parameters:  Maximum Tasks or the Maximum MT Servers reaches the maximum value. The default values are shown below:

Parameter	Default Value
Maximum Tasks	20
Maximum MT Servers	1

These default values should be increased depending on the number of tasks and users. Generally for every Siebel Web client connection it is one task.

For Siebel versions 8.0:

For more information about setting these parameters and the Siebel Object Manager, refer to Siebel Bookshelf version 8.0 > System Administration Guide > Application Object Manager Administration. Please also refer to "How to Configure Siebel Object Manager (SOM) in Siebel 7.x and 8.0 (Doc ID 476830.1)"

For Siebel versions 7.x:

For more information about setting these parameters and the Siebel Object Manager, refer to Siebel Bookshelf version 7.7 > Siebel System Administration Guide > Application Object Manager Administration. Please also refer to "How to Configure Siebel Object Manager (SOM) in Siebel 7.x and 8.0 (Doc ID 476830.1)"

For Siebel versions 6.x:

For more information about setting these parameters and the Siebel Object Manager, refer to Siebel Bookshelf version 6.0 > Siebel Server Administration Guide > Application Object Manager Administration.

For Siebel versions 5.x:

For more information about setting these parameters and the Siebel Object Manager, refer to Siebel Bookshelf version 5.6 > Siebel System Administration Guide > Object Manager Administration.

History

 Checked For Relevance *********05Feb2013*********

Applies to:

Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] CHS Com/Med
Database: Oracle 9.0.1
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 3

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

Symptoms

SBL-SVR-00028, SBL-NET-01028Hi, SupportWeb,

We have encountered a question from this Monday. At some time, we can not log in the Siebel Server and we found the error message in Enterprise log file:

ServerLog    ProcessCreate    1    2006-01-10 17:16:03     Created server process (OS pid = 2187320) for Siebel Server Scheduler with task id 33857

ServerLog    ProcessExit    1    2006-01-10 17:16:03    <NoCompName>    30260     SBL-SVR-00028   Process exited with error - No more tasks available for this component

and found error message is eCommunication Log file:

GenericLog    GenericError    1    2006-01-10 17:14:49    (sciapi.cpp 7(1145) err=1801028 sys=0) SBL-NET-01028: Error in shell: SBL-SVR-00028: No more tasks available for this component

Then, We restart the Siebel Servce Service and we can log into Siebel Application , but after some hours, the error happened again. And from monday till to today, this error occured 3 times.

It is very urgency and could you please help me.

Thank you

Solution

Message 1

For the benefits of other users:

Customer encountered login error. After restarting the Siebel Servce Service, they can log in again. However, after some hours, the login error happened again.

Resolution:

It was found that customer has set the following Object Manager parameters:
MemoryBasedRecycle = TRUE
MemoryLimit = 180 means 180 Mbytes

The above parameter will cause the Object Manager to recycle on reaching a memory limit of 180 Mbytes. 180 Mbytes is too low a value to be set as a memory limit for the Object Manager to recycle. The Object Manager will get recycled even when maximum tasks is not reached. After adjusting the MemoryLimit to 600 Mbytes, the customer did not update the issue anymore.

Applies to:

Siebel CTI - Version: 7.5.3.8 [16192] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.8 [16192]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 8

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

Symptoms

During a recent deployment of Siebel 7.5.3.8/Genesys Voice Adapter 6.5.201.13, we encountered a "Call Stack" on the dedicated Siebel Communications Server. These Call Stacks were associated with 1) Problems with CTI Toolbar 2) Agents being logged out of tool bar 3) Agent calls being dropped. Some of the text below is:

- CALL STACK -
<invalid> 0x5dda484
GenModel +0x5b594
GenModel +0x10f20 = ReleaseTeleset() +0x1e70
<invalid> 0x868b57f1

This Call Stack occured 5 times during our initial deployment and subsequently was associated with these errors in the Siebel Communications Manager Logs:

1) GenericLog    GenericError    1    2005-05-31 10:53:58    (sissrvr.cpp 47(3069) err=2000028 sys=0) SBL-SVR-00028: No more tasks available for this component

2) CommSessionMgr 59455     SBL-OSD-01000   Process exited with error - Internal: The process attempted to read from or write to a virtual address for which it does not have the appropriate access

3) GenericLog    GenericError    1    2005-05-31 11:08:51    (srbqueue.cpp 6(918) err=5700005 sys=0) SBL-SRB-00005: no element in the queue

4) SComm[05/31/2005 10:24:23:555]:FATAL:SRM session handle is NULL in DoInvokeMethod() for user(BENNETS6), key(1328|429c71f8|248466b0).
SComm[05/31/2005 10:24:23:555]:ERROR:Unable to identify driver for action, profile ID=, channel string=, media type=, command=Ready, event=
SComm[05/31/2005 10:24:23:555]:ERROR:Error on invoke media manager method(InvokeCommand), input args={
DataSet = 2#18#1#13#AgentWorkMode5#1#1#1
DeviceCommand = Ready
Child property set, type = DataSet {
AgentWorkMode = 1
}
}, error=?), msg='Unable to identify driver command(Ready) among all loaded drivers.(SBL-CSR-00504)'

Our frustration is occurring because we are not able to re-create this error in our load testing environment. Since this error was associated with CTI Toolbar connectivity issues (i.e.: agents being logged out of the toolbar) and other CTI issues, we remain concerned.

Cause

After researching and checking the call Stack:
- CALL STACK -
<invalid> 0x5dda484
GenModel +0x5b594
GenModel +0x10f20 = ReleaseTeleset() +0x1e70

We could identify that the crash was happening while CSM was calling method on Genesys Gplus Driver libraries.

The customer engaged Genesys Support who has confirmed that this is a known issue.

Solution

Genesys confirmed that the issue  has been fixed in Genesys  Gplus Driver 7.x code stream and the fix was replicated into 6.5 stream.

The recommendation is to deploy the latest version (6.5.201.20). Note that the customer was using 6.5.201.13 version of the driver.

Customer worked with Genesys to get the latest Gplus Driver hot fixes.

Applies to:

Siebel Enterprise Integration Manager - Version 7.7.2.6 [18372] and later
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-3352104615.

Symptoms

EIM component in test system is generating hundreds of siebsh process, this is consuming all available memory on the server until the system crashes.
Despite the EIM jobs have been turned off, the behavior still continues.
The only way to stop this issue is to disable the EIM component definition.

What is causing this and how can be stopped?

Cause

CR 10641285

Solution

Customer was getting some errors from EIM tasks:

SBL-SVR-00028 Process exited with error - No more tasks available for this component.
SBL-EIM-00207: Unable to log in to the database.
SBL-EIM-00108: Internal error in retrieving scf parameter
SBL-EIM-00205: Failed to load the application dictionary

The only EIM tasks customer had running were the two Repeating Component Requests. Customer tried canceling both of these jobs to see if that corrected the problem, but after canceling the jobs and disabling then enabling the component definition, the EIM component still has the problem behavior.

The root cause found for the problem is CR# 10641285 for Cancelled Repeating Component Requests keep running. It is fixed in 7.5.3 fix pack, 7.8, and 8.0. Customer is on 7.7.x, so it is still a problem.
Customer ran a sql to find any queued of arctive RCR's and the results returned 11946 rows. Four of these are Active and the rest are all Queued. The four Active RCR's are all old dates. All of the others, the Queued tasks, were all created on the same date/time.
To know what component they are you can run the following SQL to get the components:

SELECT T1.ROW_ID, T1.CREATED, T1.STATUS, T1.PAR_REQ_ID,
        T2.ROW_ID PAR_ID, T2.STATUS PAR_STATUS, T3.NAME COMPONENT_NAME
        FROM S_SRM_REQUEST T1, S_SRM_REQUEST T2, S_SRM_ACTION T3
        WHERE T1.STATUS IN ('QUEUED','ACTIVE')
            AND T1.REQ_TYPE_CD='RPT_INSTANCE'       
            AND T1.PAR_REQ_ID = T2.ROW_ID
            and T1.ACTION_ID = T3.ROW_ID

Customer ran this SQL, and as expected, the component name for every task was EIM. To resolve the problem quickly, customer followed the workaround to cancel all of the tasks, restarted the server, and verified that the RCR tasks did not restart. Then customer re-enabled the EIM component, restarted the server again, and the many siebsh.exe processes were not generated, and the RCR tasks also did not restart. Customer then recreated the two repeating component requests that they usually have running continually, and have been monitoring the situation. So far, the two tasks continue to run and perform their correct functions, and no other RCRs or siebsh.exe tasks have been generated. So it appears that for the time being, the immediate issue is resolved.

Before customer upgrades to the version that has the fix for the CR 10641285, I suggest to run the SQL on a regular basis to monitor RCR and apply the workaround when needed.