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

January 7, 2017

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

Comments

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

Olu
November 13, 2023
Hi Vishal,
Thanks for all the support you give to the community.
I’m currently working on a data migration project using SSIS on Visual Studio 2015 version.
I also recently installed the 32 Bit and 64 Bit versions of Attunity v5.0. There has been no issue when I run the package from the front end interface. However, there’s an issue when I try to execute the package( saved in a .bat file) using the dtexec.exe.
I get a number of error messages. Below are some of the messages.
“Description: The connection type “MSORA” specified for connection manager “” is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name.”
Another error.
“Error: 2023-11-13 09:48:00.67
Code: 0xC00490F7
Source: Data Flow Task Data Flow Task (Oracle Destination [2])
Description: The managed pipeline component “AttunitySSISOraDst.8″ could not be loaded. The exception was: Could not load type ‘AttunitySSISOraDst.8’ from assembly ‘Microsoft.SqlServer.PipelineHost, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91’..
End Error”
Please note that the version of oracle client installed is 11G.
I need you help to fix this issue.
Thanks.
Reply
Olu
November 10, 2023
Hello Vishal,
Thank you for this as it was really helpful.
I’m currently working on a data migration project using SSIS for Visual Studio Data Tools 2015.
I have tried to install Attunity 4.0 32 bit and 64 bit but I couldn’t find the MSORA connection managers. However when I installed both Attunity 5.0 32 bit and 64 bit I can see the MSORA connection managers and it runs successfully. The issue arises when I try to execute the SSIS package (Configured as a .bat file) using dtexec.exe . I get the following error “Description: The connection type “MSORA” specified for connection manager “Connection Name” is not recognized as a valid connection manager type. Check the spelling in the connection type name. ”
The Oracle client version is 11G.
Is there something I could be doing wrong or missed?
I look forward to your response.
Thank you
Reply
Jose
November 23, 2022
hi,
If I have DB: SQL SERVER 2014 64bits and Visual Studio 2019 Community is possible to use Attunity and what can i do?
Reply
Priya
October 27, 2021
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?
Reply
1. Vishal Monpara
  October 28, 2021
  Hello Priya,
  I believe that you should be able to use “Execute SQL Statement” SSIS task to truncate Oracle table.
  Regards,
  Vishal Monpara
  Reply
Reema Kurane
June 1, 2021
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.
Reply
1. Vishal Monpara
  June 1, 2021
  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
  Reply
Gary Holbrook
January 3, 2018
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
Reply
Nidhi
March 30, 2017
Fixed my problem
Thanks a LOT
Reply