Workflow Monitor Agent

(Doc ID 495819.1)

Last updated on SEPTEMBER 09, 2016

Applies to:

Siebel Workflow - Version SIA [16168] and later
Generic Windows
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 2.8

***Checked for relevance on 26-Sep-2013***


We are using workflow policies in order to invoke workflow processes. We create a custom Workflow Monitor Agent component WorkMonSFAAssignment.

The workflow processes are executing "Synchronous Assignment Manager Requests" business service and the "Assign" method for calling the Assignment Manager to assign entities like Account and Opportunity.

When we create a new Account or Opportunity, our workflow monitor agent errors out with 'SBL-ESC-00054: Error processing requests' errors. Here is extracted from WorkMonSFAAssignment log:


2021 2004-04-29 15:47:08 2004-04-29 15:49:13 -0500 000000c0 001 ffff 0001 09 WorkMonSFAAssignment 57453 5372 3072 C:\apps\sea753\siebsrvr\log\WorkMonSFAAssignment_57453.log 7.5.3 [16157] ENU

GenericLog GenericError 1 2004-04-29 15:47:08 (smireq.cpp 33(144) err=4300203 sys=0) Error (null) invoking method "(null)" for Business Service "(null)"

GenericLog GenericError 1 2004-04-29 15:47:08 ((0) err=4300107 sys=27813) Object manager error: ([0] No server connect string for Siebel Component SRBroker in Siebel Enterprise TFSD_ES_P, Siebel Server namcptsolas500 (0x6ca5))


WorkMonSFAAssignment tries to get it processed for 2 minutes which is the standard WorkMon behavior when there is an error, all attempts failed, then the task failed completed.



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