JohnYou ever get the error message along the lines of: “…If the 64-bit driver is not installed, run the package in 32-bit mode…Class not registered”
One of the main solutions to this is to run the package in 32-bit mode – as it states. There are often times that I need to execute a SSIS package in 32-bit mode while in development/debug or using a stored procedure to run a package in the Integration Service Catalog. Here are the ways to “flip-the-switch” to do that in both areas.
Development
Within Visual Studio, go to the project properties by one of the following methods:
- Select project in Solution Explorer -> Go to Menu -> Project -> Properties
- Right click the project in Solution Explorer and go to Properties
- Select project in Solution Explorer and press Alt + Enter
This will open the Property Pages box. Now go to Configuration Properties -> Debugging -> Change Run64BitRuntime value from True to False:
Integration Services Catalog
Assuming that you already have your package deployed to the catalog and you are using the script here, to execute. There is a @use32bitruntime parameter for the catalog.create_execution method; switch that to True:
Hopefully that helps you. If you are working with a SQL Server Agent job, there should also be a switch on the window at the bottom to use 32-bit as well.
