64 Bit SQL Server SSIS Packages with Excel and Access Data

If you've just switched to the 64-bit version of SQL Server and have SSIS packages that access Excel or Access, you may find that you packages stop working. That's because the JET driver that is used to access Excel and Access is 32-bit only. SSIS normally uses the 64-bit DTExec to run SSIS packages, it has not access to the 32-bit drivers. Here are some articles with all the details and work arounds

MSDN: Integration Services Considerations on 64-bit Computers
http://msdn.microsoft.com/en-us/library/ms141766(SQL.90).aspx

MSKB: How to schedule the 64-bit SQL Server Agent to run a package by using the 32-bit version of the DTExec.exe utility
http://support.microsoft.com/kb/934653

Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered"
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/b1d5de28-b80b-4f34-a135-c68e87039c58/

64 Bit SQL Server and Scheduling SSIS Packages
http://sqlblogcasts.com/blogs/lawrenso/archive/2009/06/18/64-bit-sql-server-and-scheduling-ssis-packages.aspx|

MSJET 4.0 (Excel, Access) in 64 bit environment
http://blogs.msdn.com/sqldev/archive/2008/10/22/msjet-4-0-in-64-bit-environment.aspx

MS Connect: Need 64-bit JET provider for x64 box
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=125117

Running SSIS 32-bit drivers or tasks on a 64 bit machine

MSKB: How to schedule the 64-bit SQL Server Agent to run a package by using the 32-bit version of the DTExec.exe utility

PRB: Data Transformation Services Jobs May Fail Because the Path for Dtsrun.exe Cannot Be Found (For SQL Server 2000 but it has some nice tips anyway.)

Notes for running Integration Services on 64-bit hardware, x64 and IA64.