Search This Blog

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


Applies to:

Siebel Life Sciences CRM - Version: 8.0.0.1 SIA [20408] to 8.1 SIA [21039] - Release: V8 to V8
Information in this document applies to any platform.

Symptoms

When deploying an ADM package containing Audit Trail Admin data type objects, a failure is encountered with one particular record. The command window displays the following error:
Some of the current deploy/restore requests failed, please use 'status' command to list the detail status or check the agent log for detail error (SBL-DMJ-00317).


In the Administration - Server Management > Jobs view, the following error message is displayed for the failing "Application Deployment Manager Processor" job:
SBL-OMS-00203: Error (null) invoking method "(null)" for Business Service "(null)"


The management agent log files show the following additional error message:
SBL-APS-00133: The current State Model's active period is overlapped with the following State Model(s): 'LS Clinical Trip Report Status'

Cause

The problem was caused by a conflict between the standard State Model already present in the deployment environment and the State Model in the ADM package.

Please note that there can only be one State Model for the same business component with the same active period.

Solution

The problem was resolved after deleting the standard State Model already present in the deployment environment ('LS Clinical Trip Report Status' in this example) and deploying the ADM package again.



Applies to:

Siebel System Software - Version: 7.5.3 [16157] and later   [Release: V7 and later ]
Information in this document applies to any platform.
Error Message Area:Object Manager - OMS
Version:Siebel 7.5.3

Purpose

This document is intended to provide cause and corrective action information about Siebel Error Message SBL-OMS-00203: Error %3 invoking method "%2" for Business Service "%1"

Scope

This document is informational and intended for any user.

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

Explanation

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"
Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Update Camp Con'.
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 peculiar to each situation hence covering all possible scenarios is not feasible. The accompanying error message is usually indicative of the problem at hand. As in the above case, it was caused by a missing entry in a bounded pick list.

To further 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

For more information about setting these logging events for the Application Object Manager, refer to Document 477897.1 How Can Tracing Be Increased for the Siebel Object Manager?
NOTE: The following bookshelf version is also applicable to the version listed in the header of this error message documentation. Also review the Siebel Bookshelf version 7.8 > System Monitoring and Diagnostics Guide for Siebel eBusiness Applications > Configuring Siebel Server and Component Logging > Configuring Siebel Server Component Logging > Common Event Types for Application Object Manager Diagnostics.

For information about debugging scripts, refer to Document 476793.1 Tips for Debugging Siebel eScript or Siebel VB and Document 477452.1 Using TraceOn, Trace, and TraceOff methods in Siebel Script.  Review the subsequent logs to assist in troubleshooting this error message.

In Siebel version 7.5.3 or earlier, you may encounter these errors while trying to build a Siebel Client Repository File language code kit.

SBL-OMS-00107: Object manager error: ([0] Error in getting file from Upgrade Kit Wizard File Attachment

SBL-OMS-00203: Error 37002 invoking method "Create Upgrade Kit" for Business Service "Upgrade Kit Wizard OMSV"

This error will occur if the upgrade kit name does not have the language code string, such as _ENU, included. Change Request 10461805 has been logged to address this product defect.

Corrective Action

It is not feasible to list all the Corrective Actions to resolve this error because the solution will vary with each specific situation. After enabling the event logging for the particular server component, you should review the appropriate log file for additional information. Then take appropriate action depending on the cause of the error. After the behavior has been corrected, do not forget to reset the event logging levels back to the default value of 1 for the server component to reduce the amount of information generated in the log files.

If you are encountering this error while trying to build a Siebel Client Repository File language code kit, then create a new upgrade kit that includes the language code string in the kit name, for example SRF_ENU. Change Request 10461805 has been fixed in Siebel version 7.7.




Applies to:

Siebel Reports - Version: 8.1.1.2 and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Sometimes when invoking a BI Publisher report and after submitting the user may receive the following error message :
"SBL-OMS-00203: error <?> When calling the method "<?>" For Business Service "<?>""

With increased logging enabled on the XMLPReportServer (change evtloglvl %=5 for comp XMLPReportServer), the following errors were visible in the log files at the point at which the UploadFiles is performed :
EAIQrySpec EAIQrySpecParams 3 00015bcb4c2a1ec4: 0 2010-07-01 13:39:04 The object ID for the''type 'GDP DH Opportunity' specified query is '[DH Opportunity - Detail TA.Id] = '1-D78ZB' AND [. Activity UID]> = '1-D78ZBTechnical000 "AND [. Activity UID] <= 1-D78ZBTechnical999" '

EAIInfra EAIInfraOutputMsg 3 00015bcb4c2a1ec4: 0 2010-07-01 13:39:04 Output message: IntObjType = GDP DH Opportunity Format = Siebel Hierarchical

ObjMgrBusServiceLog 00015bcb4c2a1ec4 Error 1 0 2010-07-01 13:39:04 (eaiqryspec.cpp (867)) SBL-EAI-04176: Information on the integration component''were not found. Check the query and output specifications integration object definition.

EAISiebAdptPerf EAISiebAdptPerfStat 00015bcb4c2a1ec4 3: 2010-07-01 13:39:04 QueryPage 0 | 0 | 0

EAISiebAdpt EAISiebAdptErr a 00015bcb4c2a1ec4: 0 2010-07-01 13:39:04 [0] information on the integration component'' were not found. Check the query and output specifications integration object definition. (SBL-EAI-04176) (0x231050)

ObjMgrBusServiceLog 00015bcb4c2a1ec4 Error 1 0 2010-07-01 13:39:04 (xmlpdatasvc.cpp (1264)) SBL-EAI-04176: Information on the integration component'<?>' were not found. Check the query and output specifications integration object definition.

ObjMgrBusServiceLog 00015bcb4c2a1ec4 Error 1 0 2010-07-01 13:39:04 (xmlpdriversvc.cpp (567)) SBL-EAI-04 176: Information on the integration component'<?>' were not found. Check the query and output specifications integration object definition.

GenericLog GenericError a 00015bcb4c2a1ec4: 0 2010-07-01 13:39:04 Object manager error: ([0], information on the integration component'<?>' not found. Check the query and output specifications integration object definition. (SBL-EAI-04176) (0x231050))

GenericLog GenericError a 00015bcb4c2a1ec4: 0 2010-07-01 13:39:04 ((0) err = 2818155 sys = 2297936) SBL-OMS-00107: Object manager error: ([0] information on the integration component'<?>' were not found. Check the query and output specifications integration object definition. (SBL-EAI-04176) (0x231050))

GenericLog GenericError a 00015bcb4c2a1ec4: 0 2010-07-01 13:39:04 (bsvcmgr.cpp (1384) err = 2818251 sys = 0) SBL-OMS-00203: Error 2297936 when calling the method "Generate Report" for Business Service "XMLP Driver Service"

GenericLog GenericError a 00015bcb4c2a1ec4: 0 2010-07-01 13:39:04 (bsvcmgr.cpp (1227) err = 2818251 sys = 0) SBL-OMS-00203: Error 2297936 when calling the method "Generate Report" for Business Service "XMLP Driver Service"

Cause

The behavior is caused because of a missing Integration Component

Solution

After adding the missing Integration Component everything works as expected.



Applies to:

Siebel Reports - Version: 8.1.1.1 [21211] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

Siebel BI Publisher Reports that display signature (captured using Signature Capture feature in Siebel) fail to generate.


How to Reproduce

1. Install and configure Siebel CRM 8.1.1.3 SIA and Oracle BI Publisher 10.1.3.4.1.

2. Create custom reports that display signature (captured in the Siebel CRM application).

3. Report generation fails with the error mentioned below.

XMLP Report Server Component log file:

SBL-OMS-00203: Error 9815388 invoking method "GenerateReport" for Business Service "XMLP Driver Service"


BI Publisher XDO logs:


[011411_154024775][][EXCEPTION] oracle.xml.parser.v2.XMLParseException: End tag does not match start tag 'properties'.
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320)
at oracle.xml.parser.v2.NonValidatingParser.parseEndTag(NonValidatingParser.java:1368)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1313)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336)
at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:292)
at oracle.apps.xdo.common.config.ConfigReader.read(Unknown Source)
at oracle.apps.xdo.common.config.ConfigReader.read(Unknown Source)
at oracle.apps.xdo.template.PropertyManager.getProperties(Unknown Source)
at oracle.apps.xdo.template.PropertyManager.getRuntimeProperties(Unknown Source)
at oracle.apps.xdo.template.RTFProcessor.process(Unknown Source)
at oracle.apps.xdo.servlet.RTFCoreProcessor.translateRTFTemplate(RTFCoreProcessor.java:177)
at oracle.apps.xdo.servlet.RTFCoreProcessor.getXSLFOFile(RTFCoreProcessor.java:122)
at oracle.apps.xdo.servlet.RTFCoreProcessor.transform(RTFCoreProcessor.java:44)
at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:326)
at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:97)
at oracle.apps.xdo.servlet.ReportImpl.renderBody(ReportImpl.java:512)
at oracle.apps.xdo.servlet.ReportImpl.renderReportBody(ReportImpl.java:83)
at oracle.apps.xdo.server.impl.DefaultReport.run(DefaultReport.java:44)
at oracle.apps.xdo.webservice.v11.PublicReportServiceImpl.generateReport(PublicReportServiceImpl.java:292)
at oracle.apps.xdo.webservice.v11.PublicReportService.runReport(PublicReportService.java:229)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:397)
at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:186)
at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:323)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:454)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:351)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:873)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Unknown Source)


Cause


The issue has been caused due to the XSLT processing error on the BI Publisher Server. The following property under the 'Runtime Configuration > Properties' had been enabled:

Enable scalable feature of XSLT processor = True

The scalable feature chunks the XML data in smaller parts for better processing. But when XML data containing signature string is chunked, it results in XSLT processing error and therefore causing the report generation to fail.

Solution

The issue can be resolved by following the steps given below:

1. Log into the BI Publisher Server as 'Administrator'.

2. Navigate to the 'Admin' tab > 'Runtime Configuration' > 'Properties' page.

3. Set the following property in the 'FO Processing' section:

Enable scalable feature of XSLT processor = False

4. Apply the changes.

5. Restart BI Publisher Services.

6. Test run the signature report.



Applies to:

Siebel Anywhere - Version 7.5.3 SIA [16157] and later
Siebel Remote - Version 7.5.3 SIA [16157] and later
z*OBSOLETE: Microsoft Windows 2000
***Checked for relevance on 30-Aug-2012***
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Com/Med
Database: Oracle 9.2.0.2
Application Server OS: Microsoft Windows 2000 Advanced Server SP 2
Database Server OS: Sun Solaris 2.8

This document was previously published as Siebel SR 38-1088344191.


Symptoms

Errors: SBL-OMS-00203, SBL-OMS-00107
We have recently upgraded our UAT environment from Siebel release 7.2.218 to 7.5.3. We as part of this release we have applied a dev2prd. As we have a replicated environment we are trying to use Siebel Anywhere to apply the dev2prd changes via a Database Schema upgrade kit. Unfortunately this is failing with the following error:
SBL-OMS-00203: Error 25064 invoking method "Create Upgrade Kit" for Business Service "Upgrade Kit Wizard OMSV"
This worked before the upgrade to 7.5.3. I have increased event logging for the upgrade Kit Builder process to 4 and will attach the log file which pretty much says that it cant find the ddl.dat file and gives the following error:

Object manager error: ([0] You are not connected to a valid file server.
I assume this means it can not access the siebfile.  I have found a related Service Request #38-927731951 and followed its recommendations, but these do not appear to help.
The database Schema Upgrade Kit is being run from a dedicated client.
Please let me know if you need any further information.

Cause

Wrong setup

Solution

Message 1

For the benefit of other readers, attempts to create Siebel Anywhere kits would fail with the following in the UpgKitBldr*.log file after “Part 4 of 4: Adding DDL file: d:\siebel1\siebsrvr\temp\ddl.dat”:

SBL-SVR-03005: No server connect string for Siebel Component SRBroker in Siebel Enterprise dtcIsen01, Siebel Server dtciswf01.
Please check whether SRBroker is running on server dtciswf01 in enterprise dtcIsen01.
If you are using web client, please make sure that the DSRequestServer is empty or set to the server you want in case you have special requirement.
If you are using dedicated client, please make sure that Gateway name, Enterprise name, Server name and RequestServer is set properly in CFG file.
Otherwise, you may see these related error messages, as well:
SBL-SVR-03005: No server connect string for Siebel Component (null) in Siebel Enterprise (null), Siebel Server (null)
SBL-SVR-03005: No server connect string for Siebel Component (null) in Siebel Enterprise (null), Siebel Server (null)
SBL-OMS-00107: Object manager error: ([0] You are not connected to a valid file server. Please contact your system administrator.
SBL-OMS-00203: Error 25064 invoking method "Create Upgrade Kit" for Business Service "Upgrade Kit Wizard OMSV"
The UpgKitBldr task was trying to connect to the SRBRoker on server dtciswf01, but could not establish the network connection. Review of the customer's siebns.dat file showed the following parameter was set for the Named Subsystem "ServerDataSrc:"

DSRequestServer = dtciswf01

This was causing UpgKitBldr to attempt to process all requests using the SRBroker on server dtciswf01. By unsetting this parameter, UpgKitBldr uses a round robin approach to process the requests, finding an SRBroker that is running on any given server within the enterprise.   The customer followed the steps in "Changing DSRequestServer to an Empty String or Null Value (Doc ID 476817.1)” to unset this parameter.

The customer was also provided with the following recommendations:
1. Reduce Maximum Tasks parameter for SRBroker to 100 from 150
2. Set Maximum MT Servers to the default value of 1 for UpgKitBldr
After the above changes, the customer rebooted the Siebel Server machines and restarted the Siebel Server services.
Kit creation was then consistently successful.






Applies to:

Siebel System Software - Version 8.0.0.1 [20408] and later
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V8 (Enterprise)
Version: 8.0 [20405]
Database: Oracle 10.2.0.2
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: IBM AIX 5L 5.3

This document was previously published as Siebel SR 38-3301597043.


Symptoms


Customer was trying to demonstrate Siebel Search using FAST Instream and were receiving errors from the Search Data Processor and the Search Incremental Indexer. Search Daa Processor is repeatedly failing with error - “The method 'CreateIncrementalFullIndex' is not supported on Business Service 'Search Data Processor'.”

Customer was able to index manually.

Customer had setup the RunTime event (although they did not have any custom search objects) and receive the following error everytime the Job is run:

SBL-OMS-00203: Error (null) invoking method "(null)" for Business Service "(null)".


Cause

Bug 10521046

Solution

The same scenario was tested inhouse and found that –
When there's no records to update index, the Incremental Search Indexer is failing with error:
SBL-OMS-00203: Error (null) invoking method "(null)" for
Business Service "(null)".

  Bug 10521046 has been raised to rectify this problem in siebel search 8.0 [20405]







Applies to:

Siebel Workflow - Version: 7.5.2.100 [15252] and later   [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.2.100 [15252]
Database: Oracle 8.1.7.4
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Microsoft Windows 2000 Server SP 2

This document was previously published as Siebel SR 38-1170955858.

Symptoms

The customer created a workflow process that invoked Assignment Manager using the Synchronous Assignment Manager Requests business service. The process was invoked from a policy with a duration.

Workflow Process Manager and Assignment Manager tasks sometimes failed when trying to assign a locked record. Ignore Errors was set to True so the Workflow Monitor Agent should have tried to invoke the action for 2 minutes and then deleted the request and moved onto the next one if the action had not completed correctly. However, in this case, the Monitor Agent kept invoking the Process Manager and Assignment Manager over and over again.

Cause

The reported behavior occurred because the request was not purged from S_ESCL_STATE at the end of retry interval and, as a result, the Monitor Agent processed it over and over again. Change request Bug 10490713 has been raised to address this defect. Please note that all requests are reviewed and prioritized for possible inclusion in a future release.

Solution

The Monitor Agent worked correctly for policies that did not include a duration. The customer prevented tasks from being invoked over and over again by setting Ignore Errors to False. As a result, the Monitor Agent task failed if the action did not complete correctly at the end of the retry interval.

 


 

 





Applies to:

Siebel CRM Marketing, SPE - Version 8.2.1 SIA[22220] and later
Information in this document applies to any platform.

Symptoms

On : 8.2.1 SIA[22220] version, Siebel Marketing

When trying to load a campaign,
the following error occurs.

ERROR
-----------------------

SBL-OMS-00203: Error (null) Invoking method "(null)" for Business Service "(null)"


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. Create Offer - AL 8.2 Offer
2. Create Treatment - AL 8.2 Phone Treatment
3. Create List - AL 8.2 List
4. Added two Contacts to the list of type 'Imported'
James Bond
Jason Bourne
5. Verified that the Marketing workflows were all active.
6. Created Campaign - AL 8.2 Campaign
7. Associated Offer and Treatment.
8. Associated List via Segments/Lists view.
9. Allocated 100% to 'AL 8.2 Phone Treatment'
10. Ran Campaign Load.
11. Errors out with:
Execution Status tab:
Argument '' in step 'Load Segment Tree Cells/Segments' is not correctly initialized or does not return valid data.(SBL-BPR-00107)

System Tasks tab:
Error/Warning : Argument '' in step 'Load Segment Tree Cells/Segments' is not correctly initialized or does not return valid data.(SBL-BPR-00107)


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot load a Campaign in 8.2

Cause

 This is caused by missing Output Arguments in the related Business Service "Mktg Data Load Service"

Solution

 This issue is resolved in 8.2.2 - Bug # 10588766:
NOT Reproducible in 8.2.2:

Ran a Campaign Load in 8.2.2 SIA [22314]

1. Create Offer - AL 8.2 Offer
2. Create Treatment - AL Phone Treatment
3. Create List - AL 8.2 List
4. Added two Contacts to the list of type 'Imported'
James Bond
Jason Bourne
5. Verified that the Marketing workflows were all active.
6. Created Campaign - Al 8.2.2 Campaign Test
7. Associated Offer and Treatment.
8. Associated List via Segments/Lists view.
9. Allocated 100% to 'AL Phone Treatment'
10. Ran Campaign Load.
11. Worked successfully....No errors.

References

@NOTE:492369.1 - Workflow Process Manager
BUG:10588766 - [CR#12-1XEJIRJ][FR#12-1XEJISX] KIRKWOOD:CAMPAIGN LOAD WITH A LIST ASSCOIATED IS
NOTE:522229.1 - SBL-OMS-00203: Error 65535 invoking method "RunProcess" for Business Service "Workflow Process Manager"
NOTE:749587.1 - Repeating component request jobs "Search Incemental Indexing" for OSES exit with error SBL-OMS-00203: Error (null) invoking method "(null)" for Business Service "(null)".

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)