My Oracle Support Banner

What are the reasons for SBL-SRB-00041 error in SRBroker logs? (Doc ID 2756752.1)

Last updated on MARCH 01, 2021

Applies to:

Siebel CRM - Version 20.6 and later
Information in this document applies to any platform.

Goal

Server Request Broker (alias SRBroker) is an interactive-mode Siebel Server component that belongs in the System Management Siebel Server component group. By default, one SRBroker is started for each Siebel Server. SRBroker handles client component requests by acting as a request router. For example, if a client makes a request to a Siebel Server for a component that is not running on that Siebel Server, the request is routed to another Siebel Server that is running the requested component.

SRBroker component connects to all server components in the Enterprise in star shape mode, and expects a graceful communication closure when a component process is shutdown.

If any component is terminated or it crashed the communication channel with SBroker cannot be gracefully closed. For this reason the following error is found on SRBroker logs:

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

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.