9

Using Visual Studio 2013, I've added the latest version of ODP.NET Managed to a project using Nuget:

Install-Package odp.net.managed

http://www.nuget.org/packages/odp.net.managed/121.1.2

Now, when I try to run the following code:

Database db = DatabaseFactory.CreateDatabase();

It throws the following exception:

An exception of type 'System.ArgumentException' occurred 
in System.Data.dll but was not handled in user code
Additional information: Unable to find the requested .Net
Framework Data Provider.  It may not be installed.

After reading of other users's similar issues, I added the Managed driver section to C:\Windows\Microsoft.Net\Framework64\v4.0.30319\Config\machine.config:

<system.data>
        <DbProviderFactories><add name="Microsoft SQL Server Compact Data Provider 4.0" invariant="System.Data.SqlServerCe.4.0" description=".NET Framework Data Provider for Microsoft SQL Server Compact" type="System.Data.SqlServerCe.SqlCeProviderFactory, System.Data.SqlServerCe, Version=4.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>
        <add name="ODP.NET, Managed Driver" invariant="Oracle.ManagedDataAccess.Client" description="Oracle Data Provider for .NET, Managed Driver" type="Oracle.ManagedDataAccess.Client.OracleClientFactory, Oracle.ManagedDataAccess, Version=4.121.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342" />
    </DbProviderFactories>
    </system.data>

But that had no affect.

I have the connection string specified as such in my web.config, but I'm not sure if it is even looking at the connection string format as it is failing before I open the connection:

<connectionStrings>
    <add name="OneCDPBuild" 
    providerName="Oracle.ManagedDataAccess.Client" 
    connectionString="Data Source=database;user id=IDhere;pwd=passwordhere;" />
  </connectionStrings>

I added the following to my web config:

<system.data>
    <DbProviderFactories>
      <remove invariant="Oracle.ManagedDataAccess.Client" />
      <add name="ODP.NET, Managed Driver"
           invariant="Oracle.ManagedDataAccess.Client"
           description="Oracle Data Provider for .NET, Managed Driver"
           type="Oracle.ManagedDataAccess.Client.OracleClientFactory, Oracle.ManagedDataAccess, Version=4.121.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342" />
    </DbProviderFactories>
  </system.data>
  • 2
    That Nuget package was not uploaded by Oracle. It may not be doing what is required to allow ODP.NET to be seen as a provider factory. For best results, install ODP.NET managed provider from the OTN web page: http://www.oracle.com/technetwork/topics/dotnet/downloads/index.html – Christian Shay Aug 19 '14 at 18:45

3 Answers3

17

I was getting this error when deploying an ASP.NET MVC 5 application using EntityFramework 5 to our 64-bit server on which the 64-bit version of the ODAC client components were installed.

I followed b_levitt's advise and confirmed that the connection could be opened manually without using the factories, so the ODAC was installed and working, but the factory methods were unable to locate the assemblies.

After pulling my hair for an undisclosed amount of time, I figured out that the problem was with the machine.config file for the 32-bit version of the .NET framework. It did not include the entries for the oracle providers, so I manually added the following entries to this file:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\machine.config

Under 

<configuration>
  <configSections>

make sure that you have the following two section entires:

<section name="oracle.manageddataaccess.client" type="OracleInternal.Common.ODPMSectionHandler, Oracle.ManagedDataAccess, Version=4.121.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342" />
<section name="oracle.dataaccess.client" type="System.Data.Common.DbProviderConfigurationHandler, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />

You can get the exact entries from your machine.config file under the framework64 folder.

Next, under 

  <system.data>
    <DbProviderFactories>

make sure that you have the following two factory names:

  <add name="ODP.NET, Managed Driver" invariant="Oracle.ManagedDataAccess.Client" description="Oracle Data Provider for .NET, Managed Driver" type="Oracle.ManagedDataAccess.Client.OracleClientFactory, Oracle.ManagedDataAccess, Version=4.121.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342" />
  <add name="ODP.NET, Unmanaged Driver" invariant="Oracle.DataAccess.Client" description="Oracle Data Provider for .NET, Unmanaged Driver" type="Oracle.DataAccess.Client.OracleClientFactory, Oracle.DataAccess, Version=4.121.1.0, Culture=neutral, PublicKeyToken=89b483f429c47342" />

After adding these entries, everything was working for me.

Yves Rochon
  • 1,492
  • 16
  • 28
  • 3
    Why do you need both managed and unmanaged driver? Isn't the managed driver provided by Oracle suppose to replace the unmanaged one? – Ray Cheng Apr 23 '15 at 22:39
  • The machine.config holds global settings, not knowing what clients are going to be targeting (managed vs unmanaged), you may want to facilitate the usage of both. – Yves Rochon Sep 19 '17 at 23:42
9

I would start by doing a direct test and avoiding the factory methods:

var conn = new Oracle.ManagedDataAccess.Client.OracleConnection("your connection string");
conn.Open();

Any issues here will either be related to the Oracle.ManagedDataAccess.dll missing from the bin directory, or connectivity issues caused by the connection string (assuming you can already connect to the oracle instance via other means).

As for the factory, it looks like you're using some out of date enterprise library code. In later versions of the framework I believe you would use:

var factory = DbProviderFactories.GetFactory("ODP.NET, Managed Driver");
var conn = factory.CreateConnection();

I think if you take it one step at a time you'll get better feedback.

b_levitt
  • 7,059
  • 2
  • 41
  • 56
  • Future readers. I added some "System.Data.Common.DbProviderFactories.GetFactoryClasses" code on my question here : https://stackoverflow.com/questions/63248855/odp-net-managed-driver-is-failing-with-system-data-common-dbproviderfactories I upvoted this because it got me further, but my GetFactory i still failing......even though System.Data.Common.DbProviderFactories.GetFactoryClasses says "it is in there". – granadaCoder Aug 04 '20 at 14:25
4

I solved mine changing the IIS Application Pool configuration for Enable 32-bit Application to FALSE.

I was getting the exception Failed to find or load the registered .Net Framework Data Provider because the ODAC I installed is for 64-bit, and my app pool was making the app run at 32-bit.

Mariano Desanze
  • 7,847
  • 7
  • 46
  • 67