Hi! I have a SSIS-package with Excel Connection Manager that fails on our x64-platform with error: Error: 2006-12-08 06:46:23.77 Code: 0xC0202009 Source: dpd2_philips Connection manager "Excel Connection Manager" Description: An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2006-12-08 06:46:23.77 Code: 0xC020801C Source: Copy Data from Blad1$ to dpd2 dbo philips Task Excel Source [107] Description: The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. End Error It's works fine on my computer (x86) and if I start the package manually on the x64-server. But I noticed that it runs under 32bit (DTExecUI.exe *32 in taskmanager) when it's started manually.Any idea? The server use dtexec.exe to start the packages. Maybe it runs under 64bit then?

Have you read this: http://msdn2.microsoft.com/en-us/library/ms141766.aspx and this: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=167907&SiteID=1

Out of curiosity, is a more graceful solution to this situation in the works? It's a lot for me to remember, much less the DBA that comes after me.Right now all our jobs that manipulate AS/400 data can run in 64 bit mode, but anything that involves reading Paradox databases, writing to Excel files, etc. has to be hacked to run in 32 bit mode. This also involves making sure ODBC is set up correctly in the 64-bit ODBC administrator, not the WoW 32-bit ODBC administrator (!).It's working fine right now, but if there was some way for SSIS to "know" all of the above (or even gracefully fallback to 32-bit ODBC settings and executables), that would be ideal.Thanks!

Hi, I ahve noticed that If we are running a package on 32 bit mode from SP & path is having Space (White Space). It was not running the package & throwing Error Path could not found. Solution: Note The package_path or filespec arguments of the /SQL, /DTS, or /FILE options must be enclosed in quotation marks if the path or file name contains a space. If the argument is not enclosed in quotation marks, the argument cannot contain white space. Permanently change the order of the paths in the PATH environment variable by placing the 32-bit path (<drive>:\ Program Files(x86)\Microsoft SQL Server\100\DTS\Binn) before the 64-bit path (<drive>:\Program Files\Microsoft SQL Server\100\DTS\Binn) in the variable. http://msdn.microsoft.com/en-us/library/ms162810(v=sql.105).aspx http://www.codeproject.com/Articles/27156/How-to-Call-SSIS-Package-from-the-Stored-ProcedureThanks Shiven:) If Answer is Helpful, Please Vote

I'm not sure if there's any relationship between your depolyment with this: Right click your project to edit its configuration At least my 64-bit platform can process excel correctly in debugging mode, I didn't try it in deployment mode. Please vote if it's helpful and mark it as an answer!