Skip to Content
0

Upgrade BPC SSIS Packages from SQL 2012 to SQL 2014

Sep 01, 2017 at 09:41 AM

125

avatar image
Former Member

Hi,

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

Nick

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
avatar image
Former Member Sep 14, 2017 at 01:50 PM
1

Hi,

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.

Regards,
Arnold

Show 1 Share
10 |10000 characters needed characters left characters exceeded
Former Member

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

Nick

0