Siebel 8.1.x Communication Outbound Manager fails to send emails with errors: "Cannot open request state file CommOutboundMgr" and "Not connected to FSM" (Doc ID 1491303.1)

Last updated on MARCH 02, 2017

Applies to:

Siebel Email Response - Version 7.8 [19038] to 8.1.1.8 SIA [23012] [Release V7 to V8]
Information in this document applies to any platform.

Symptoms

On Siebel 8.1.1.3 using Communications Outbound Manager component to send out Outbound Requests.

When Siebel tries to send out outbound requests using CommOutboundMgr component it fails to send the emails. The following errors can be observer on Communication Outbound Manager component task for the outbound request with event trace log level increased:

SrmRouting SrmRoutingSubevent 4 0000006d50341600:0 2012-08-22 01:00:45 SNDREQ
 IDS  : FLAGS [1] : REQID [2-4OFLL-1BFG] : SRBSESSID [a5f315e8200003SBLGW] : SRMCONNID [11]
 SRC  : SRC_ID [] : SRC_KEY []
 DEST : ROUTE_ID [FSMSrvr] : ROUTE_KEY [] : ROUTE_SRVR [] : LANG_CODE [ENU] : CODE_PAGE [1200]
GenericLog GenericError 1 0000006d50341600:0 2012-08-22 01:00:45 (srmconn.cpp (2571) err=1180682 sys=0) SBL-NET-01034: The SISNAPI connection was closed by the peer.
GenericLog GenericError 1 0000006d50341600:0 2012-08-22 01:00:45 (srmconn.cpp (2313) err=1311735 sys=0) SBL-SVR-01015: Could not send message due to (null)
GenericLog GenericError 1 0000006d50341600:0 2012-08-22 01:00:45 (fsmclientstub.cpp (355) err=1311735 sys=0) SBL-SVR-01015: Could not send message due to (null)
GenericLog GenericError 1 0000006d50341600:0 2012-08-22 01:00:45 Not connected to FSM
CommSrvr CommSrvrWarning 2 0000006d50341600:0 2012-08-22 01:00:45 Cannot open request state file CommOutboundMgr2-11DPAN3.CommSrvr.crf, error 1.
GenericLog GenericError 1 0000006d50341600:0 2012-08-22 01:00:45 Not connected to FSM
CommSrvr CommSrvrWarning 2 0000006d50341600:0 2012-08-22 01:00:45 Cannot remove request state file CommOutboundMgr2-11DPAN3.CommSrvr.crf, error 1.

After this error all other Outbound Request processed by this CommOubountMgr component instance fail with similar error:

GenericLog GenericError 1 0001a54c5033249c:0 2012-08-22 01:01:29 Not connected to FSM
GenericLog GenericError 1 0001a54c5033249c:0 2012-08-22 01:01:29 Not connected to FSM
CommSrvr CommSrvrWarning 2 0001a54c5033249c:0 2012-08-22 01:01:29 Cannot open request state file CommOutboundMgr2-11DPAMA.CommSrvr.crf, error 1.
GenericLog GenericError 1 0001a54c5033249c:0 2012-08-22 01:01:29 Not connected to FSM
CommSrvr CommSrvrWarning 2 0001a54c5033249c:0 2012-08-22 01:01:29 Cannot remove request state file CommOutboundMgr2-11DPAMA.CommSrvr.crf, error 1.

The only way to recover is to restart the CommOutboundMgr component.

 

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