We Keep Coding

Unable to determine the provider name for provider factory of type > 'System.Data.SqlClient.SqlClientFactory'

Attempting to run integration tests in a project using Entity Framework 6 resulted in the error:
SetUp : System.NotSupportedException : Unable to determine the provider name for provider factory of type
'System.Data.SqlClient.SqlClientFactory'. Make sure that the ADO.NET
provider is installed or registered in the application config.
But the tests on same project works absolutely fine on several of my colleagues' machines and I have no local changes.
Have attempted reinstalling EF, I don't have any unnecessary config sections or Glimpse and I've tried targeting a different version of the framework but the error persists...

It turns out I have an empty, duplicate DbProviderFactories element in both my Framework/Framework64 machine.config files, which appears to have been created by the installation of the IBM DB2 .NET provider (?!). The duplicate node is rendering the machine.config invalid, so the issue is localised to my machine.
Modifying
<DbProviderFactories>
<add name="IBM DB2 for i5/OS .NET Provider" invariant="IBM.Data.DB2.iSeries" description=".NET Framework Data Provider for i5/OS" type="IBM.Data.DB2.iSeries.iDB2Factory, IBM.Data.DB2.iSeries, Version=12.0.0.0, Culture=neutral, PublicKeyToken=9cdb2ebfb1f93a26"/>
<add name="Microsoft SQL Server Compact Data Provider" invariant="System.Data.SqlServerCe.3.5" description=".NET Framework Data Provider for Microsoft SQL Server Compact" type="System.Data.SqlServerCe.SqlCeProviderFactory, System.Data.SqlServerCe, Version=3.5.1.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/><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"/>
</DbProviderFactories>
<DbProviderFactories/>
to remove the extra node:
<DbProviderFactories>
<add name="IBM DB2 for i5/OS .NET Provider" invariant="IBM.Data.DB2.iSeries" description=".NET Framework Data Provider for i5/OS" type="IBM.Data.DB2.iSeries.iDB2Factory, IBM.Data.DB2.iSeries, Version=12.0.0.0, Culture=neutral, PublicKeyToken=9cdb2ebfb1f93a26"/>
<add name="Microsoft SQL Server Compact Data Provider" invariant="System.Data.SqlServerCe.3.5" description=".NET Framework Data Provider for Microsoft SQL Server Compact" type="System.Data.SqlServerCe.SqlCeProviderFactory, System.Data.SqlServerCe, Version=3.5.1.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/><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"/>
</DbProviderFactories>
Resolved the issue.

ODP.NET Managed - Unable to find requested .Net Framework Data Provider

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>

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.

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.

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.

InvalidCastException in Windows Azure connecting to MySQL DB

I have just started using Azure and I am having a problem accessing the MySQL DB I set up. It appears as if Azure is referencing the MySQL.Data.dll version 6.5.4 instead of the version I require, MySQL.Data.dll v6.8.3. I receive the following error:
MySql.Data.MySqlClient.MySqlConnection cannot be cast to
MySql.Data.MySqlClient.MySqlConnection. Type A originates from
'MySql.Data, Version=6.5.4.0, Culture=neutral,
PublicKeyToken=c5687fc88969c44d' in the context 'Default' at location
'D:\Windows\Microsoft.Net\assembly\GAC_MSIL\MySql.Data\v4.0_6.5.4.0__c5687fc88969c44d\MySql.Data.dll'.
Type B originates from 'MySql.Data, Version=6.8.3.0, Culture=neutral,
PublicKeyToken=c5687fc88969c44d' in the context 'Default' at location
'C:\DWASFiles\Sites\test\Temporary ASP.NET
Files\root\fc8f3c27\4f9201b0\assembly\dl3\ca8ec5e2\74482a5e_285fcf01\MySql.Data.dll'.
I tried using my application with v6.5.4 but I require v6.8.3 for it to work. Numerous searches have not revealed a solution. Does anyone have any ideas? The checked using Web Matrix that the version in the bin directory is 6.8.3. How can I reference this correct dll?

I had the same problem.
The problem is that on the server there is installed a lower version of the MySql library.
You can bypass this modifying your web.config file:
<system.data>
<DbProviderFactories>
<remove invariant="MySql.Data.MySqlClient" />
<add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=6.8.3.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" />
</DbProviderFactories>
</system.data>

DbProviderFactory failed

With C#, Framework 4.5 and MySqL connector installed on my PC
If I tried
using MySql.Data.MySqlClient;
...
MySqlConnection tst = new MySqlConnection();
Everything works, but now
DbProviderFactory factory =
DbProviderFactories.GetFactory("MySql.Data.MySqlClient");
Raises the error :
Unable to find the requested .Net Framework Data Provider. It may not be installed.
Don't understand !?

does your config file have an entry
<system.data>
<DbProviderFactories >
<add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=6.6.5.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" />
</DbProviderFactories>
</system.data>

I have same problem with DbFactory for Firebird connections. The problem is, that it is not enough to add DbProviderFactories section to configuration file, but you must also add appropriate NuGet package to project, where you modified that config.

How do I set the absolute path for a assembly containing Database connector? MySQL Connector 6.4.3 with Entity Framework 4.1

Reason why: http://bugs.mysql.com/bug.php?id=61933
I recompiled the connector from source, incremented tit a version to 6.4.3.1, but now this (possibly) trivial question blocks me.
How do I set the full provider name in the connection string in app.config? I have the official 6.4.3 connector installed.
The error I get is when I add a new entity data model, and select from an existing database. This I traced to the above linked (silly) bug.
I couldn't find a better title for this question.
Microsoft Visual Studio
An error occurred while connecting to the database. The database might be unavailable. An exception of type 'System.Data.ProviderIncompatibleException' occurred. The error message is: 'The provider did not return a ProviderManifestToken string.
The inner exception caught was of type 'System.FormatException', with this error message: 'Input string was not in a correct format.'.'.
OK
Solution
Download MySQL Connector/6.4.3 sources, and extract it.
In the MySql.Data.Entity project, replace...:
(ProviderServices.cs:188) With: double version = double.Parse(connection.ServerVersion.Substring(0, 3), System.Globalization.CultureInfo.InvariantCulture);
(ProviderManifest.cs:73) With: double version = double.Parse(manifestToken, System.Globalization.CultureInfo.InvariantCulture);
Create a new sign key and name it ConnectorNet (same name as in the assemblyinfo.cs)
Add .1 to the AssemblyVersion in AssemblyInfo.cs in the MySql.Data project, this 1 file is shared with the rest: [assembly: AssemblyVersion("6.4.3.1")]
Put Release as target configuration, you can also disable the .Tests projects from being built.
As admin, install them with gacutil. Here you also get the public key token.
Locate Machine.config note it is important to know what .NET fx you compiled the project(s) to use.
Search for DbProviderFactories, and comment out the existing MySQL Data Provider, copy it and replace in the duplicate entry, by adding the .1 in version and the public key token.
<!-- add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=6.4.3.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" / -->
<add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=6.4.3.1, Culture=neutral, PublicKeyToken=XXXXXXXXXXXXXXX" />

Connection string doesn't contain path to provider assembly. Connection string's providerName is only reference to provider registered in system.data\DbProviderFactories:
<system.data>
<DbProviderFactories>
<remove invariant="MySql.Data.MySqlClient" />
<add name="MySQL Data Provider"
invariant="MySql.Data.MySqlClient"
description=".Net Framework Data Provider for MySQL"
type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=6.4.3.1, Culture=neutral, PublicKeyToken=YourToken" />
</system.data>
The invariant from factory registration is what you reference in providerName of connection string. You can try to put your new connector assembly to your application directory or strongly name the assembly install it to GAC.

Simpler solution: use the official 6.4.3 installer.
Go in your regional settings, change your decimal separator from ',' to '.' et voilà.
It's enough while waiting for the 6.4.4 to ship.