How to run SSIS packages in 32-bit mode to avoid Excel and Access errors
Part two of a three-part series of blogs

If you're using SSIS to import from or export to Excel workbooks or Access tables - as you surely will be - you'll need to run your packages in 32-bit mode. This blog explains why and how to do this.

  1. Integration Services Problem Importing Excel/Access Data
  2. Running Packages as 32-Bit in Development (this blog)
  3. Running your Packages as 32-Bit on the Server

Posted by Andy Brown on 08 January 2016

You need a minimum screen resolution of about 700 pixels width to see our blogs. This is because they contain diagrams and tables which would not be viewable easily on a mobile phone or small laptop. Please use a larger tablet, notebook or desktop computer, or change your screen resolution settings.

Running Packages as 32-Bit in Development

When you create a project, the first thing you should do is to run packages in 32-bit mode (at least, if you're importing from or exporting to Access or Excel).  Here's how to do this.

First, choose to change your project's properties:

Changing project properties

Right-click on your project in Solution Explorer, and choose to change its properties.

Now expand Configuration Properties on the left, choose the Debugging tab and reset the Run64BitRuntime property to False:

The Run64BitRuntime property

The property to change (the new property value False will appear in bold).

When you select OK, you should now be able to run your packages!

One other hint - make sure you've closed down the Excel workbook from which you're trying to import data.

This blog has 0 threads Add post