BPC 7.0 MS upgrade - reinitiate SSIS packages required

Hello,
We have recently upgraded from BPC 5.1 to BPC 7.0 MS version.
We have SSIS package to load Accounts (as flat file), which load the flat file into a staging table and then moved to <mbraccount>.
This setup works very fine till in BPC 5.1, after upgrade to BPC 7.0 MS and noticed that the Account - member are loaded in jumbled order. Further investigating, we found that the SSIS packages loaded to staging table in the same jumbled order and then followed to copy the same in mbraccount table.
1. Should we required to re-initiate all the SSIS packages (custom built) after BPC 7.0 MS upgrade?
2. Have SSIS packages to load other MasterData, the same procedure as above but no issues in display order of dimension members. Why is it so?
Any clue..
Thanks in advance.
Warm Regards
Uma

Hi Tim,
Thanks for the reply.
No change in the versions SQL SERVER 2005 and EXCEL 2003 for both SAP 5.1 and 7.0.112
These DM packages are customised and flow of data is as below:
Flat File --> Clear the staging table (delete from stage) --> load the flatfile data into Staging table ( via Data Flow task, Table - Fast load option) --> clear the MBR tbl --> Copy Stage into MBRACCOUNT table
Not using the SSIS bulk insert.
This works well after gone live almost for 4-5 months in BPC 5.1 and as said recently upgraded in Mid June 2009, we have issues loading MasterData in jumbled order.
Account ids are all numeric. Flat file extracted from SAP R/3 is in correct sequential order and while loading into Stagingtable.. it sorting order varies and then copied the same into Mbr<dim> table.
Should this problem be with SSIS packages? Any clues.
Warm Regards
Uma

Similar Messages

Unable to upgrade SSIS packages to SQL Server 2014

Hi there,
I'm trying to upgrade our SSIS packages from SQL Server 2012 to 2014 (in Visual Studio 2013). The wizard pops up the minute the project loads and I leave everything to default.
It errors immediately though on almost every package with the following error:
Error 0xc001000e: MyPackage: The connection "{5F69F91E-8CD7-49A7-A76A-815244411037}" is not found. This error is thrown by Connections collection when the specific connection element is not found.
That connection is a project connection manager and most definitely exists. In fact, I can open the individual package and it upgrades it for me and the package is completely fine. It seems to me that the upgrade wizard has a bug whereby it doesn't
look for project connection managers.
Any help would be greatly appreciated, otherwise I might just post it to connect as a bug.

I was able to fix it using the following steps:
Open project, "Upgrade Package Wizard" opens automatically
Select all packages, click next, some packages will fail. Ignore them, close wizard.
Open every package. A message says "Package was upgraded" for each package.
Save every package, save solution, close solution
Open the solution again. This time no "Upgrade Wizard" opens, upgrade was successful
Deploy the solution to SSIS server (my project already had package configuration)
This is what worked for me, I hope it'll help others.

SQL 2012 SSIS package runs from the command line (dtexec.exe) and completes right away ...

Hi
I’m upgrading our SSIS packages from SQL 2005 to SQL 2012 .
Everything is working fine in Visual Studio, but when I’m submitting dtexec.exe it’s finishing right away in the command line (the actual execution takes long time).
It looks to me that as the return code doesn’t pass properly.
As I have depending tasks how I can make sure all jobs will be executed in the proper order.
(We never had this issue in SQL 2005)
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn>dtexec.exe /ISSERVER "\"\SSISDB\Direct_Prod\Direct_SSIS_Package
\DD_Load_Customer.dtsx\"" /SERVER TORSQLSIS01 /ENVREFERENCE 2
Microsoft (R) SQL Server Execute Package Utility
Version 11.0.2100.60 for 32-bit
Copyright (C) Microsoft Corporation. All rights reserved.
Started: 10:21:55 AM
Execution ID: 21138.
To view the details for the execution, right-click on the Integration Services Catalog, and open the [All Executions] report
Started: 10:21:55 AM
Finished: 10:21:56 AM
Elapsed: 0.766 seconds

As per MSDN /ENVREFERENCE argument is used only by SQL Server Agent
see
https://msdn.microsoft.com/en-us/library/hh231187.aspx
below part is what it says
/Env[Reference] environment reference ID
(Optional). Specifies the environment reference (ID) that is used by the package execution, for a package that is deployed to the Integration Services server. The parameters configured to bind
to variables will use the values of the variables that are contained in the environment.
You use /Env[Reference] option together with the /ISServer and the /Server options.
This parameter is used by SQL Server Agent.
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Error while executing SSIS Package after upgrading the Oracle Client

Hello,
I am running to the below error after we upgraded the Oracle client to 11g from 10g. The source of the Data is Oracle database . Looked online but each error is pointing towards different route, Confused here any help is very much appreciated. Have to say
I am not a pro with SSIS.
SSIS package "Bentek_ISO_Package (2).dtsx" starting.
Information: 0x4004300A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80049304 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Warning: Could not open global shared memory to communicate with performance DLL; data flow performance counters are not available. To resolve, run this package as an administrator,
or on the system's console.
Information: 0x40043006 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Error: 0xC0202009 at Temp_tbl Injection Data Flow Task, OLE DB Source [1]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E14.
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80040E14 Description: "ORA-12801: error signaled in parallel query server P183, instance *****:qrmgmt2 (2)
ORA-01861: literal does not match format string".
An OLE DB record is available. Source: "OraOLEDB" Hresult: 0x80004005 Description: "ORA-12801: error signaled in parallel query server P183, instance ****:qrmgmt2 (2)
ORA-01861: literal does not match format string".
Error: 0xC004701A at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: component "OLE DB Source" (1) failed the pre-execute phase and returned error code 0xC0202009.
Information: 0x4004300B at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: "component "OLE DB Destination" (52)" wrote 0 rows.
Information: 0x40043009 at Temp_tbl Injection Data Flow Task, SSIS.Pipeline: Cleanup phase is beginning.
Task failed: Temp_tbl Injection Data Flow Task
Warning: 0x80019002 at *******: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (2) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches
the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "****** (2).dtsx" finished: Failure.

Do you have any Date conversion functions in your Oracle datetime fields? I did run into a similar issue when we upgraded the oracle client and the provider started to decipher the metadata of the date columns. The SSIS metadata conversion for the date
columns yielded dates that were not valid. I had to update my queries to use the TO_CHAR conversion to bring it out as a string and then save it to the date field.
TO_CHAR (DATE, 'MM/DD/YYYY HH24:MI:SS')
Regards, Dinesh

SSIS package Upgrade from 2005 to 2012

Hi,
We have a Solution file with 8 projects for SSIS packages. All of them are in VSS. They all have been created in 2005. Now we installed VS 2012 and SSDT on our local machines. I got latest of solution and projects from VSS on new machine. I tried to open
solution file which took me SSIS package Upgrade wizard. I followed the steps and in the last step of conversion, it displayed that it had errors. The errors are:
Error 0xc001f429: Package Upgrade: The file, "C:\SSIS\compay\hello.dtsx", could not be opened for writing. The file could be read-only, or you do not have the correct permissions.
and for some packages, it is like this:
Messages
* Information 0x40019316: : The provider name for the connection manager "OLEDBConnection" has been changed from "SQLNCLI.1" to "SQLNCLI10".
* Information 0x40019316: : The provider name for the connection manager "OLEDBConnection" has been changed from "SQLNCLI10" to "SQLNCLI11".
* Information 0x40016019: : The package format was migrated from version 2 to version 6. It must be saved to retain migration changes.
* Warning: PackageName: Found SQL Server Integration Services 2005 Script Task "ScriptTask_49664f73e0f440bbb0e7d44f01036bff" that requires migration!
* Information 0x4001601a:PackageName: The Script Task "ScriptTask_49664f73e0f440bbb0e7d44f01036bff" has been migrated. The package must be saved to retain migration changes.
* Error 0xc001f429: Package Upgrade: The file, "C:\SSIS\company\Hi.dtsx", could not be opened for writing. The file could be read-only, or you do not have the correct permissions.
But solution and all projects and packages show that they are checked out. I checked properties also. Read only checkbox is not checked.
Please suggest what to do. I appreciate your response.
Thanks,

Why didnt you check it out directly from VSS rather than going this long route? How would VSS now that file is in checked out status if you go and manually change readwrite property? I think it may be that its getting confused when you tried to save
it into its working folder as it still has status as checked in and not locked by anyone.
Can you try saving packages copies to different folder and then do the upgrade by including them onto a IS project?
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Unexpected Termination SSIS package - Issue with SSIS packages after upgrading to SQL Server 2014

Hello everyone.
We performed an upgrade of SQL Server 2012 installation to SQL Server 2014 (with last CU5 update). We found that all SSIS packages (even the simplest with just Execute SQL tasks) fail with Unexpected termination message. The issue reproduces with both new
packages (that are created from scratch with SSDT 2014) and old packages (migrated from SQL 2012).
Any ideas, please? We googled and found that it is a known issue that should have fixed with CU4. But we use CU5 and the issue is still here.
MCP

Hi. Yes...
- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="SQLISServer" />
<EventID Qualifiers="0">1</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-02-12T07:41:56.000000000Z" />
<EventRecordID>469950</EventRecordID>
<Channel>Application</Channel>
<Computer>abtru1a11.oneabbott.com</Computer>
<Security />
</System>
- <EventData>
<Data>The SSIS Execution Process could not write to the IS catalog: ABTRU1A11\DEV:SSISDB Error details: Cannot find the symmetric key 'MS_Enckey_Proj_Param_5', because it does not exist or you do not have permission.; at System.Data.SqlClient.SqlConnection.OnError(SqlException
exception, Boolean breakConnection, Action`1 wrapCloseInAction) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) at System.Data.SqlClient.TdsParser.TryRun(RunBehavior
runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData()
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream,
Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion,
Int32 timeout, Task& task, Boolean asyncWrite) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader() at Microsoft.SqlServer.IntegrationServices.Server.Shared.ExecutionParameterLoader.GetExecutionParameter() at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.StartPackage()
at Microsoft.SqlServer.IntegrationServices.Server.ISServerExec.ProjectOperator.PerformOperation()</Data>
</EventData>
</Event>
MCP

SSIS packages are failing after upgrade to SQL server 2014

Hi,
I have some SSIS packages running on SQL server 2012 .
After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
I read some articles about this and they say it not able to connect to SQL server agent job.
And, I can see that the package is running if i run manually using SQL 2012 run time.
Why its not running on SQL 2014 ?
did i miss anything while upgrading SQL server 2014 ?
Please give me some suggestions to solve this issue.
And is there any way i can change the SQL server agent 2014 to adapt this and run ?
Below is the error :
The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
errors.: This occures when CPackage::LoadFormXML fails.
Regards,
Vinodh Selvaraj.

I think you have typed this error message by yourself.
Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
You may try executing package in 32 bit mode from SQL Agent Job.
Please refer:
http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
-Vaibhav Chaudhari

SSIS packages on BPC v5

Helo Forum,
We encounter the following problem. Within an application we run a logic located in another application.
This usually works fine however in this particular instance the dimension names of the time and entity dimension is different. Hence the package ends in error as he can not find the time and entity dimension in the first application. My quetion is how can I modify the SSIS package so that the dimension name used in the logic is translated to the dimension name of the source application where I call the package.
Thanks for your help

Hi, Sanjaj,
U were right when saying that SAP BPC for NW version has SAP BW backend (not SQL Server) and that's why we don't use SSIS packages in Data Manager functionality. Instead of it we r using packages build on NetWeaver process chains (ABAP). U can get more information about BPC for NW packages at the official help page:
http://help.sap.com/saphelp_bpc70sp02/helpdata/en/af/36a94e9af0436c959b16baabb1a248/frameset.htm
The main idea is that u still have a list of standart packages that u can use (master data loading, transactional data loading, etc) and u can create your own packages build on your own process chains.
Hope that will help u,
Dzmitry

*Error executing SSIS Package from BPC 5.1*

All -
I'm trying to execute a perfectly working SSIS package from BPC 5.1. When I execute the package it instantly completes executing (Failure) with nothin written to the Log file.
After doing further analysis, we have found the root cause to be "Sequence Containers" in SSIS Packages. We can execute the same package if we remove the sequence container.
When we try to edit the SSIS package via BPC, containing the Sequence Containers", we receive the following error:
[QuerytoServer] An error occurred while getting a package information. System.InvalidCastException: Unable to cast object of type 'Microsoft.SqlServer.Dts.Runtime.Sequence' to type 'Microsoft.SqlServer.Dts.Runtime.TaskHost' at Osoft.Services.Application.DataMgr.PackageExecute.DTSX.GetPackageInfor()
When we try to edit SSIS packages via BPC, containing NO Sequence Containers", everything is wonderful.
Does anyone have any suggestions, besides removing all of the Sequence Containers and moving the tasks to the base SSIS package level?
I trully appreciate any help you guys can provide.

Hi Lars,
Could you be more specific the step you did?
1. It works fine in Visual Studio,
2. It is not working with Excel Front-end. Call the package from Excel.
3. It worked few days ago, ==> Do you mean it was working with #2 step?
I think this might be caused by authentication,
1. could you check your athentication you have for #1 and #2?
2. Did you introduce BPC DM to call the package? BPC DM uses impersonated ID even you use ID which has restrictive to use system resource, there will be no problem for the authentication.
3. As you see the log, it points FLOW task and OLEDB SOURCE, check your connection string in OLEDB SOURCE also.
Hope this helps,
Regards,
YH Seo

Upgrade Preparation: How to map applications, DTS packages, SSIS packages and reports to databases

Hi,
I am on the initial phase of upgrading SQL Server 2005 to SQL Server 2012. Right now, I'm taking as much inventory as I can from our current server, SQL Server 2005. If anyone could help me, how can I map the following:
Map applications to databases
Map DTS packages to databases
Map SSIS packages to databases
Map reports to databases
Thank you!

Some questions and suggestions:
How are we planning to upgrade whether in-place\parallel\others?
Will this be with HA[Clustered one] or with standalone?
Do you have time to do actual migration from now on and you will need to setup the environment for end to end testing for application validation so that all differences between application or system variables can be known before actual deployment?
Also, it will be good to check with Upgrade Advisor for below pointers preparedness too.
Map applications to databases: If you have already need to setup databases and logins for each and every applications then your mapping to database for applications will be lot easier and you will have less challenge.
Map DTS packages to databases: Good link to check
https://www.simple-talk.com/sql/ssis/dts-to-ssis-migration/
Map SSIS packages to databases: Good link to check
http://www.experts-exchange.com/Database/MS-SQL-Server/Q_28340818.html http://www.sqlservercentral.com/Forums/Topic1531839-2799-1.aspx
Map reports to databases -- Good link for Reporting Services if you meant that:
http://msdn.microsoft.com/en-us/library/ms143747.aspx
http://www.mssqltips.com/sqlservertip/2627/migrating-sql-reporting-services-to-a-new-server/
Good link to check other thing as well :
http://thomaslarock.com/2013/03/upgrading-to-sql-2012-ten-things-you-dont-want-to-miss/
Santosh Singh

How to build SSIS package for SAP BPC 5.0

Is the above how paper apply to BPC 5.1?
I also have two questions:
1.As we know in the Data Manager 5.1 user guide indicate that we use DTS to manage SQL Server 2000 packages,and SSIS to manage SQL Server 2005 packages.
Also in the guide, when it discuss about the data manager package, it only reference DTS, is all the DTS package discussed in that guide apply to SSIS?
2. from BPC 7.0 NW, the BPC is part of NetWeaver , what role SSIS is play here, since we know that a lot of customer of not use SQL Server as their database.

Hi JW,
The answer to your question #2 is that we won't have SSIS packages in BPC7NW since all SQL server based functionality won't be there in Netweaver version. If you use migration tools to migrate from BPC5.x to BPC7NW, it can convert SSIS packages. However any custom SSIS code would have to be converted manually. For more information, please read Ryan's blog at SAP's definitive strategy for planning technologies moving forward: What's the word on BPC, BI-IP and SRC?
Regards
Pravin

SSIS Package resources

Hello, can someone please guide me to some resources on creating SSIS packages that read data from files, load data into SQL server tables and interface with BPC using the SAP provided extensions to SSIS.
Thanks.

Hey Zack -
This is pertaining to Version 5, but the same procedures translate to later versions...
http://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2027ebee-a928-2a10-4485-b88c926f5e24
Good luck!
Sean

Multiple Convert/Dump and Load tasks in a single SSIS package?

I'd appreciate some input. We have a single data file that has about 1,000,000 rows of data spanning 28 time periods in the columns across each row. The file is too large to import at one time, and so we have created 9 different transformation files to pull subsets of the timeperiods using MVAL. The end user does not want to have to break apart the file and/or schedule 9 separate imports to bring this file in each time. So, I've attempted to create a single SSIS package that runs each of the 9 required component imports, but I'm running into the following error any time that I try to run more than one import at once:
An error occurred while running a packageException of type 'System.OutOfMemoryException' was thrown.
I've tried using a ForEach loop to simply loop through each of the transformation files and run an import for each transformation file it finds. But, I understand that SSIS doesn't release memory until the end of the ForEach loop, which would explain an out of memory issue. I then broke it out and specified 9 distinct Convert task and 9 distinct Dump and Load tasks in the package with an order of Convert 1 --> Dump and Load 1 --> Convert 2 --> Dump and Load 2, etc. This results in the same out of memory issue any time I enable it to run more than 1 convert/dump & load task in the package - they are not running simultaneously, but rather sequentially. I don't understand this. In looking at the logs, it looks like it's creating the temp files for the first import and adding them into BPC, and then creating the temp files for the second import but then fails prior to the second load. This will work for a smaller data file, but shouldn't the memory be released after the task and allow subsequent tasks to complete? Any recommendations on how to address this and automate this load?

Quick update - I created unique ssis packages for the distinct imports and called those packages from within the initial package that is kicked off through Data Manager, and I ran into the same out of memory issue. Any ideas, suggestions, or help would be greatly appreciated.
Thanks!
Josh

SSIS Package developed in SQL Server 2008 R2 Using BIDS 2008 is not working in SQL Server 2012

I am working in a Product based company.
We have given a Pre-requisites to our customers like SQL Server version should be 2008 or later.
I have developed and deployed my SSIS package in SQL Server 2008 R2 with BIDS 2008.
I have used "Script Component" in my package.
We will take only DTSX package file to the customer places and run using SQL Agent Job daily.
Who are all(Customer Environments) using SQL 2008 or R2 my package is running fine.
Who are all(Customer Environments) using SQL 2012, I am facing the below issue
The component metadata for “Script Component, clsid {874F7595-FB5F-4OFF-9BAF-FBFF825OE3EF}” could not be upgraded to the newer version of the component. The PerformUpgrade method failed.
Still the same package is running fine for some of the customers having SQL 2012.
I am getting the above error only for few customers.
Can someone please guide me how to proceed on this. Is there any solution to go without upgrading the package to SQL 2012. Because we need to maintain only one package for all customers

Hi Katherine,
I am just using the script component only for generating Identity column purpose. I will get the maximum count from the table and using this count value as Input (JurisCount in my below code) for script component and increment the counter for new records.
Finally I am mapping the Script component output value (JurisKey in my below code) to Key column of the table. That's all I am doing with Script Component.
Here is my Simple .net code
/* Microsoft SQL Server Integration Services Script Component
* Write scripts using Microsoft Visual C# 2008.
* ScriptMain is the entry point class of the script.*/
using System;
using System.Data;
using Microsoft.SqlServer.Dts.Pipeline.Wrapper;
using Microsoft.SqlServer.Dts.Runtime.Wrapper;
[Microsoft.SqlServer.Dts.Pipeline.SSISScriptComponentEntryPointAttribute]
public class ScriptMain : UserComponent
public override void PreExecute()
base.PreExecute();
Add your code here for preprocessing or remove if not needed
public override void PostExecute()
base.PostExecute();
Add your code here for postprocessing or remove if not needed
You can set read/write variables here, for example:
Variables.MyIntVar = 100
int counter = 0;
public override void Input0_ProcessInputRow(Input0Buffer Row)
if (counter == 0)
counter = Convert.ToInt32(Row.JurisCount);
Row.JurisKey = counter;
counter = counter + 1;
PAVAN MSBI

Scheduling SSIS packages through SQL Server Agent

Hello All! I have an SSIS question for BPC 7.5 installations across multiple servers. I have been rebuilding all my DTS packages over to SSIS and trying to learn this more dynamic environment. Currently I have saved a copy of all my rebuilt packages from BIDS (on web server) to the MSDB located on the SQL server. I can manually run packages from Integration Services and load data successfully. When I try to schedule packages based on the packages stored in MSDB, I get failures. The errors initially suggested I was passing over a NULL password, so I adjusted the protection level of the package to ServerStorage, as opposed to the default setting.
Now I have the following error when I schedule and run it:
Message
Executed as user: AMERICREDIT\svcbpc_ssis_dev. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 11:48:00 AM Error: 2011-02-28 11:48:02.05 Code: 0xC0010018 Source: Convert Task 2008 Description: Failed to load task "Convert Task 2008", type "OSoft.Services.Application.DataMgr.Task.SSISConvert, OSoftTaskConvert2008, Version=7.0.112.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648". The contact information for this task is "". End Error Error: 2011-02-28 11:48:02.06 Code: 0xC0010018 Source: DumpLoad Task 2008 Description: Failed to load task "DumpLoad Task 2008", type "OSoft.Services.Application.DataMgr.Task.SSISTaskDumpLoad, OSoftTaskDumpLoad2008, Version=7.0.112.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648". The contact information for this task is "". End Error Error: 2011-02-28 11:48:02.13 Code: 0xC0010026 Source: Convert Task 2008 Description: The task has failed to load. The contact information for this task is "". End Error Error: 2011-02-28 11:48:02.13 Code: 0xC0024107 Source: Convert Task 2008 Description: There were errors during task validation. End Error Error: 2011-02-28 11:48:02.13 Code: 0xC0010025 Source: Z6_VW_STAT_APLN_CURR Description: The package cannot execute because it contains tasks that failed to load. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 11:48:00 AM Finished: 11:48:02 AM Elapsed: 1.406 seconds. The package execution failed. The step failed.
It appears I cannot execute any of the BPC custom tasks in the SSIS packages. Any recommendations?

Thanks, James, your point is well taken. Originally we were importing packages into the file system, but had the same results when scheduling.
Below is the message received when I schedule a package located in the stored package file system from my web server:
Executed as user: AMERICREDIT\svcbpc_ssis_dev. Microsoft (R) SQL Server Execute Package Utility Version 10.0.2531.0 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:36:00 AM Error: 2011-03-01 10:36:02.56 Code: 0xC0010018 Source: Convert Task 2008 Description: Failed to load task "Convert Task 2008", type "OSoft.Services.Application.DataMgr.Task.SSISConvert, OSoftTaskConvert2008, Version=7.0.112.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648". The contact information for this task is "". End Error Error: 2011-03-01 10:36:02.58 Code: 0xC0010018 Source: DumpLoad Task 2008 Description: Failed to load task "DumpLoad Task 2008", type "OSoft.Services.Application.DataMgr.Task.SSISTaskDumpLoad, OSoftTaskDumpLoad2008, Version=7.0.112.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648". The contact information for this task is "". End Error Error: 2011-03-01 10:36:02.62 Code: 0xC0010026 Source: Convert Task 2008 Description: The task has failed to load. The contact information for this task is "". End Error Error: 2011-03-01 10:36:02.62 Code: 0xC0024107 Source: Convert Task 2008 Description: There were errors during task validation. End Error Error: 2011-03-01 10:36:02.62 Code: 0xC0010025 Source: Z6_VW_STAT_APLN_CURR Description: The package cannot execute because it contains tasks that failed to load. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:36:00 AM Finished: 10:36:02 AM Elapsed: 1.954 seconds. The package execution failed. The step failed.
Could this be a security thing? If so, what would my security need to be set up from the package level?

BPC 7.0 MS upgrade - reinitiate SSIS packages required

Similar Messages

Maybe you are looking for