microsoft office 12.0 access database engine ole db provider
Hello I have a new package witch need to export Data from SQL SERVER to Excel 2007. I use the microsoft office 12.0 access database engine ole db provider . the package run and finish successfully . while adding the configuration file to the package and trying to execute the package it fails no metter what i do. i think it's realeted to the fact that the provider expect for username and password . Does anybody knows the reason and how can i solve it beacuse i need this configuration file? Thanks,
December 26th, 2010 2:16am

why you don't use Excel Destination? you can export everything you want with excel destination to excel 2007. http://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
December 26th, 2010 3:32am

Hi Because Excel Destination is for Excel 97-2005 and not for office Excel 2007 .
December 26th, 2010 4:20am

Hi Because Excel Destination is for Excel 97-2005 and not for office Excel 2007 . if you work with SSIS 2008 , you can use Excel destination with Excel 2007. but if you have problem with excel destination, check this link for how to use oledb destination for excel 2007: http://blogs.msdn.com/b/mattm/archive/2010/04/05/exporting-to-excel-2007-xslx-vs-xslb.aspx also these links may help: http://www.sqlservercentral.com/articles/Integration+Services+%28SSIS%29/64585/ http://dbantics.blogspot.com/2008/04/office-excel-2007-and-ssis.htmlhttp://www.rad.pasfu.com
Free Windows Admin Tool Kit Click here and download it now
December 26th, 2010 4:32am

Hi Thanks for trying helping but i still have a problem. i dont have a problem running the package maually without configuration file . i know how to create a connection to excel 2007 . the problem is whike trying to run the package with the definition of the configuration file. the error is: "[Execute SQL Task] Error: Failed to acquire connection "DestinationConnectionOLEDB". Connection may not be configured correctly or you may not have the right permissions on this connection. " i cannot solve this problem.
December 26th, 2010 4:58am

Hi Krugliak, Did you get the error while running the package from a SQL Server Agent job? If so, the issue migth be caused by the ProtectionLevel setting. We can try to set it to EncryptSensitiveWithPassword to solve the issue. For more information, please see: EncryptSensitiveWithPassword: http://msdn.microsoft.com/en-us/library/ms141747.aspx Thanks, Jin Chen
Free Windows Admin Tool Kit Click here and download it now
December 27th, 2010 4:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics