Port in Use / Blocked - Cannot access FSMSrvr (or other component) through SRBroker - SISNAPI Error - HP-UX / HP Open View (Doc ID 875068.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Financial Services CRM - Version 7.8.2.6 SIA [19230] and later
HP-UX Itanium
HP-UX Itanium (32-bit)
HP-UX PA-RISC (32-bit)
HP-UX PA-RISC (64-bit)
One or more Siebel components become unavailable, even if their logs show they are running

SRBRoker log shows errors like
SBL-SRB-00041: Could not send a SISNAPI hello message


Symptoms

In this particular case, the FSMSrvr component registered with port 49179 when the Siebel Server started up

netstat -an | grep 49179

showed

tcp        0      0  127.0.0.1.49179        *.*                     LISTEN tcp        0      0  *.49179                *.*                     LISTEN tcp        0      0  127.0.0.1.49179        127.0.0.1.924           ESTABLISHED tcp        0      0  127.0.0.1.924          127.0.0.1.49179         ESTABLISHED

The Siebel component binds with * (bold),

the binds to localhost (127.0.0.1) are from other software using the same port - in this case, HP Open View.

SRBroker requests don't reach the Siebel component, in this case FSMSrvr.

Note that this is not limited to any specific component name - it can affect any Siebel Component whose port number from the enterprise log is used by a different process; another customer for example reported the same problem for WfProcBatchMgr that suddenly stopped processing (repeating component) requests.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms