Hi, I have a procees in SSIS 2005 which reads from a table in SQL server 2005 and writes to Excel file in the filesystem. this process work fine. Since we are performing conversion to SQL 2008 + SSIS 2008 (on a differenr server) I've developed this process in SSIS 2008, but when I executed it I got this error: "[Excel Destination [2790]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel_destination" failed with error code 0xC00F9304. There may be error messages posted before this with more information on why the AcquireConnection method call failed. [SSIS.Pipeline] Error: component "Excel Destination" (2790) failed validation and returned error code 0xC020801C." While searching this forum I read this article: http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/d85b134b-17c1-4353-be0e-60cc9585053e When I configured the SSIS Project property (under Debugging) "Run64BitRuntime" to False - the package runs fine (without any error). This package is ran via SQL Agent and this article says to set the job step to run the 32-bit dtexec - But I rather not doing it because this package is executed under certain conditions by another package (which executes several more package) and I'm afraid it will influence other packages. Can anyone offer a workaround? Is there a way to change the provider connection for excel to 64 bit? where is the place these providers are configured in SSIS? Thanks! David P.S The SSIS 2008 is installed on a server with windows server 2008 R2 operating system, 64 bit.

AFAIK, 64 bit excel drivers are not available for excel 2003/2007. Which version of excel are you using? Office 2010 has 64 bit drivers.Nitesh Rai- Please mark the post as answered if it answers your question

The Excel file I'm using is 1997-2003 format (.xls) - Although it was created by Excel 2007. So if I understand correctly - the "problem" is that the operatin system (windows server 2008) is 64 bit? because mu older server (win server 2003) was 64 bit as well... Are you familiar with another way to bypass this problem besides creating an independent step for this package? Most of my project's package are exetuted by a "hight level packge" which contains "Execute Packge" tasks and coditional split arrows. Thanks again! David

No. Whenever I have to execute a package involving excel files using SQL Agent job, I create CmdExec step type (instead SSIS step type) and calling 32 bit dtexec utility from x86 folder.Nitesh Rai- Please mark the post as answered if it answers your question

I completly understand your implementation - but I'm still a bit consufed about the reason I encounter this problem. Can you explain why I don't encounter this problem on SSIS 2005 which is installed on windows server 2003 (64 bit as well...)? Thanks, David

Hi David, Is the SSIS 2005 32 bit version? If so, it will work as expected. The SSIS execution is based on SSIS's version, not the Operation System(OS). Additionally, in order to use 64bit version Execl driver, please download and install the 64 bit Microsoft Access Database Engine 2010 from: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c06b8369-60dd-4b64-a44b-84b371ede16d&displaylang=en Thanks, Jin ChenJin Chen - MSFT

Hi Jin, Thanks for the reply. Can you please explain where can I see what if my SSIS 2005 version is 32 or 64? I coun't find this information at the help -> about menu of my visual studio 2005. I also looked for it in the "add / remove programs" - but couldn't find it. Regarding the link of Microsoft Access Database Engine 2010 - from what I read it's suppose to enable data transfer from Office Excel 2010 files to other data sources such as Microsoft SQL Server. The excel file I'm using is 2003 format (*.xls). If I install this Access Database Engine on my windows 2008 server (64 bit) - should it enable the use of SSIS 2008 data transfer proccess from SQL server 2008 to *.xls file? Thanks again! David

David, Microsoft Access Database Engine 2010 is driver, which support Office 2003 too. So, yes, it is able to transform data from Execl 2003 to SQL Server, or from SQL Server to Excel 2003 using the Microsoft Access Database Engine 2010. The esay way to check the SSIS 2005 is 32 or 64, please open C:\Program Files\Microsoft SQL Server\90\DTS\Binn, check if there is a DTExec.exe program. In a 64 bit server, if we just install 32 bit SQL Server, by default, there won't have DTExec.exe in C:\Program Files\Microsoft SQL Server\90\DTS\Binn. Thanks, Jin ChenJin Chen - MSFT

Connect to SSMS and execute this: Select SERVERPROPERTY('Edition') Nitesh Rai- Please mark the post as answered if it answers your question

When I connect to the msdb of the sql server 2005 and execute your statement I get: "Enterprise Edition (64-bit)". Are you sure it reffers to the SSIS 2005 version I use? Thanks, David

Check if there is any MsDtsSrvr.exe in %programfiles%\Microsoft SQL Server\90\DTS\Binn. If yes then you are using 64bit version of SSIS.Nitesh Rai- Please mark the post as answered if it answers your question

I found it... so I assume I use SSIS 2005 with 64 bit. In that case - my problem is even trickier than It thought, because my proccess run succesfully on SSIS 2005 (64 bit) but fails on SSIS 2008 (64 bit)... Do you thinks that installing the Access Database Engine on my windows 2008 server (64 bit) - should enable the use of SSIS 2008 data transfer proccess from SQL server 2008 to *.xls file?