Hi, I recently moved from Windows XP to Windows 7 on my primary workstation, and since then I'm unable to import from Excel to SQL from any of my SSIS scripts when I run them Locally. The one instance I'm running into now is importing from Excel 2010 on my system (64-bit Windows 7) to SQL Server 2008 running on 32-bit Windows Server 2003. Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86) Jul 9 2008 14:43:34 Copyright (c) 1988-2008 Microsoft Corporation Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2) I even tried creating the import through SSMS and saving it as an SSIS script to get the same results. The only thing I can think of is the change of architecture on my workstation. I'm running 64-bit Windows 7 and the server is 32-bit Windows Server 2003 and SQL Server 2008. Below is the Validation text SSIS returns: Validation has started [SSIS.Pipeline] Information: Validation phase is beginning. Progress: Validating - 0 percent complete [Source - Sheet1$ [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "SourceConnectionExcel" 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 "Source - Sheet1$" (1) failed validation and returned error code 0xC020801C. Progress: Validating - 33 percent complete [SSIS.Pipeline] Error: One or more component failed validation. Error: There were errors during task validation. Validation is completed Any suggestions on how to get around this? I'm not seeing any errors in SQL Server itself, so I'm not sure what to try next. There are no errors reported in SQL Server or Windows. Also note, I set Delay Validation to True and still got the same error. Also the file isn't open and I even created a new Spreadsheet and copied the text minus the formatting from the old to the new spreadsheet and I'm getting the same results. Thanks -- Sam Alex

Hello Sam, it might be the issue mentioned here: http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/da076e51-8149-4948-add1-6192d8966ead/ or set the package to not use 64bit - right click on project, properties, debugging: Run64BitRuntime must be set to false.Arthur My Blog

Hello Sam, it might be the issue mentioned here: http://social.msdn.microsoft.com/forums/en-US/sqlintegrationservices/thread/da076e51-8149-4948-add1-6192d8966ead/ or set the package to not use 64bit - right click on project, properties, debugging: Run64BitRuntime must be set to false. Setting Run64BitRuntime to False did it.. Thanks, Sam

Just so you're aware, that "fix" will only work while you're running the package within BIDS. If you want to execute the package using Agent, or from the command line, you'll have to take different steps. Talk to me now on