An SSIS error: 64-bit and Excel-2003 conflicts

Problem:

Environment: Window 7 - 64-bit, VS 9.0 64-bit

Destination: Excel 1997-2003 file

Error when running the package:

"SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "

Solution: 

Make Run64Runtime to False

Case Senstive for the VB code

Problem:

Execute Script task, got the error as below:

Error: 0x1 at Script: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Microsoft.SqlServer.Dts.Runtime.DtsRuntimeException: The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on a container during execution of the package and the element is not there.
 ---> System.Runtime.InteropServices.COMException (0xC0010009): The element cannot be found in a collection. This error happens when you try to retrieve an element from a collection on a container during execution of the package and the element is not there.

Reason:

Variable: DepartmentID

In the code, I used DepartmentId

An SSIS Error on Executing a Fuzzy Lookup

Using Visual Studio 9.0 on Win 7, I got the following error:

SSIS package "Package1.dtsx" starting.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC0209303 at Package1, Connection manager "C:\Users\CK\Documents\SQL Server 2008 Videos from LearnItFirst.com\LearnItyFirst_SSIS2008\SSIS2008_Chapter04\04_60-LookupTransformationsVsFuzzyLookupTransformations.accdb": SSIS Error Code DTS_E_OLEDB_NOPROVIDER_64BIT_ERROR.  The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered -- perhaps no 64-bit provider is available.  Error code: 0x00000000.
An OLE DB record is available.  Source: "Microsoft OLE DB Service Components"  Hresult: 0x80040154  Description: "Class not registered".
Error: 0xC020801C at Data Flow Task, OLE DB Source [1]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "C:\Users\CK\Documents\SQL Server 2008 Videos from LearnItFirst.com\LearnItyFirst_SSIS2008\SSIS2008_Chapter04\04_60-LookupTransformationsVsFuzzyLookupTransformations.accdb" failed with error code 0xC0209303.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: component "OLE DB Source" (1) failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Data Flow Task: There were errors during task validation.
SSIS package "Package1.dtsx" finished: Failure.

Changed to run64runtime to false, got the following issue:
SSIS package "04_60-LookupTransformationsVsFuzzyLookupTransformations.dtsx" starting.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.
Warning: 0x80047076 at Data Flow Task, SSIS.Pipeline: The output column "ID" (17) on output "OLE DB Source Output" (11) and component "OLE DB Source" (1) is not subsequently used in the Data Flow task. Removing this unused output column can increase Data Flow task performance.
Information: 0x40043006 at Data Flow Task, SSIS.Pipeline: Prepare for Execute phase is beginning.
Information: 0x40043007 at Data Flow Task, SSIS.Pipeline: Pre-Execute phase is beginning.
Information: 0x402090DC at Data Flow Task, Flat File Destination [316]: The processing of file "c:\Junk.txt" has started.
Information: 0x4004300C at Data Flow Task, SSIS.Pipeline: Execute phase is beginning.
SSIS package "04_60-LookupTransformationsVsFuzzyLookupTransformations.dtsx" finished: Canceled.


NO SOLUTION YET. SEE
http://connect.microsoft.com/SQLServer/feedback/details/488387/fuzzy-lookup-triggers-sqldumper-even-with-very-small-dataset-with-run64bitruntime-set-to-false

A warning sign for the Lookup task, why?

I chose to redirect rows for the no-match output. That should be it for the Lookup task. Do not need to configure the ErrorOutput tab. The options for the error should be grayed out.

Additionally, be aware of using SQL Server Destination instead of OLE DB Destination for the match and no-match outputs. The OLE DB one has the option for Error Output configuration, adding confusions....