Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
Purpose
This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04304: Unknown Part '%1' for operation '%2' exists in SOAP message.
Scope
This document is informational and intended for any user.
SBL-EAI-04304: Unknown Part '%1' for operation '%2' exists in SOAP message.
Explanation
The SOAP message contains an unknown part for the particular operation. This does not correspond to the WSDL definition.
Corrective Action
Check that the correct part as defined in the WSDL definition is being sent in the SOAP message.
Applies to:
Siebel eConfigurator - Version: 8.1.1 [21112] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
On : 8.1.1 [21112] version, eConfigurator
Bookshelf guide Siebel CRM Web Services Reference> Product Configurator Web Service> Response Message Description: Begin Configuration, states:
ListOfQuote:
Quote instance if ReturnFullInstance input parameter was set to Y. See BeginConfiguration Request Message for details.
This parameter is not listed in the BeginConfiguration Request Message. When inserted the following error occurs.
ERROR
-----------------------
Cause
Product Defect 12-1YOKG1Z.
Application should be able to use ReturnFullInstance parameter as described in Bookshelf.
Solution
Fix Request 12-1YOL65P has been created to enable this functionality to be included in the 8.1.1.4 maintenance release.
Workaround : call the Quote webservice and query the quote and it’s details before or after BeginConfiguration.
References
BUG:10595949 - PRODUCT CONFIGURATOR WEB SERVICE, RETURNFULLINSTANCE INPUT PARAMETER CAUSES ERROR
Applies to:
Siebel Reports - Version: 8.0.0.8[20430] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
XMLP Report Server log shows:
=====================
ObjMgrLog Error 1 000000024d0f1628:0 2010-12-20 06:08:37 (soapbinding.cpp (564)) SBL-EAI-04304: Unknown Part ':oracle.apps.xdo.webservice.exception.OperationFailedException' for operation 'runReport' exists in SOAP message.
ObjMgrBusServiceLog Error 1 000000024d0f1628:0 2010-12-20 06:08:37 (outdisp.cpp (209)) SBL-EAI-04308: Operation 'runReport' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceService' at port 'PublicReportService_v11' failed with the following explanation: "oracle.apps.xdo.webservice.exception.OperationFailedException: PublicReportService::generateReport failed: due to oracle.apps.xdo.XDOException".
Xdo.log shows:
===========
[122010_060837020][java.lang.String][EXCEPTION] java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(Unknown Source)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(Unknown Source)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(Unknown Source)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(Unknown Source)
at oracle.apps.xdo.template.FOProcessor.createFO(Unknown Source)
at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
at oracle.apps.xdo.servlet.RTFCoreProcessor.transform(RTFCoreProcessor.java:70)
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)
Cause
The following code in the BI Publisher report remplate is not working after applying the BI Publisher Patch (10023449) :
Solution
After applying the latest BI Publisher patch (10256764) it was confirmed that the behavior persisted.
Removal of the patch can be used to resolve this behavior the only way is to revert back to the previous update patch / build providing you have a back up of the scheduler schema together with the existing xmlpserver.ear. Before any patch application you should take a backup of the scheduler schema and make a copy of the existing xmlpserver.ear.
Siebel Reports - Version: 8.1.1 SIA [21111] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
During the installation of the Siebel BI Publisher Reports Server the post-installation steps include the upload of the standard Siebel Reports from the Siebel Server up to the BI Publisher Server (Siebel Reports Administration Guide, P.36).
When attempting to perform this upload an error was being returned to the user performing the upload and, upon examination through the BI Publisher administration console, it was evident that no reports had been uploaded.
The error being returned to the user appeared as follows :
[1][0] Operation '' of Web Service '.' at port '' failed with the following explanation:
"".(SBL-EAI-04308)(IDS_EAI_WS_OD_FAULT)
[2] Object manager error:([0] Operation '' of Web Service '.' at port failed with the following explanation: "".(SBL-EAI-04308)(IDS_WS_OD_FAULT))
[3] Error (null) invoking method "(null)" for Business Service "(null)"
In addition further examination of the XMLPReportServer_xxx.log with increased logging in place showed the following more detailed errors :
ObjMgrBusServiceLog InvokeMethod 4 000000264aaa1244:0 2009-09-11 17:14:08 Begin: Business Service 'EAI HTTP Transport' invoke method: 'SendReceive' at 109bc658
ObjMgrLog Error 1 000000264aaa1244:0 2009-09-11 17:14:22 (httptransport.cpp (1631)) SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 500'
ObjMgrLog Error 1 000000264aaa1244:0 2009-09-11 17:14:22 (httptransport.cpp (981)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
ObjMgrBusServiceLog InvokeMethod 4 000000264aaa1244:0 2009-09-11 17:14:22 Business Service 'EAI HTTP Transport' invoke method 'SendReceive' Execute Time: 13.698 seconds.
.
.
ObjMgrBusServiceLog InvokeMethod 4 000000264aaa1244:0 2009-09-11 17:14:22 End: Business Service 'XML Hierarchy Converter' invoke method: 'DocToHier' at 10c7b110
ObjMgrLog Error 1 000000264aaa1244:0 2009-09-11 17:14:22 (soapbinding.cpp (564)) SBL-EAI-04304: Unknown Part 'http://xml.apache.org/axis/:hostname' for operation 'uploadReport' exists in SOAP message.
ObjMgrBusServiceLog Error 1 000000264aaa1244:0 2009-09-11 17:14:22 (outdisp.cpp (209)) SBL-EAI-04308: Operation 'uploadReport' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceService' at port 'PublicReportService_v11' failed with the following explanation: "java.lang.SecurityException: /SiebelCRMReports/Account List/aclist.rtf".
ObjMgrBusServiceLog InvokeMethod 4 000000264aaa1244:0 2009-09-11 17:14:22 Business Service 'PublicReportService' invoke method 'uploadReport' Execute Time: 13.734 seconds.
ObjMgrBusServiceLog InvokeMethod 4 000000264aaa1244:0 2009-09-11 17:14:22 End: Business Service 'PublicReportService' invoke method: 'uploadReport' at 1371ed38
Cause
The more detailed XMLPReportServer_xxx.log shows the following error which is returned in response to the uploadReport request by the BI Publisher Server :
ObjMgrBusServiceLog Error 1 000000264aaa1244:0 2009-09-11 17:14:22 (outdisp.cpp (209)) SBL-EAI-04308: Operation 'uploadReport' of Web Service 'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceService' at port 'PublicReportService_v11' failed with the following explanation: "java.lang.SecurityException: /SiebelCRMReports/Account List/aclist.rtf".
This indicates that a java.lang.SecurityException is occurring on the BI Publisher Server and therefore an examination of the console window on the BI Publisher Server is beneficial. Through examination of the console contents (specifically the GetRoles trace) it can be seen that in this instance the user performing the upload did not have the XMLP_DEVELOPER responsibility which is required to run uploadReport :
[091109_064412296][][STATEMENT] PublicReportService::uploadReport Service BEGIN
[091109_064412296][][STATEMENT] PublicReportService::initSession BEGIN
[091109_064412312][][EVENT] SiebelValidator(Properties prop)
[091109_064412312][][EVENT] endpoint:http://xxxx/eai_enu/start.swe?SWEExtSource=WebService&SWEExtCmd=Execute
[091109_064412312][][EVENT] adminUsername:SADMIN
[091109_064412312][][EVENT] adminPassword:********
[091109_064412312][][EVENT] Endpoint contains no UserName or Password, appending it with Admin's
[091109_064416578][][EVENT] GetRoles() returnsDispatcher,Siebel Administrator,Customer Service Representative,Customer Service Manager,Call Center Administrator
.
.
cs User,PH Executive Analytics Admin,PH Service Analytics User,PH Mobile Analytics Admin,Investigative Agent Analytics,Health Professional Analytics,PH Objective Analytics Admin,PH Objective Analytics User,PH Mobile Manager Analytics Admin, PH Mobile Manager Analytics User,XMLP_ADMIN
[091109_064416593][][STATEMENT] PublicReportService::initSession END --- ElapseTime = 4297
Solution
In order to resolve this behavior it is necessary to add the XMLP_DEVELOPER responsibility to the user performing the upload on the Siebel Server.
Having added the responsibility the user should logout, start a new Siebel Object Manager session, and then retry the upload.
Applies to:
Siebel Reports - Version: 8.1.1 [21112] and later [Release: V8 and later ]
Information in this document applies to any platform.
Symptoms
When a user attempts to upload a new report definition to the BI Publisher server through the Site Map > Administration - BIP Reports > Report Template Registration view an error can be returned as follows :
[1][0] Operation '' of Web Service ',' failed with the following explanation: "".(SBL-EAI-04308)(IDS_EAI_WS_OD_FAULT)
With increased logging enabled on the XMLPReportServer (change evtloglvl %=4 for comp XMLPReportServer), the following errors were visible in the log files at the point at which the UploadFiles is performed :
EAITransport EAITransportDebug 4 000001e44a0b0ffc:0 2009-05-13 16:42:03 *** HTTP response Headers from Data Send request:
HTTP/1.1 500 Internal Server Error
Date: Wed, 13 May 2009 20:42:02 GMT
Server: Oracle Containers for J2EE
Connection: Keep-Alive
Keep-Alive: timeout=15, max=100
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
.
.
.
ObjMgrLog Error 1 000001e44a0b0ffc:0 2009-05-13 16:42:03 (httptransport.cpp (1631)) SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 500'
ObjMgrLog Error 1 000001e44a0b0ffc:0 2009-05-13 16:42:03 (httptransport.cpp (981)) SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
.
.
ObjMgrLog Error 1 000001e44a0b0ffc:0 2009-05-13 16:42:03 (soapbinding.cpp (564)) SBL-EAI-04304: Unknown Part 'http://xml.apache.org/axis/:hostname' for operation 'createReport' exists in SOAP message.
ObjMgrBusServiceLog Error 1 000001e44a0b0ffc:0 2009-05-13 16:42:03 (outdisp.cpp (209)) SBL-EAI-04308: Operation 'createReport' of Web Service 'http://xmlns.oracle.com/oxp/service/PublicReportService.PublicReportServiceService' at port 'PublicReportService' failed with the following explanation: "No such operation 'createReport'".
ObjMgrBusServiceLog InvokeMethod 4 000001e44a0b0ffc:0 2009-05-13 16:42:03 Business Service 'PublicReportService' invoke method 'createReport' Execute Time: 103.678 seconds.
Cause
The behavior is caused because the target was a version 10.1.2 BI Publisher Server rather than the supported 10.1.3.4.
Solution
The Oracle BI Publisher Server should be upgraded to the support 10.1.3.4 version.
Further related information can be found in :
DocId 1051319.1 - Troubleshooting problems with the Siebel BI Publisher integration
No comments:
Post a Comment