BPC NW Publication Error

[former_member662689]

I am new to BPC (trying to learn!)

We have an issue publishing books to a SharePoint Portal.

I am using BPC Add-In 10.0 SP 20 Patch 2 .NET 3.50, Build 9063 installed locally.

I am using SAP BPC for Netweaver 10.1

I am publishing a Book to a single PDF containing 19 sheets.

I start up Excel (so no workbooks Open), go into EPM and Book Publication.

Select all details and set to publish to a SharePoint Team Site (defined as a mapped Network Drive)

Set to run now.

However when the publish runs the first 6-8 pages show as an error and don't create in the PDF, but then all subsequent pages do not error and appear in PDF.

Error displayed is "Error while saving the file...."

If I run this to a local (desktop) directory instead of SharePoint then all is OK - all pages created in PDF with no errors.

Distribution works OK, even to the same target directory (so I don't think the issue is a connection to SharePoint or authorisation issue)

I looked in the Log File and can see error detail:

|ERROR|BookOperation|FPMXLCClient.Books.BoopOperationProcessImpl.PublicationPrinting|p01comsc|||||9|You cannot save this workbook with the same name as another open workbook or add-in. Choose a different name, or close the other workbook or add-in before saving

This is confusing, nobody else is logged in, I don't have any other sessions logged in

When I run locally I see that Excel opens a Workbook with the name of the Publish (that I entered), and another one for the worksheet the template says to use, so 3 worksheets open until process is completed and then only left with one worksheet.

However when I run to SharePoint I see different behaviour, as each sheet fails I get a Blank Excel Workbook called "Bookn.xslx" (where n is an incremental number). This is only created where there is an error. Pages that are OK don't create additional workbooks. This is probably not a cause but thought it best to mention!

Can anyone shed some light?

I have seen on another thread a suggestion to install amyuni, but how does this help?

Have also seen a suggestion to save to .xltx rather than .xlsx  but not sure if this is relevant. The underlying report on BPC is a .xlsx, but I am creating a .pdf? If this was an issue why does it fail for the first few pages and then work for the remainder of the pages?

Regards

Simon

[navip]

Hi Simon,

  Try to change the name of the files which you are going to save into the share drive.

It worked for me.

--

Naveen

[Former Member]

Hi Simon,

Try close all your opened workbook in excel before running publication.

Using the latest EPM add in is highly recommended.

Latest is SP25 patch 3.

Andy

[former_member662689]

Hi Andy

I have no Workbooks open when I start the Publication. This is why it's confusing, the only workbooks opened are the ones BPC has created, and this works OK when publishing to a Desktop folder.

Will separately have a look at SP upgrade, but this involves quite a lot of regression testing for us so can only justify this if there is a documented fix. I may look to see if I can install locally as a test. Can I just download a version to try out installing locally? Where from?

Cheers

Simon

[Former Member]

Hi Andy,

You recommended latest release. Could you please share on which release the possible fix for this issue could be?

Publishing books locally and distribution to the portal are all working fine. Only publishing to Portal does not work. Portal is a customer built SharePoint based system.

Any further idea?

Thanks

Jingjing (working on this issue together with Simon)

[Former Member]

Hi Simon,

Have a look at this sap note

http://service.sap.com/sap/support/notes/1968589

and this

http://service.sap.com/sap/support/notes/2190162

Always install the latest EPM add in, there are many fixes and enhancement in each release, this is front end, it is not the same as SP update in BW.

Andy

[former_member662689]

Thanks Andy.

I am looking to implement latest SP for EPM Add-in locally to try out to see if it fixes issue.

Good info on the 2 SAP Notes, but I don't think this is the case for us...my publication is called "test1" and it still fails.

Interestingly I tried the same publication to desktop (worked OK) and also to a Mapped Network drive (worked OK). It just failed when publish to a mapped Network drive that points to a SharePoint Team site directory.

Simon

[former_member186338]

Publish it locally or on the network drive and then using a simple script copy the results to SharePoint

Vadim

[former_member662689]

Hi Vadim

Yes I understand I can do this as a workaround, but I would need to have a job running very frequently as I don't not know when the users will run the publish.....this seems an unneccesary overhead on the system.

I think this seems to be a bug/restriction on the system and was hoping someone could point me to a solution.

Cheers

Simon

[former_member186338]

I am not sure that it's a bug... Looks like SharePoint is constantly checking the files in the folder and temporary open the files. With the job in some another folder you can put some delay...

Vadim

[former_member186338]

P.S. It's like some antivirus software behavior - any changes to the files has to be checked resulting in delays and some errors...

[former_member662689]

Is it possible to "chain" a Publish Book step and then run an external (windows) script somehow? e.. from a Package Link or a Process Chain?

Simon

[former_member186338]

"Package Link or a Process Chain" are not related to book publication...

And I don't think it's possible to launch windows script automatically after Publish Book without changing code of EPM .

[Former Member]

Hi Jing and Simon,

Have a look at this note, try SP22 EPM add in at least, I recommend the latest, SP25 patch 3.

https://launchpad.support.sap.com/#/notes/2166776

Andy

[former_member662689]

Hi Andy

I installed locally SP35 Patch Level 3, and also AmyUniPDF.

However I still get the same issue.

I can publish to a Desktop directory (so I know the underlying PDF creation is OK), but when I publish to SharePoint Team Site (via a mapped network drive), its actually worse now!  On old software (SP20 and "PDFCreator") the first few pages failed but later pages were OK and created the PDFOK. But using new software EVERY page in PDF fails when publish to SharePoint.

Any further ideas?

Regards

Simon

[former_member186338]

The issue is definitely SharePoint locking the files on the SharePoint drive... I don't think you can do a lot (may be some SharePoint expert can provide some deep configuration settings for delays etc...)

[Former Member]

Hi Simon,

That is not good to hear, open a call with SAP and see what they says.

I don't think you need external PDF converter programs to run publishing.

Andy

[former_member662689]

Hi Andy

Yes, already with SAP. They had also recommended latest patch and also the use of AmyUniPDF. I have asked to progress the call but I suspect I will need to try to push through to Development if possible to get anywhere. I am not aware that there is any certification that BPC can publish to a SharePoint Portal, so not confident I will get a definite answer though.

Will let you know if I make any progress.

Simon

[former_member186338]

I can recommend to launch Process Monitor

on the server with SharePoint share to track files activity during publication!