4/05/2016

SAP BPC 10.1 for Microsoft, Bug Hunt

This is NOT a SQL Server related blog post.

Over the past week or so, I've been working to setup the latest version of SAP BPC 10.1 for Microsoft.  During my initial attempt to install the latest release of the software I found, validated, and submitted, to SAP, a bug in the application.

The short of this blogpost is:

BEWARE of BPC 10.1 for Microsoft, Server package 05.  The BPC service manager service crashes in a multi-server environment.

Below are the details:

I just tried to perform a 2 web server, 1 sql server install with a remote fileshare for the data path using BPC 10.1 for Microsoft, Server package 05.

Other details:
SQL 2014 SP1 CU5 Enterprise
Windows Server 2012 R2 (fully updated)

I ran into multiple issue with the fileshare, most notably, "The network name cannot be found".

After validating this issue in a second environment we "rolled back" (uninstalled/re-installed) to Server package 04 Patch Level 3 and proceeded without issue.

Here's what I pulled from the application log prior to rebuilding:
(There is a related SAP note here: 2300603.)

This is an "Unhandled exception".













The system was successfully implemented with BPC 10.1 for Microsoft, Server package 04 Patch Level 3.

On a side note, I noted a second bug.

Several stored procedures were missing from the appserver database after performing the second application install.

Take aways:
1.  If using a remote fileshare for the data path, don't use BPC 10.1 for Microsoft, Server package 05.
2.  If using a multi app server architechture, backup your appserver database prior to installing the 2nd appserver.

If anyone else has a list of known bugs, please share.


1 comment:

  1. This comment has been removed by a blog administrator.

    ReplyDelete