Siebel SQLs/Error Messages >  SBL-ESC-00054: Error processing requests

SBL-ESC-00054: Error processing requests

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

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

SYMPTOMS

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.

CAUSE

The problem appears to be that the environment issue, that is, it not set up correctly to connect to the Assignment Manager (AsgnSrvr) through Server Request Broker (SRBroker).

In customer's environment, neither thick client nor thin client worked through the Process Simulator, got error also.

SOLUTION
We did the following to correct the environment, so customer can step through the Process Simulator without errors for thin client and thick client, and Assignment Manager worked correct:

1. thick client

- Edit client's fins.cfg to change the following:

[ServerDataSrc]
RequestServer = correct_siebsrvr_name
RequestServerName = incorrect_sieb_srvr_name

You changed RequestServerName to have the correct Siebel Server name.

- Please note from Siebel 7.7 onward, the following section is used instead of [ServerDataSrc] in the .cfg file for RequestServerName, and needs to be added when missing:

[InfraObjMgr]
RequestServerName = <Siebel Server Name>

After the above changes, you relogin to client application. After that the Simulator worked fine.

2. thin client

In Enterprise Configuration -> Enterprise Profile Configuration, the DSRequestServer parameter is the correct siebsrvr name under ServerDataSrc, but is blank under GatewayDataSrc.

You edited DSRequestServer to have the correct siebsrvr name for GatewayDataSrc, restart Gateway and Siebel Servers. After that, the Simulator worked fine.