Skip to Content

Upgrade BPC SSIS Packages from SQL 2012 to SQL 2014


I have recently migrated and re-installed our BPC MS from BPC10.0 on SQL 2012 to BPC 10.1 MS SP05 on a SQL Server 2014 Platform.

We installed BPC on a clean Windows Server and SQL 2014 Server and then restored the Environment and ran the Migration from the Server Manager.

At this point, on the testing server, everything is all on one physical machine. (BPC + SQL + OLAP)

The Data Packages don't want to work. I get the error:

To use the SQL Server 2012 package, you must install SQL Server 2012 Integration Services, SQL Server 2012 SQL Data Tools, SQL Server 2012 Client Tools Connectivity, SQL Server 2012 Client Tools SDK, and BPC SSIS_Client 2012 on the application server.

I am battling to really understand Chapter 8 (Installing SSIS Custom Tasks) of the Installation Guide (BPC 10.1 MS, version 1.8)

At this point, I have installed the 2012 SSIS tasks and the 2014 SSIS tasks. This by unzipping the files and running OSoftSetup.exe

I have also copied the 2012 and the 2014 BPCTask*.dll files into C:\Program Files\Microsoft SQL Server\120\DTS\Tasks

Still the same error. Is it the version of the .dtsx that is wrong (somewhere in the XML) or I am missing something more fundamental?

Kind Regards


Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 14, 2017 at 01:50 PM


    I was in a similar situation. The package was one of the standard ones (like currency conversion). I copied the .dtsx file from the newly installed environment shell which solved the issue. So I am guessing that the issue is the .dtsx file.


    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Arnold,

      Thanks. Yip, I figured that out a day or two ago, too. Finally :-)

      I took the .dtsx files from Environmentshell, copied them over to my Environment and then manually changed the "Modify Script" option where it was needed (for my Data Packages). The XML for SQL 2012 .dtsx differs vastly from SQL 2014 .dtsx, it appears.

      Thanks for your help.

      Kind Regards


  • Posted on Jan 16, 2019 at 05:32 AM


    We faced a similar situation, figured out this is because of the BPC custom tasks in SSIS packages.

    You may need to recreate the SSIS packages for the Data manager package.
    Alternatively, you can create a mapping file in XML and save it at this location "C:\Program Files (x86)\Microsoft SQL Server\120\DTS\UpgradeMappings", import the SSIS packages into a project and the mapping will take care of recreation of packages.

    After the import is successful copy the SSIS packages from project directory to the target directory for DM packages and it should be working fine.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Feb 28, 2019 at 01:29 PM

    Hello Nick,

    I have posted a question related to the update of SAP BPC. Could you please have a look and leave a comment in case you have any ideas?

    Thanks in advance!

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.