Publication failing - Using Dynamic Recip & One Fetch per recip.

[gleo_SRAM]

Hi,

SAP BusinessObjects BI Platform 4.2 Support Pack 7 Patch 5

I am running a publication with a webi doc as it source, using a dynamic recipients file (Excel --> Webi) and outputting Excel files to SharePoint.

The Webi document will run from Launchpad and also when I schedule it (Destination: default enterprise location) for the parameters of the recipient listing; which leads me to believe its not a data volume issue.

95% of the time the publication fails and I see the WebIntelligenceProcessingserver restarts itself after the failure.

I've checked the Knowledge base and Notes and not seeing anything like this there so any suggestions would be welcome if you have encountered this message.

With thanks

Gill

The error message I get in both our Development and Production systems is:

2019-11-26 10:40:19,073 ERROR [PublishingService:HandlerPool-70] BusinessObjects_PublicationAdminErrorLog_Instance_124294 - [Publication ID # 124294] - Scheduling document job "Cost Center Summary" (ID: 124,305) failed: publication failed: com.businessobjects.sdk.core.server.CommunicationException$UnexpectedServerException: FatalException occured. The cause was : com.crystaldecisions.enterprise.ocaframework.OCAFrameworkException$AllServicesDown: Unable to find servers in CMS [HOST]:6400 and cluster @[HOST]:6400 with kind webiserver and service null. All such servers could be down or disabled by the administrator. (FWM 01014) (FBE60502)

[96 recipients processed.]

[former_member189501]

Hello,

had they never replied back?

Thanks

[gleo_SRAM]

Apologies for such a late reply Deigo,

Yes, they came back to me. Webi had an issue with Dimension Attributes in publications which is what I was using so we made them navigational attributes and this solved the issue.

With regards

Gill

[gleo_SRAM]

An update - a call has been logged with SAP (Incident 489027/2019 - Publication failure - WebiIntelligence ProcessingS - SAP changed the status to 'in process' and they have acknowledged that its an issue and have referred the call to their development team.