Error saving package in Organize Package List after Modify Script

[brian_fitzgerald2]

We're upgrading from BPC MS 7.5 PL 6 (SQL 2008) to BPC MS 10.0 PL 15 (SQL 2012).

We have several custom DataManager packages with Script Tasks in them.

The problem we're running into is we get an error trying to save the package after it has been loaded into DataManager Organize Package List.

Steps to reproduce error with simple package

• Create a new integration solution in SSDT-BI
• Add a "Script Task" to package file (no need to add code or modify here)
• save
• Copy package file to appropriate folder under \WebFolders\
• Log into BPC into the environment/model that owns the location where the package file was placed
• Select Organize from the Data Manager menu.
• Add package to appropriate area in Organize Package List
• Modify the package from Organize Package List
• Click Modify Script button
• Click Save button
• Result is the error dialog that is attached.

We've tried every permutation we can think of and have not been successful in fix.

Has anyone out there experienced something like this?

Thanks,

Brian Fitzgerald

[former_member182709]

Hi All,

I just found two sap notes below.

1399459 - Failed to Save Package File

1406471 - Setting 32bit Runtime for package execution in 64bit BIDS

The 1st note says the cause is this problem occurs because the custom package was created in BIDS 2005 with BPC 2005 custom tasks. The solution is Rebuild the custom package in BIDS 2008 using the BPC 2008 custom tasks or install BIDS 2005 on the application server.

The 2nd note says the cause is DM runs in 32bit runtime, but the package runs with 64bitRuntime in 64bit BIDS. The solution is Set to False the Run64BitRunTime property in integration services on the project property page.

Detail reference: http://msdn.microsoft.com/en-us/library/ms141766.aspx

Since Brian's situation is that upgrading bpc from sql 2008 from sql 2012, the 1st note is more relevant. Since the 1st note is quite old, the solution may be changed to Rebuild the custom package in BIDS 2012 using the BPC 2012 custom tasks or install BIDS 2008 on the application server.

Hope this helps.

Charlie

[former_member219713]

Hi Brian,

Were you able to resolve this issue? I am experiencing the same exact problem and am searching for answers.

Thanks,

Tesh

[former_member219713]

Update: I created simple package with script task (no modifications) and recreated Brian's issue in our production environment.  The same package does not present any problems within our development environment.

Any insights or pointers in the right direction would be greatly appreciated.

Thank you.

[former_member219713]

Final Update:

This issue was resolved by adding the BPC Admin account (the account running the BPC DM COM object) to application server's administrators group.