Workflow Monitor Agent fails with SBL-SRB-00047: Could not route message to WfProcMgr with registered key (null)
(Doc ID 486911.1)
Last updated on APRIL 18, 2023
Applies to:
Siebel Workflow - Version 7.7.2.5 [18368] to 8.1.1 [21112] [Release V7 to V8]Information in this document applies to any platform.
This document was previously published as Siebel SR 38-3070028991.
Symptoms
Customer has several custom Workflow Monitor Agent components created by following this Doc:
How Do You Start a Workflow Monitor Agent in Siebel Version 7.x? (Doc ID 476425.1)
These work fine until the last few days where the agents fail with the following logs:
SrmLayerLog Error 1 0 2006-06-19 16:51:28 (srbroute.cpp(2052) err=5700035 sys=0) no other server
SrmLayerLog Error 1 0 2006-06-19 16:51:28 (srbmsgfn.cpp(387) err=5700047 sys=0) Could not route message to WfProcMgr with registered key (null)
GenericLog GenericError 1 0 2006-06-19 16:51:28 (srmconn.cpp (3049) err=5700047 sys=126) SBL-SRB-00047: Could not route message to WfProcMgr with registered key (null)
GenericLog GenericError 1 0 2006-06-19 16:51:28 (srmconn.cpp (2703) err=5700047 sys=0) SBL-SRB-00047: Could not route message to WfProcMgr with registered key (null)
GenericLog GenericError 1 0 2006-06-19 16:51:28 (srmconn.cpp (2303) err=5700047 sys=0) SBL-SRB-00047: Could not route message to WfProcMgr with registered key (null)
Cause
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
Symptoms |
Cause |
Solution |
References |