Siebel SQLs/Error Messages >  SBL-OMS-00203, SBL-NET-01034, SBL-DAT-00523,SBL-CSR-00418 and SBL-UIF-00299

SBL-OMS-00203: Error %3 invoking method "%2" for Business Service "%1"

This error message is usually reported when errors are encountered
upon executing a method within a business service.
The error message is usually accompanied with an additional follow up error message that indicates reason for failure, as shown below:

OMS-00203: Error 33016 invoking method "RunProcess" for Business Service "Workflow Process Manager"
SBL-OMS-00203: Error ... invoking method "RunProcess" for Business Service "Workflow Process Manager"
Cannot find entry '0-R9NH' in the bounded pick list for the field 'Contact Organization' in Integration component 'Contact' (IDS_ERR_EAI_SA_PICK_VALIDATE))

The cause for the error is unique for almost all cases and does not have a standard solution.
In the above case, it was caused by a missing entry in a bounded pick list.

To diagnose this behavior, you can increase the ObjMgrBusServiceLog and ObjMgrExtLangLog logging events for the specific server component.

NOTE: You can also set these events for the Workflow Process Manager.
For example, if this error was reported within a Call Center Object Manager user session,
the following event levels would be set to acquire more details on the reason for this failure.
Some additional event level logging might also be required and varies from case to case.
srvrmgr> change evtloglvl ObjMgrBusServiceLog=4 for comp SCCObjMgr_enu
srvrmgr> change evtloglvl ObjMgrExtLangLog=4 for comp SCCObjMgr_enu

SBL-NET-01034: The SISNAPI connection was closed by the peer

This error message indicates that the Siebel server connection with the session was closed.
This can be caused for several reasons - network error can be one of them.
To check network errors, we had to ask the networking team to check if there was some
issue. There were no errors there.

We discovered that these error messages occurred around deployment time. We had shut down
Siebel servers and the errors occurred just after that. In such a case, these errors can be
ignored.

SBL-DAT-00523: The selected record has been modified by another user since it was retrieved

This means that some process is trying to update a row in a table and cannot find it.
This error occurred for us in 2 cases

1) Workflow was trying to update an opportunity that was deleted or did not fit the
workflow criteria. e.g. An opportunity with correct row_id but different name.
Some of these cases could be ignored. If the user had deleted an opportunity after modifying
it, this case can be ignored. If the opportunity exists with wrong values, we need to check
workflow logic. Increase log levels of Workflow and diagnose.

2) EAI object was searching for a record with some wrong variables. e.g. Account with
correct VAT number but wrong row_id. This was actually a design error with the integrated
system. The application interfacing with Siebel had different composite keys than Siebel.
Hence it was fetching incorrect records, multiple records or could not find the correct record.

SBL-CSR-00418: Communication: User is not associated with any communication configuration in the database.

These error messages will keep coming and can be ignored. Oracle support web says that in a future release, these messages will stop coming.From Oracle document - ID 536303.1.
If you are NOT using Siebel CTI Toolbar or CTI Functionality you can disable the Application Object Manager parameter "Enable Communications" setting it to False in Site Map>Administration - Server Configuration>Servers>Components>Parameters.
Now in case you have a mixed environment with Siebel CTI users and NO Siebel CTI users connecting to the same Application Object Manager,
currently the SComm_<user id>.log will be gerenated for ALL user and for the NO Siebel CTI users the error message will be logged into the SComm.log and Siebel Application Object Manager task log and a message will appear in the Application Menu Status Message in the User Interface for a couple of seconds.
Notice that in this case this error message is benign and can be ignored since the customer do not want to use Siebel CTI functionality at all although the Application Object Manager has the parameter Enable Communications for CTI enabled.
There is no possible workaround available to avoid this error mesage for Siebel users NOT associated to any Communications Configuration and login to a Application Object Manager with "Enable Communications" component parameter set to True.
Enhancement Request Bug 10503044 and Product Defect <> has been logged to stop to generate this error message in the SComm.log.
Enhancement Request Bug 10478422 has been logged to stop this error message from occurring in the Applicaiton Object Manager task log file too.
Currently this Enhancement are target to a future release.

SBL-UIF-00299: Wrong Field Values or value types.

This is usually a benign error. This happens when a user enters a different type of data in a field.
e.g. If the user enters a number in a string field or a non-existing value in a picklist, this error is logged.
If this error happens too often, check if some automated process is trying to insert incorrect values.