Thursday, October 4, 2012

SBL-RPT-50524



Applies to:


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



Symptoms


Customer migrated some BI Publisher reports to another environment,
these reports worked on the original environment without issues, but
when they migrated to the new system one of them stopped working.


When the report is submitted an "Asynchronous Server Requests" windows appears with following text:




XMLP Report Generation time exceeds the Threshold time. Please see the generated Report Output File from BIP my Reports screen


When checking the report execution in "My BI Publisher Reports" this reports status is displayed as "Error".


Cause




Analyzing XMLPReportServer log files displayed the following entries:



ObjMgrBusServiceLog
Error 1 0000071f4dac0984:0 2011-04-28 15:13:50 (xmlpdriversvc.cpp
(567)) SBL-RPT-50524: BI Publisher engine failed to generate report.

ObjMgrBusServiceLog
InvokeMethod 4 0000071f4dac0984:0 2011-04-28 15:13:50 Business Service
'XMLP Driver Service' invoke method 'GenerateReport' Execute Time: 4.232
seconds.

ObjMgrBusServiceLog InvokeMethod 4 0000071f4dac0984:0
2011-04-28 15:13:50 End: Business Service 'XMLP Driver Service' invoke
method: 'GenerateReport' at 13011208

GenericLog GenericError 1
0000071f4dac0984:0 2011-04-28 15:13:50 Object manager error: ([0] BI
Publisher engine failed to generate report.(SBL-RPT-50524) (0x95c55c))

GenericLog
GenericError 1 0000071f4dac0984:0 2011-04-28 15:13:50 ( (0) err=2818155
sys=9815388) SBL-OMS-00107: Object manager error: ([0] BI Publisher
engine failed to generate report.(SBL-RPT-50524) (0x95c55c))

GenericLog
GenericError 1 0000071f4dac0984:0 2011-04-28 15:13:50 (bsvcmgr.cpp
(1393) err=2818251 sys=0) SBL-OMS-00203: Error 9815388 invoking method
"GenerateReport" for Business Service "XMLP Driver Service"

ObjMgrBusServiceLog
Delete 4 0000071f4dac0984:0 2011-04-28 15:13:50 Business Service 'XMLP
Driver Service' (address: '13011208')was unregsitered at model '3e515c8'
for session ''

ObjMgrBusServiceLog Delete 4 0000071f4dac0984:0
2011-04-28 15:13:50 Business Service 'XMLP Driver Service' was deleted
at 13011208

GenericLog GenericError 1 0000071f4dac0984:0
2011-04-28 15:13:50 (bsvcmgr.cpp (1236) err=2818251 sys=0)
SBL-OMS-00203: Error 9815388 invoking method "GenerateReport" for
Business Service "XMLP Driver Service"


After some researching in the BI Publisher logs we could find the root cause for this issue in the following entries:



[042811_031350484][oracle.apps.xdo.common.xml.XSLTWrapper][ERROR] XSL error:

<Line 51, Column 346>: XML-22043: (Error) Extension function error: Method not found 'getCanonicalDate'

[042811_031350484][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) is called.
[042811_031350484][oracle.apps.xdo.template.FOProcessor][STATEMENT] clearInputs(Object) done. All inputs are cleared.
[042811_031350484][oracle.apps.xdo.template.FOProcessor][ERROR] End Memory: max=508MB, total=23MB, free=7MB
[042811_031350484][][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:91)
at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:384)
at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:98)
at oracle.apps.xdo.servlet.ReportImpl.renderBody(ReportImpl.java:502)
at oracle.apps.xdo.servlet.ReportImpl.renderReportBody(ReportImpl.java:81)
at oracle.apps.xdo.server.impl.DefaultReport.run(DefaultReport.java:44)
at oracle.apps.xdo.webservice.v11.PublicReportServiceImpl.generateReport(PublicReportServiceImpl.java:286)
at oracle.apps.xdo.webservice.v11.PublicReportService.runReport(PublicReportService.java:229)
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 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:763)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:351)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at oracle.oc4j.network.ServerSocketAcceptHandler.procClientSocket(ServerSocketAcceptHandler.java:239)
at oracle.oc4j.network.ServerSocketAcceptHandler.access$700(ServerSocketAcceptHandler.java:34)
at oracle.oc4j.network.ServerSocketAcceptHandler$AcceptHandlerHorse.run(ServerSocketAcceptHandler.java:880)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:303)
at java.lang.Thread.run(Thread.java:595)
Caused by: oracle.xdo.parser.v2.XPathException: Extension function error: Method not found 'getCanonicalDate'
at oracle.xdo.parser.v2.XSLStylesheet.flushErrors(XSLStylesheet.java:1534)
at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:521)
at oracle.xdo.parser.v2.XSLStylesheet.execute(XSLStylesheet.java:489)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:271)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:155)
at oracle.xdo.parser.v2.XSLProcessor.processXSL(XSLProcessor.java:192)
... 49 more




Most relevant entry of the aforementioned error are the following entries:



<Line 54, Column 172>: XML-22043: (Error) Extension function error: Method not found 'getCanonicalDate'<br />
Caused by: oracle.xdo.parser.v2.XPathException: Extension function error: Method not found 'getCanonicalDate'





This clearly states that this report is not being generated since this getCanonicalDate function is missing from the XSLFunctions library.



Note 764191.1
includes a technical note about an updated XSLFunctions library that
includes this new method. Following there is an excerpt from this
document detailing this new function:




"A new function has been created and included in
the standard library. The new function converts a date field in string
format from a Siebel Integration Object into canonical format. Once
converted it enables standard BI Publisher date functions to be used
without the need to convert the strings using string functions. The
updated library is attached to this technical note and can be deployed
into a Siebel BI Publisher environment by overwriting the existing
library. Please make sure to include the following function library
declaration in the report template when using this function:
<?namespace:psfn=http://www.oracle.com/XSL/Transform/java/com.siebel.xmlpublisher.reports.XSLFunctions?>"


Therefore this error might trigger when a report containing a reference to this getCanonicalFunction is developed in or migrated to an environment that does not have this updated library.


Solution


Note 764191.1
includes an updated version of this XSLFunctions library in the link
"Standard function library including canonical date function" that
includes this new getCanonicalDate function as well as other
new functions, this new library must replace the old XSLFunctions.jar
file in BI Publisher deployment under
ORACLE_HOME/oc4j_bi/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib.

Following steps are necessary in order to replace this library:

- Shutdown BI Publisher server.
- Download this new library from Note 764191.1 in <ORACLE_HOME>/oc4j_bi/j2ee/home/applications/xmlpserver/xmlpserver/WEB-INF/lib replacing the old library.
- Start your BI Publisher server.
- Test the report.


References


NOTE:1051319.1 - Troubleshooting problems with the Siebel BI Publisher integration

NOTE:764191.1 - Siebel Reports 7 Migration Guide for Reports Developers










Applies to:


Siebel CRM - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.



Symptoms


When clicking the custom report from the reports menu on the Mobile
Client, message is displayed: "BI Publisher engine failed to generate
report (SBL-RPT-50524)".

siebel.log shows following errors:
XMLPReportLog
XMLPReportError 1 000000024b180b84:0 2009-12-04 10:29:53 Error in
generating xsl file C:\Siebel\81\Client_1/xmlp/templates/QuoteHeader.xsl
in the XMLP Engine

ObjMgrBusServiceLog Error 1
000000024b180b84:0 2009-12-04 10:29:53 (xmlpadaptersvc.cpp (518))
SBL-RPT-50524: BI Publisher engine failed to generate report.

XMLPReportLog
XMLPReportError 1 000000024b180b84:0 2009-12-04 11:40:13 Report Output
file C:\Siebel\81\Client_1/xmlp/reports/Quote_1J-C2.PDF is having zero
bytes.


Cause


Generating xsl file was failed in the XMLP Engine and this lead to the
"SBL-RPT-50524: BI Publisher engine failed to generate report." error.


Solution


In Administration - BIP Reports > Report Template Registration >
select Report Name and click "Generate Xliff" button on the Mobile
Client.

This operation is only needed on the Disconnected mode.

For
more details, please refer to the "Siebel Reports Guide Version 8.1,
Rev. A August 2009 > Creating Reports > Process of Creating Custom
Reports"












Applies to:


Siebel Reports - Version: 7.7.2.12 SIA[18393] to 7.7.2.12 SIA[18393] - Release: V7 to V7
Information in this document applies to any platform.



Symptoms


When running a report under Siebel 7.7.2.12 which is based on a dataset
of over 100 records the resulting report generation will fail with an
error :



We detected an Error which may have occurred for one or more of the following reasons:

BI Publisher engine failed to generate report.(SBL-RPT-50524)


A review of the contents of the BI Publisher console will show the following errors :



[051410_061904359][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.invokeParse(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:91)
at oracle.apps.xdo.servlet.CoreProcessor.process(CoreProcessor.java:364)
at oracle.apps.xdo.servlet.CoreProcessor.generateDocument(CoreProcessor.java:97)
at oracle.apps.xdo.servlet.ReportImpl.renderBody(ReportImpl.java:596)
at oracle.apps.xdo.servlet.ReportImpl.renderReportBody(ReportImpl.java:81)
at oracle.apps.xdo.server.impl.DefaultReport.run(DefaultReport.java:44)
at oracle.apps.xdo.webservice.PublicReportService.generateReport(PublicReportService.java:368)
at oracle.apps.xdo.webservice.PublicReportService.runReport(PublicReportService.java:280)
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 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:763)
at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:711)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:368)
at com.evermind.server.http.HttpRequestHandler.doProcessRequest(HttpRequestHandler.java:866)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:448)
at com.evermind.server.http.HttpRequestHandler.serveOneRequest(HttpRequestHandler.java:216)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:117)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.java:110)
at oracle.oc4j.network.ServerSocketReadHandler$SafeRunnable.run(ServerSocketReadHandler.java:260)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:298)
at java.lang.Thread.run(Thread.java:595)
Caused by: oracle.xdo.parser.v2.XMLParseException: PI with the name 'xml' can occur only in the beginning of the document.
at oracle.xdo.parser.v2.XMLError.flushErrors1(XMLError.java:337)
at oracle.xdo.parser.v2.XMLReader.popXMLReader(XMLReader.java:528)
at oracle.xdo.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1287)
at oracle.xdo.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:314)
at oracle.xdo.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:281)
at oracle.xdo.parser.v2.XMLParser.parse(XMLParser.java:278)
... 45 more




Cause


This behavior is caused because the use of over 100 records results in
the XMLPReportServer using the uploadChunk webservice call which uploads
blocks of XML data to the BI Publisher. This is then combined to
provide the full set of data for the report which is then processed.

In
the scenario being described under Siebel 7.7.2.12 each of the chunks
which is uploaded shows its own xml header which when merged results in
an invalid set of xml data. A review of the xxx_fo_data_nn.xml file in
the BI Publisher logging directory will show evidence of this as can be
seen below :

xdo_051410_055152937_fo_data_12.xml



<?xml version="1.0" encoding="UTF-8"?><?Siebel-Property-Set EscapeNames="false"?><ListOf_ssAccount
><ssAccount
><ssAccountStatus
>Active</ssAccountStatus
.
.
><ssUpdatedBy
>0-1</ssUpdatedBy
></ssAccount
><?xml version="1.0" encoding="UTF-8"?><?Siebel-Property-Set EscapeNames="false"?><ListOf_ssAccount
><ssAccount
><ssAccountStatus


When
BI Publisher parses the uploaded data it encounters these nested xml
headers and reports an error in the console for each one encountered :



[051410_055200031][oracle.apps.xdo.common.xml.XSLTWrapper][EXCEPTION] XSL error:

<Line 4403, Column 7>: XML-20109: (Fatal Error) PI with the name 'xml' can occur only in the beginning of the document.
<Line 8804, Column 7>: XML-20109: (Fatal Error) PI with the name 'xml' can occur only in the beginning of the document.
<Line 13205, Column 7>: XML-20109: (Fatal Error) PI with the name 'xml' can occur only in the beginning of the document.


and following on from this the aforementioned java stack will be reported.


Solution


A Change Request #12-1Y6LL71 "BI Publisher generates an error when a
report includes over 100 records under 7.7.2.12" has been raised for
this behavior. This request will be reviewed, analyzed, and prioritized
for possible inclusion in a future release of the application.

In order to avoid this behavior reports should be restricted to less than 100 records.










Applies to:


Siebel Reports - Version 8.1 [21039] and later
Information in this document applies to any platform.



Symptoms


When running a BI Publisher report from the Siebel web client and
having selected an output format for the report an error message is
returned :




XMLP Report Generation time exceeds the Threshold time



 If you then navigate into the Site Map > BIP Reports Server >
My Reports and try to drilldown on the generated report a different
error is returned :






SBL-SVC-00155: No file has been attached to this record. Please attach a file.


Cause


Having increased the logging levels on the XMLP Report Server
component, restarted it, and then re-tested the behavior it was evident
from a review of the log file that the timeout errors were occurring
because the XMLP Report Server component was unable to connect to the BI
Publisher Server within the Timeout period. Evidence of this can be
seen in the log file excerpt below :






EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:01:59 *** HTTP Transport Parameters:

EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:01:59 Request URL = http://xx.xx.xx.xx:9704/xmlpserver/services/PublicReportService

EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:01:59 Request Method = POST

EAITransportPerf EAITransportPerf 5 000005fb4a6f30e4:0 2009-08-04 10:02:03 Created Request Connection|4617



EAITransport EAITransportGeneric 3 000005fb4a6f30e4:0 2009-08-04
10:02:03 Dropped old connection and creating new connection for
'Request'

EAITransportPerf EAITransportPerf 5 000005fb4a6f30e4:0 2009-08-04 10:02:03 Destroyed Request Connection|2



EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:02:03 *** HTTP Transport Parameters:

EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:02:03 Request URL = http://xx.xx.xx.xx:9704/xmlpserver/services/PublicReportService

EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:02:03 Request Method = POST

EAITransportPerf EAITransportPerf 5 000005fb4a6f30e4:0 2009-08-04 10:02:03 Created Request Connection|6



EAITransport EAITransportGeneric 3 000005fb4a6f30e4:0 2009-08-04 10:02:03 Sending Request

EAITransport EAITransportDebug 4 000005fb4a6f30e4:0 2009-08-04 10:02:04 *** HTTP request Headers for Data Send Request:

User-Agent: Mozilla/4.0

Accept: text/*

SOAPAction: ""

Content-Type: text/xml; charset=UTF-8



ObjMgrLog Error 1 000005fb4a6f30e4:0 2009-08-04 10:02:05 (httptransport.cpp (1631)) SBL-EAI-04115: Cannot connect to the server

ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04
10:02:05 Business Service 'EAI HTTP Transport' invoke method
'SendReceive' Execute Time: 5.902 seconds.

ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04
10:02:05 End: Business Service 'EAI HTTP Transport' invoke method:
'SendReceive' at a231100

ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04
10:02:05 Business Service 'PublicReportService' invoke method
'runReport' Execute Time: 30.095 seconds.

ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04
10:02:05 End: Business Service 'PublicReportService' invoke method:
'runReport' at a3e0270

ObjMgrBusServiceLog Delete 4 000005fb4a6f30e4:0 2009-08-04 10:02:05
Business Service 'PublicReportService' (address: 'a3e0270')was
unregsitered at model '12ff3c0' for session ''

ObjMgrBusServiceLog Delete 4 000005fb4a6f30e4:0 2009-08-04 10:02:05
Business Service 'PublicReportService' was deleted at a3e0270

ObjMgrBusServiceLog Error 1 000005fb4a6f30e4:0 2009-08-04 10:02:05
(xmlpadaptersvc.cpp (1378)) SBL-EAI-04115: Cannot connect to the server

XMLPReportLog XMLPReportError 1 000005fb4a6f30e4:0 2009-08-04 10:02:05
Error in generating Report Output file
/crm/app/siebel/product/8.1.1.0/siebsrvr/xmlp/reports/Account
List1-6BGX.PDF in the XMLP Engine

ObjMgrBusServiceLog Error 1 000005fb4a6f30e4:0 2009-08-04 10:02:05
(xmlpadaptersvc.cpp (1696)) SBL-RPT-50524: BI Publisher engine failed to
generate report.

ObjMgrBusServiceLog InvokeMethod 4 000005fb4a6f30e4:0 2009-08-04
10:02:05 Business Service 'XMLP Adapter Service' invoke method
'RunBIPReport' Execute Time: 30.161 seconds.







The following additional error message may also be reported in some scenarios :



ObjMgrLog
Error 1 000022d94c891d18:0 2010-09-10 09:22:59 (httptransport.cpp
(1631)) SBL-EAI-04116: HTTP Internet Exception during 'Data Send': 'The
connection with the server was reset

', code: '12031'









Solution


As the connectivity to the BI Publisher Server had previously been
tested and confirmed as working correctly it was recommended to add some
additional code to ensure that the last connection had been cleaned up
correctly.


The following actions were performed :


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 your
application server. If you have multiple Siebel Application servers then
deploy the SRF to all the servers.



5. Test running the BIP reports.


The piece of code provided initiates a connection closure BEFORE
calling the 'SendReceive' method and in this way it ensures that there
are no stale or dead connections. The code has been written in the
'PreInvokeMethod' method which therefore gets executed before the actual
'SendReceive method is called.


ALTERNATE SOLUTION


1. Create a new 'System Preference' by navigating to Site Map > Administration Application > System Preferences view










System Preference NameSystem Preference Value
BIPServer http://[BIPServerHostname:9704]/xmlpserver/services/PublicReportService_v11



2. Create a new field in the following Business Component:





















Business Component NamePersonalization Profile
Field NameBIP Server
Calc FlgY
Calc ValueSystemPreference("BIPServer")

 3. Add the code in EAI HTTP Transport business service:




function Service_PreInvokeMethod (MethodName, Inputs, Outputs)


if((MethodName == "SendReceive" || MethodName == "Send" ) &&
(Inputs.GetProperty("HTTPRequestURLTemplate")
==TheApplication().GetProfileAttr("BIP Server")))

{

Inputs.SetProperty("HDR.Connection","close");

}












Applies to:


Siebel Reports - Version 8.0.0.10 SIA [20436] and later
Information in this document applies to any platform.



Symptoms




When attempting to run BI Publisher Report,

the following error occurs:



In XMLP Report Server log the following error is shown:





ObjMgrLog
Error 1 000008d94f563cce:0 2012-03-07 13:27:34 (soapbinding.cpp (564))
SBL-EAI-04304: Unknown Part
':oracle.apps.xdo.webservice.exception.OperationFailedException' for
Operation 'runReport' exists in SOAP message.

ObjMgrBusServiceLog Error 1 000008d94f563cce:0 2012-03-07 13:27:34
(outdisp.cpp (201)) 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".

ObjMgrBusServiceLog InvokeMethod 4 000008d94f563cce:0 2012-03-07
13:27:34 Business Service 'PublicReportService' invoke method
'runReport' Execute Time: 4.594 seconds.

ObjMgrBusServiceLog InvokeMethod 4 000008d94f563cce:0 2012-03-07
13:27:34 End: Business Service 'PublicReportService' invoke method:
'runReport' at 917a248

ObjMgrBusServiceLog Delete 4 000008d94f563cce:0 2012-03-07 13:27:34
Business Service 'PublicReportService' (address: '917a248')was
unregsitered at model '116ca50' for session ''

ObjMgrBusServiceLog Delete 4 000008d94f563cce:0 2012-03-07 13:27:34
Business Service 'PublicReportService' was deleted at 917a248

XMLPReportLog XMLPReportError 1 000008d94f563cce:0 2012-03-07 13:27:34 Invalid User Name and Password for BIP Server

ObjMgrBusServiceLog Error 1 000008d94f563cce:0 2012-03-07 13:27:34
(xmlpadaptersvc.cpp (1940)) SBL-RPT-50529: Verify BI Publisher Server
Userid and Password.

XMLPReportLog XMLPReportError 1 000008d94f563cce:0 2012-03-07 13:27:35
Error in generating Report Output file
/int-sbl-poc-01/siebel/siebsrvr/xmlp/reports/EStestreport1-9P27A4.PDF in
the XMLP Engine

ObjMgrBusServiceLog Error 1 000008d94f563cce:0 2012-03-07 13:27:35
(xmlpadaptersvc.cpp (2333)) SBL-RPT-50524: BI Publisher engine failed to
generate report.



xdo.log shows the following error:

---------------------------------



[030812_085559797][oracle.apps.xdo.common.xml.XSLTWrapper][ERROR] XSL error:



<Line 34, Column 86>: XML-22008: (Error) Namespace prefix 'ref' used but not declared.





Cause




The issue is caused because of the incorrect references to the Integration Component Fields in rtf template.



rtf template ->field Properties -> show the code = "<?ref:xdo0008?>"



So the report generation failed and xdo.log shows the error "<Line
34, Column 86>: XML-22008: (Error) Namespace prefix 'ref' used but
not declared."



Solution


1) Open the rtf template using BI Publisher Desktop

2) Load Sample XML

3) Click on 'Add Ins' Menu > Tools > Field Browser

4) Here, we can see all the fields and their codes.

5) Check for any entries similar to <?ref:xdo0007?>

6) Here, it was observed that the field (ssAccount) -> Right Click
-> BI Publisher -> Properties -> had the entry ->
(<?ref:xdo0007?>).

7) This is an invalid reference.

8) Correct the invalid references (to exact field name) in rtf template

9) Re-upload the report from Siebel and generate the report.












Applies to:


Siebel Reports - Version 8.1.1.5 SIA [21229] to 8.1.1.5 SIA [21229] [Release V8]
Microsoft Windows (32-bit)



Symptoms


When trying to upload templates from Reports - Standard Templates view, XMLPReportServer component crashes.



- CALL STACK -

sslcshar +0x521d3 = CCFLock::Lock() +0x3

SSCAXMLPSV +0xcda2 = CSSXMLPAdapterSvc::UploadReport() +0x13d2

SSCAXMLPSV +0x122db = CSSXMLPAdapterSvc::DoInvokeMethod() +0xbb

sscfom +0x188fa = CSSService::InvokeMethod() +0x1ba

SSCAXMLPSV +0x49be = CSSXMLPDriverSvc::ProcessRequest() +0xa2e

SSCAXMLPSV +0x3450 = CSSXMLPDriverSvc::DoInvokeMethod() +0x280

sscfom +0x188fa = CSSService::InvokeMethod() +0x1ba

sssabsvm +0x2a92 = LessComparison::operator()() +0x13f2

sssabsvm +0x427e = CreateSmiMThreadObj() +0xaae

siebmtshmw +0x1a2d9 = GetSmiTaskAPI() +0x1059

siebmtshmw +0x1a973 = GetSmiTaskAPI() +0x16f3

siebmtshmw +0x1b444 = GetSmiTaskAPI() +0x21c4

siebmtshmw +0x1c4f4 = GetSmiTaskAPI() +0x3274

siebmtshmw +0x1c881 = GetSmiTaskAPI() +0x3601

siebmtshmw +0x15e65 = SmiBeginTrace() +0x3155

siebmtshmw +0x1741f = GetSmiWorkQObj() +0x148f

siebmtshmw +0xc7c7 = SmiCleanupDetTask() +0x3bd7

sslcosd +0x2132 = OSDThreadPrivIsInit() +0x1d2

sslcosd +0x21bc = OSDThreadPrivIsInit() +0x25c

MSVCR71 +0x9565 = endthreadex() +0xa0

kernel32 +0x2482f = GetModuleHandleA() +0xdf



Cause


"Application Client Tempdir" parameter in XMLPReportServer component
was pointing to a network directory where user did not have Write
permission.


Before uploading the report (.rtf, .xlf, .xdo) to BIP Server, it
creates .xdo file under "Application Client Tempdir" so Write permission
is required.



Solution


Add Write permission to the network directory where "Application Client Tempdir" is pointing to.




Note: Crash could not be reproduced in 8.1.1.7FP. Instead of crashing, the following error is displayed in the detailed log:


Error while open xdo file \\NET_DIR\SBLTEMP\aclist.rtf12582914.xdo

(xmlpadaptersvc.cpp (1545)) SBL-RPT-50524: BI Publisher engine failed to generate report.
 









 














Posted by at
Labels:

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)