How to Fix: “MSORA” is not recognized as a valid connection manager type

Category: SSISTags: , , ,

Error

The connection type “MSORA” specified for connection manager “” is not recognized as a valid connection manager type.

This is the most dreaded error while working with Oracle and Attunity and could not find why it would not work even after installing everything that is needed.

Edit: Updated for Attunity 4.0 and 5.0 based on RC’s comments

Technical Details

It is missing Attunity drivers only. Here is a simple table of which Attunity drivers are needed in order to fix this error

ApplicationNeeded DriverNote
Visual Studio 2012Attunity 2.0 32 bitVisual Studio is a 32 bit application
Visual Studio 2012Attunity 2.0 64 bitIf SSIS Project property > Configuration Properties > Debugging > Run64BitRunTime = true and if SSIS 2012 64 bit runtime is intalled, it needs 64 bit Attunity 2.0
SQL Server Integration Service (SSIS) 2012 – 32 bitAttunity 2.0 32 bitFor executing SSIS packages through SQL agent or dtexec.exe
SQL Server Integration Service (SSIS) 2012 – 64 bitAttunity 2.0 64 bitFor executing SSIS packages through SQL agent or dtexec.exe
Visual Studio 2014Attunity 3.0 32 bitVisual Studio is a 32 bit application
Visual Studio 2014Attunity 3.0 64 bitIf SSIS Project property > Configuration Properties > Debugging > Run64BitRunTime = true and if SSIS 2014 64 bit runtime is intalled, it needs 64 bit Attunity 3.0
SQL Server Integration Service (SSIS) 2014 – 32 bitAttunity 3.0 32 bitFor executing SSIS packages through SQL agent or dtexec.exe
SQL Server Integration Service (SSIS) 2014 – 64 bitAttunity 3.0 64 bitFor executing SSIS packages through SQL agent or dtexec.exe
SSDT 16Attunity 4.0 32 bitVisual Studio/SSDT is a 32 bit application
SSDT 16Attunity 4.0 64 bitIf SSIS Project property > Configuration Properties > Debugging > Run64BitRunTime = true and if SSIS 2016 64 bit runtime is intalled, it needs 64 bit Attunity 4.0
SQL Server Integration Service (SSIS) 2016 – 32 bitAttunity 4.0 32 bitFor executing SSIS packages through SQL agent or dtexec.exe
SQL Server Integration Service (SSIS) 2016 – 64 bitAttunity 4.0 64 bitFor executing SSIS packages through SQL agent or dtexec.exe
SSDT 17Attunity 5.0 32 bitVisual Studio/SSDT is a 32 bit application
SSDT 17Attunity 5.0 64 bitIf SSIS Project property > Configuration Properties > Debugging > Run64BitRunTime = true and if SSIS 2017 64 bit runtime is intalled, it needs 64 bit Attunity 5.0
SQL Server Integration Service (SSIS) 2017 – 32 bitAttunity 5.0 32 bitFor executing SSIS packages through SQL agent or dtexec.exe
SQL Server Integration Service (SSIS) 2017 – 64 bitAttunity 5.0 64 bitFor executing SSIS packages through SQL agent or dtexec.exe

So if you have a server which has SSIS 2014 64 bit and Visual Studio 2012 then you need to install Attunity 3.0 64 bit and Attunity 2.0 32 bit respectively for SSIS packages to execute through SSIS and Visual Studio

Share

2 comments

Your email address will not be published. Required fields are marked *

  1. Nidhi says:

    Fixed my problem
    Thanks a LOT