Skip to Content
avatar image
Former Member

Publications fail

Hello,

On a BI 4.1 SP1 Platform all the publications fail and it has never worked since the installation.

The problem seems too come from Axis2 so at first I replaced the Axis2 file with another one from a working platform but no result.

Then I patched the platform with patch 1 and patch 2 but still no improvement.

Any idea?

This is the error message:

2013-10-23 11:38:41,604 INFO [PublishingService:RunInstancePool-55] BusinessObjects_PublicationAdminLog_Instance_20542 - [Publication ID # 20542] - Running publication instance.

2013-10-23 11:38:41,654 INFO [PublishingService:RunInstancePool-55] BusinessObjects_PublicationAdminLog_Instance_20542 - [Publication ID # 20542] - The global delivery rule for this publication was met; publication processing will now begin.

2013-10-23 11:38:56,260 ERROR [PublishingService:HandlerPool-47] BusinessObjects_PublicationAdminLog_Instance_20542 - [Publication ID # 20542] - An exception was caught during post-processing. (FBE60401)

org.apache.axis2.AxisFault: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]

Message: Premature end of file.

at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)

at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:123)

at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:67)

at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:354)

at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:421)

at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)

at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)

at com.businessobjects.framework.services.oca2.publishing.postprocessing.PublishingPostProcessingServiceStub.postProcess(PublishingPostProcessingServiceStub.java:182)

at com.businessobjects.sdk.oca2.publishing.postprocessing.internal.PublishingPostProcessingService.postProcess(PublishingPostProcessingService.java:66)

at com.businessobjects.publisher.postprocessing.PostProcessingHelper.postProcessScopeBatch(PostProcessingHelper.java:82)

at com.businessobjects.publisher.processing.ScopeBatchHandler.run(ScopeBatchHandler.java:148)

at com.businessobjects.publisher.processing.threadpool.TraceLogRunnableWrapper.run(TraceLogRunnableWrapper.java:29)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:743)

Caused by: org.apache.axiom.om.OMException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]

Message: Premature end of file.

at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:296)

at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.getSOAPEnvelope(StAXSOAPModelBuilder.java:198)

at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:154)

at org.apache.axiom.soap.impl.builder.StAXSOAPModelBuilder.<init>(StAXSOAPModelBuilder.java:140)

at org.apache.axis2.builder.BuilderUtil.getSOAPBuilder(BuilderUtil.java:686)

at org.apache.axis2.transport.TransportUtils.createDocumentElement(TransportUtils.java:197)

at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:145)

at org.apache.axis2.transport.TransportUtils.createSOAPMessage(TransportUtils.java:108)

... 13 more

Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1,1]

Message: Premature end of file.

at com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:599)

at org.apache.axiom.util.stax.wrapper.XMLStreamReaderWrapper.next(XMLStreamReaderWrapper.java:225)

at org.apache.axiom.util.stax.dialect.SJSXPStreamReaderWrapper.next(SJSXPStreamReaderWrapper.java:138)

at org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:668)

at org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:214)

... 20 more

2013-10-23 11:38:56,308 INFO [PublishingService:RunInstancePool-55] BusinessObjects_PublicationAdminLog_Instance_20542 - [Publication ID # 20542] - Publication scheduling complete.

Thank you in advance for your help.

Best regards,

Clotilde

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

6 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 25, 2013 at 10:34 AM

    HI

    Cause

    The server group is missing Adaptive processing server responsible for publishing and post-processing.

    Solution

    Add an Adaptive processing server to the server group to resolve the issue

    Sandeep

    Add comment
    10|10000 characters needed characters exceeded

  • Apr 01, 2014 at 07:07 PM

    I have good news. SAP BusinessObjects BI 4.1 Support Pack 3 appears to correct this publication issue. There are several ADAPT (issues) about publications listed in the fixed issued guide but none seem to address this particular problem. I built a new system using BI 4.1 SP2 build with SP3 patch applied. This is the same publication that did not work properly for me in SP2 until I reconfigured the APS as documented in this thread. It's a single Web Intelligence document and eFashion universe filtered by a profile and distributed to multiple BI Inboxes. I moved it to the new system using Promotion Management.

    I no longer had to split the Publishing Service and the Publishing Post Processing Service into separate APS, which was the workaround for SP2. Instead, I used the System Configuration Wizard's out-of-the-box "small" setting, which created 4 APS: Analysis, Auditing, Core, and Data. Both publishing services are in the Core APS as shown below.

    As a bonus, the System Configuration Wizard "small" setting no longer incorrectly creates two Client Audit Proxy Services (CAPS) like it did in earlier patch levels.

    This news is encouraging. Please share your results here if you are able to retest publications using BI 4.1 SP3.


    Add comment
    10|10000 characters needed characters exceeded

  • Aug 26, 2014 at 01:18 PM

    Does anyone have any feedback on publications with BI 4.1 SP4 or SP4 Patch 1? Good? Bad? Ugly?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Stone Jenny

      To be honest, I was helping a co-worker and we discussed the options, but I don't remember the resolution. We are running SP4 Patch 2 and I think it's all running fine now. I'll get more information and reply back.

  • avatar image
    Former Member
    Nov 05, 2013 at 09:06 PM

    I would create APS with following service in order to fix the issue and you want dedicated APS for publisher:

    Publisher Service

    Publishing Post Processing Server''

    Hope this helps!!

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 10, 2014 at 09:12 AM

    Hi All,

    Faced similar issues this morning with 4.1 SP02 Patch 1, Pre-upgrade publications were working fine with publishing service and post publishing service in a separate APS.

    To resolve looks like you may have to further split down the publishing APS created in previous set ups.

    Created a single APS one for Publishing Service and one for post publishing service and this seems to have resolved the issue.

    Cheers

    Matt

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 19, 2014 at 07:39 AM

    I thought I'd post this in case it was useful to others.


    We were facing the same issue as Dallas, running on SAP BI 4.1 SP2, and wanted a quick resolution to this issue without implementing SP3.


    So we implemented the workaround suggested in SAP Note:


    2001786 - Error:"an exception was caught during post-processing. (FBE60401)....PublishingPostProcessingService is not activated" while publishing reports in BI 4.1


    and it worked like a charm!


    Obviously the long term solution will be the implementation of SP4, but for the moment it's a valid workaround for us


    Please note that this involves disabling Introscope Enterprise Manager and it may not be a solution advisable to everyone.


    I hope it helps



    Add comment
    10|10000 characters needed characters exceeded