Siebel Administration >  SBL-SRB-00041: can't do SISNAPI handshake

SBL-SRB-00041: can't do SISNAPI handshake

These error messages can be reported along side the above error. Follow the recommendations below to troubleshoot all of these error messages.

Note: SISNAPI is Siebel Systems Inc. internal communication protocol. An error in this layer generally means that network communication between the entities involved is not functioning correctly.

Cause

This error is reported when an attempt to establish communication with a Siebel application server or server component running on it fails. The reasons for this failure could be one of many. Below is a list of a few of these reasons:

Component A is being contacted but

It is not enabled
If it is enabled it is not running
If it is enabled and it is running, it does not have any more tasks left to service the above request.
Component A is expected to be running on port # XYZ, but it actually is running on another port.

In some situations, for one component to launch an instance of another server component the request is handled by two key server components. Both these components are part of the "System Management" component group. If these components are not functional (running) errors of the above nature can be reported.

Server Request Broker (SRBroker)
Server Request Processor (SRProc)
Diagnostic Steps

Is the Siebel Server service running?

If the error is reported while a zero foot print client session is initiated, it manifests itself in the web server logs. Check to see if the gateway server service, Siebel server service is running, the specific component (in this case it would be an object manager component such as CallCenter Object Manager) on this server is running and has ample Max Tasks to accommodate growing requests.

If the error is reported when two components are attempting to establish communication, check that the target component is running.

Check to ensure that all components that belong to "System Management" component group are functional and running.

Solution

Start the Siebel server service if it is found not to be running.

Start the server component in question that users are attempting to contact - verify that it has the appropriate settings for the component parameter called "Max Tasks" and it is running on the port # users are attempting to contact it on. If there is a firewall present, ensure that the port in question is open and accessible.

Ensure network connectivity issues do not exist between the several Siebel entities.