1. Is the 'Configuration Filter' an identifier for a specific package?

Not necessarily, a single configuration filter can be shared across packages.

2. When I select 'Finish' I get the following message...

Do you get any records, if you execute the SP??

Try this...

SET NOCOUNT ON

Exec SP

The error says that the connection string is not well formed...

Try to set the variable value as follows in script component:

'For xls:

Dts.Variables("strConnectionString").Value = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=D:\sample.xls;Extended Properties=""Excel 8.0;HDR=YES"";"

'For xlsx:

Dts.Variables("strConnectionString").Value =...

I guess you are using table variable inside your SQL query. If that is the case, then OLEDB source task will not generate the columns.

Use a stored procedure instead of...

There is nothing to do with the connection string. Excel connection is not supported in 64 bit environment. Hence the package needs to be executed in 32 bit mode only.

Try...

Try including SET NOCOUNT ON in the begining of your SQL script that is used in OLEDB source task.

Yes, single script component with multiple outputs will do... instead of a conditional split task and a script for each record type.

Define a Excel Connection Manager with sample output file. Use script task to dynamically generate the Connection String and store it in a string variable. In the properties of excel...

One possible solution is to read the complete line in the file as a single column using flat file connection manager & flat file source. Use a script component to...

Hi,

I am not sure under what circumstance you would want to roll back the DFT.

I am assuming that the DFT needs to be rolled back, if any errors occur...