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
| Application | Needed Driver | Note |
|---|---|---|
| Visual Studio 2012 | Attunity 2.0 32 bit | Visual Studio is a 32 bit application |
| Visual Studio 2012 | Attunity 2.0 64 bit | If 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 bit | Attunity 2.0 32 bit | For executing SSIS packages through SQL agent or dtexec.exe |
| SQL Server Integration Service (SSIS) 2012 – 64 bit | Attunity 2.0 64 bit | For executing SSIS packages through SQL agent or dtexec.exe |
| Visual Studio 2014 | Attunity 3.0 32 bit | Visual Studio is a 32 bit application |
| Visual Studio 2014 | Attunity 3.0 64 bit | If 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 bit | Attunity 3.0 32 bit | For executing SSIS packages through SQL agent or dtexec.exe |
| SQL Server Integration Service (SSIS) 2014 – 64 bit | Attunity 3.0 64 bit | For executing SSIS packages through SQL agent or dtexec.exe |
| SSDT 16 | Attunity 4.0 32 bit | Visual Studio/SSDT is a 32 bit application |
| SSDT 16 | Attunity 4.0 64 bit | If 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 bit | Attunity 4.0 32 bit | For executing SSIS packages through SQL agent or dtexec.exe |
| SQL Server Integration Service (SSIS) 2016 – 64 bit | Attunity 4.0 64 bit | For executing SSIS packages through SQL agent or dtexec.exe |
| SSDT 17 | Attunity 5.0 32 bit | Visual Studio/SSDT is a 32 bit application |
| SSDT 17 | Attunity 5.0 64 bit | If 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 bit | Attunity 5.0 32 bit | For executing SSIS packages through SQL agent or dtexec.exe |
| SQL Server Integration Service (SSIS) 2017 – 64 bit | Attunity 5.0 64 bit | For 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
hi,
If I have DB: SQL SERVER 2014 64bits and Visual Studio 2019 Community is possible to use Attunity and what can i do?
Hi Vishal,
We are using VS 2015 version with SSDT 14.0. I need to connect to Oracle and truncate the table before loading it. I created MSORA connection and able to load the table successfully. But how do I connect to the same connection to truncate the Oracle table? Is there any workaround to truncate the Oracle table before loading?
Hello Priya,
I believe that you should be able to use “Execute SQL Statement” SSIS task to truncate Oracle table.
Regards,
Vishal Monpara
Hello Vishal, We are using Visual Studio 2017 (build 15.9.5) with SSDT 15.1 and SSIS 15.0 and Attunity 5.0 installed. But I can’t see MSORA connector in connection manager.
We cannot install older versions of Visual Studio or SSDT. I would highly appreciate you helping me out.
Hello Reema,
Based on your setup, Attunity 5.0 32 bit (and not 64 bit) should show the connectors in connection manager.
Regards,
Vishal Monpara
Vishal, thank you for putting this together.
We are using VS 2017, so for us it is Attunity v50 (64 bit). This web page was also helpful for the Attunity versions: https://docs.microsoft.com/en-us/sql/integration-services/attunity-connectors
Again,
Thanks!
G
Fixed my problem
Thanks a LOT