How to run SSIS packages in 32-bit mode to avoid Excel and Access errors
Part three 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
  3. Running your Packages as 32-Bit on the Server (this blog)

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 your Packages as 32-Bit on the Server

When you've deployed your packages (I'm assuming you're using project-level deployment in SSIS 2012 or later), you also need to be careful to execute them in 32-bit mode.

Running a package

You can right-click on a deployed package to run it.


The symptom of the problem

You can see that I ran this report 3 times before I found the answer to my problem:

Report status

The package failed 3 times, but is now working.

If I look at the error messages, they're really not that helpful:

The error messages

These errors shed almost no light on the subject.


The solution

When you choose to execute your package, a dialog box appears.  You need to tick a tiny little box!

32-bit runtime box

On the Advanced tab, be sure to tick the 32-bit runtime box shown.

I think it's fair to say that this is easy to overlook!

If you're using a stored procedure to run your package, the auto-generated script will include a parameter called @use32bitruntime, which you can set to True.

This blog has 0 threads Add post