Excel connection Manger in 64 bit

Question

Post reply

Excel connection Manger in 64 bit

sandyinfowave

Default port

Points: 1490
More actions
March 16, 2012 at 11:52 am

#391815

I know excel connection manger has some issues in 64 bit machine...i created a package in 32 bit machine and running the package in 64 bit...I forgot what change i need to make for the package to run in 64 bit machine
your help is highly appreciated
Thanks,
Sandeep

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

sqlserver8650 Ten Centuries Points: 1121 More actions · Answer 1

Hi,

Follow below steps

solution explorer-->right click

click on debugging(Left side of window) Here set Run64BitRuntime as False

I think it is useful for you

Thanks,

Mark

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 2

The suggestion of the previous poster only handles the BIDS environment.. It is not honored on the server..

What version of SQL are you using, if its 2008 or higher then in a SQL Agent job where the step is an SSIS package, goto the Execution Options tab, the option on the bottom right is "Use 32 bit runtime", this will run the step using the 32 bit DTExec exe.

CEWII

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 3

Elliott Whitlow (3/16/2012)
The suggestion of the previous poster only handles the BIDS environment.. It is not honored on the server..
What version of SQL are you using, if its 2008 or higher then in a SQL Agent job where the step is an SSIS package, goto the Execution Options tab, the option on the bottom right is "Use 32 bit runtime", this will run the step using the 32 bit DTExec exe.
CEWII

And if you're scheduling the package using another tool (or when using SQL Server Agent 2005 ), use the 32-bit DTEXEC located in the Program Files (x86) folder.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Orlando Colamatteo SSC Guru Points: 182279 More actions · Answer 4

Elliott and Koen provided ways for you to run your existing package in 32-bit mode on the server, with no changes, which may be sufficient for your case.

However, if you are required to run the package in 64-bit mode on the server it is possible, but you will need to use something other than the 32-bit Jet OLE DB provider built into SSIS to access the Excel file, meaning you will need to make changes to the SSIS package.

Here is a package that will install drivers that can be used to access Excel files for purposes of loading them into SQL Server in a 64-bit environment:

Microsoft Access Database Engine 2010 Redistributable (includes 64-bit OLEDB provider named "Microsoft.ACE.OLEDB.12.0")

Item 2 under "To use this download:"

2. If you are an application developer using OLEDB, set the Provider argument of the ConnectionString property to “Microsoft.ACE.OLEDB.12.0”
If you are connecting to Microsoft Office Excel data, add the appropriate Extended Properties of the OLEDB connection string based on the Excel file type:
File Type (extension) Extended Properties
---------------------------------------------------------------------------------------------
Excel 97-2003 Workbook (.xls) "Excel 8.0"
Excel 2007-2010 Workbook (.xlsx) "Excel 12.0 Xml"
Excel 2007-2010 Macro-enabled workbook (.xlsm) "Excel 12.0 Macro"
Excel 2007-2010 Non-XML binary workbook (.xlsb) "Excel 12.0"

There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato

sqlserver8650 Ten Centuries Points: 1121 More actions · Answer 5

sqlserver8650

Ten Centuries

Points: 1121

March 26, 2012 at 2:17 pm

#1464539

Hi

Thanks Elliott