Commonly Reported BI Publisher Errors

1) Mismatch between fields being queried on and fields included in the Integration Components
SBL-EAI-04177: Information about integration component field 'As Of Date' not found. Check query specification
and fields defined for integration component 'Order Entry - Orders'
The error indicates that the query which is being passed to the Integration Component uses fields which it does
not contain and therefore the query specification cannot be applied. As the query specification is constructed from
a combination of elements in the UI it is necessary to review the PDQ used on the view along with any custom
query performed by the user to establish the source of the error. The error message does include details of the
problematic fields and the Integration Component in question and this information should aid the developers in
making the necessary modifications.

2) Generic HTTP Internal Server error

SBL-EAI-04117: HTTP Request error during 'Submitting Data SendHTTP request': 'Status code - 500'
SBL-EAI-04117: HTTP Request error during 'Submitting Data Send HTTP request': 'Status code - 500'
These two error messages are commonly seen in a variety of scenarios and indicate that an error has occurred
on the BI Publisher side of the integration. When encountering these errors within the XMLPReportServer log files
a review should be made of the following trace which may provide details of specific issues in the integration.
If these errors are reported in isolation then it may be beneficial to introduce the following changes :
1. In Siebel Tools modify the vanilla 'EAI HTTP Transport' business service.
2. Right click on the name of the business service and select 'Edit Server Scripts'.
3. Copy paste the following script in the 'PreInvokeMethod' event:
function Service_PreInvokeMethod (MethodName, Inputs, Outputs)
{
if (MethodName == "SendReceive" || MethodName == "Send")
{
Inputs.SetProperty("HDR.Connection","close");
}
return (ContinueOperation);
}
4. Compile the modified business service and deploy the SRF to the Siebel server.
These changes ensure that the HTTP connections are closed and re-opened when new requests are made to the
BI Publisher Server thereby clearing any incomplete connections to the server.

3) Generic error with content of SOAP message

SBL-EAI-04304: Unknown Part ':oracle.apps.xdo.webservice.exception.InvalidParametersException' for operation
'uploadReport' exists in SOAP message.
The error message indicates that there are aspects of the SOAP message being returned from the BI Publisher

Server which were unexpected and this is normally an indication that there have been errors which require further
investigation. The recommendation in this scenario is to review subsequent error messages in the logs,
commonly the 'SBL-EAI-04308' error messages, which will provide specifics on the nature of the failure.
4) uploadReport error "Due to Report with Path xxxxx already exist"
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:
"oracle.apps.xdo.webservice.exception.InvalidParametersException: PublicReportService::executeUploadReport
Failure: Due to Report with Path [/SiebelCRMReports/Application Activity/Application Activity.xdo] already exist!".
The error message indicates that the attempt to upload the report template (in this case 'Application Activity')
failed because the BI Publisher Server already has a copy of the file uploaded. At present the uploadReport
method does not allow an Administrator to upload a new version of a report and automatically over-write the
existing copy of the report on the BI Publisher Server.
In order to workaround this behavior the Administrator needs to either rename or delete the folder for the existing
instance of the report currently uploaded on the BI Publisher Server. The BI Publisher Server stores its report
templates in the following location :
<%ORACLE_HOME%>\xmlp\XMLP\Reports\SiebelCRMReports
Once the existing report instance has been renamed or deleted a fresh upload of the report template should
complete without error.
5) uploadReport or run report error due to "java.lang.SecurityException"
Upload Report fails with the below error:
SBL-EAI-04304: Unknown Part 'http://xml.apache.org/axis/:hostname' for operation 'uploadReport' exists in SOAP
message.
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".
Running Report fails with the below error:
ObjMgrBusServiceLog Error 1 00000bb04d9a0e8c:0 2011-04-05 04:13:14 (outdisp.cpp (214)) 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:
"oracle.apps.xdo.webservice.exception.OperationFailedException: PublicReportService::executeUploadReport
Failure: Due to unable to create new Report as AbsolutePath [/SiebelCRMReports/Account List/aclist.xdo] due to
java.util.zip.ZipException: error in opening zip file".
This error message indicates that there was a Security issue with the upload of the Report Template in question
to the BI Publisher Server. This implies that the user performing the upload does not have permission to access
the folder and/or file. This is normally caused by a failure to set the correct responsibilities for the user in question
within the Siebel application.
The user running the report needs to have XMLP_SIEBEL_GUEST responsibility.
6) SetFieldValue error in Siebel Tools during import of the PublicReportService_v11.wsdl

SBL-DAT-00225: The value entered in field Integration Object of buscomp Repository Business Service Method
Arg does not match any value in the bounded pick list Repository PickList Integration Object.
SBL-EAI-04451: Method 'SetFieldValue' of business component 'Repository Business Service Method Arg'
(integration component 'Repository Business Service Method Arg') for record with search specification '[Name] =
"runReportRequest:parameters"' returned the following error:"The value entered in field Integration Object of
buscomp Repository Business Service Method Arg does not match any value in the bounded pick list Repository
PickList Integration Object.(SBL-DAT-00225)"
This error occurs when multiple repositories are present in the database and is caused by the import process not
validating which repository is being used as the target for the import.

7) CLASSPATH errors within the XMLPJvmSubsys

SBL-EAI-05010: Class name incorrect or does not extend SiebelBusinessService
This error occurs when the CLASSPATH parameter is incorrectly defined or is incomplete and is indicative of the
fact that the Java subsystem cannot resolve some of the classes for which methods are being called.
8) "No such operation" errors occurring during PublicReportService web service calls
SBL-EAI-04304: Unknown Part 'http://xml.apache.org/axis/:hostname' for operation 'getTemplateParameters'
exists in SOAP message.
SBL-EAI-04308: Operation 'getTemplateParameters' of Web Service
'http://xmlns.oracle.com/oxp/service/v11/PublicReportService.PublicReportServiceService' at port
'PublicReportService_v11' failed with the following explanation: "No such operation 'getTemplateParameters'".
SBL-EAI-04308: Operation '<?>' of Web Service '<?>.<?>' at port '<?>' failed with the following explanation:
"<?>".
The error message occurs when the operation being called cannot be found on the server side within the target
web service. In the case of a Siebel BI Publisher integration this is normally indicative of a mismatch within the
definition of the Outbound Web Service where the Siebel installation is running on the Siebel 8.1.1.1 release but
calls are being made to the earlier version of the PublicReportService web service available with Oracle BI
Publisher 10.1.3.4.0.
9) Missing dataservice.wsdl
WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at 'dataservice.wsdl'.: This
file was not found: file:/u01/obi/OracleBI/setup/dataservice.wsdl: java.io.FileNotFoundException: This file was not
found: file:/u01/obi/OracleBI/setup/dataservice.wsdl.
This behavior can occur during scheduling calls if there are access problems to the dataservice.wsdl. If this error
is reported then please review the file permissions on the .jar files in the CLASSPATH and also ensure that the
dataservice.wsdl file exists, has the correct permissions, and that the filename is all in lowercase.
10) "Setup.exe has encountered an error..." during installation of Oracle BI Publisher 10.1.3.4.1 or higher
When running the installation for Oracle BI Publisher 10.1.3.4.1 or higher via setup.exe an error dialog may
appear indicating that either:
"Setup.exe has encountered a problem and needs to close."
or
"The instruction at <xxxxxx> referenced memory at <xxxxx>. The memory could not be 'read'"

Both of these errors are caused by attempting to run the setup.exe from an installation directory which has a very
long path name. When unpacking the 'bipublisher_windows_x86_101341.zip' file it unpacks to the following path
by default:

<xxx>\bipublisher_windows_x86_101341\Windows\Oracle_Business_Intelligence_Publisher_Standalone\setup.e
xe

In order to resolve this behavior please unpack the .zip file so that it results in a shorter path to the setup.exe
where upon it will execute correctly.