I want to let everyone knows that this issue is now fixed. It turns out that when we want to force an application to behave in 32 bit mode, we need to change platform target from 'Any CPU' to 'x86'. This is a tiny change that made a big impact especially when we are using x64 machines. Thank you everyone from responding to this post. --sopheap

I have two custom .net wrappers that would allow us to manage how we process SSIS. One is specifically written to handle 64 bit mode, and the 2nd one is written to handle 32 bit mode. I have update our existing .net component to reference the following dlls: It used to point to SQL 2005 location. C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SQLServer.ManagedDTS.dll C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SQLServer.DTSRuntimeWrap.dll C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SqlServer.DTSPipelineWrap.dll I am able to reference, also updated all DTS object to reference SQL 2008. Example: change IDTSComponentMetaData90 to IDTSComponentMetaData100 Everything build without error. When I execute the 64 bit mode, everything works as expected. When I execute the 32 bit mode wrapper, I gotthe following errors: SSIS Error Code DTS_e_OLDB_EXCEL_NOT_SUPPORTED: The Excel Connection Manager is not supported in the 64 bit version of SSIS, as no OLE DB provider is available. SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER... error code 0xC00F9304 My question to the forum is why does the connection manager not recognize 32 bit file?(Excell or Access) I am running this from a 64 bit server. I am also able to unit test this package by manually executing it using debug mode from this same server. Is there different set of dlls that I need to reference to make it call 32 bit ssis? No, I am not calling DTEXEC. I hope someone encounter this same issue and would be able to shed some light on this error. Thank you. --sopheap

If you run this package using the SQL Agent then you need the "use 32 bit mode" flag set. It is also possible that the PATH environmental variable has the 64 bit directory listed before the 32 one.Arthur My Blog

Which version of the Office drivers do you have installed? If you have installed the new Office 2010 drivers that are available in 64-bit, then that's your problem. Those drivers are ONLY installable in either the 32-bit version OR the 64-bit version. You can't install both bitnesses at the same time on the same machine. (Yet another confirmation that Office is NOT intended to be used in a server environment.) Talk to me now on