Hi, I am trying to gain access to a local Access database. I tried using "Add a new datasource" which activates the Data Source configuration Wizard. I select New connection,
Select Microsoft Access Database File (.Net Framework Data Provider for OLE DB)
Browse to my MDB file.
When I select "Test Connection" I get a Test connection succeeded message
When I OK out of the Add Connection Box
I get then following message:
Unable to find the requested .Net Framework Data Provider. It may not be installed.
My question is.. what is it, where is it and how do I get it?
thanksWednesday, October 10, 2007 5:57 PM
I'm having the same problem, and I'm using Microsoft Visual Studio 2008 Version 9.0.20706.1 Beta 2, with the Microsoft .NET Framework Version 3.5.
Help me. My test connection is turning out okay, but then I get that freaky response above. I'm trying to use MySQL and have Connector installed.Saturday, November 17, 2007 11:50 PM
so is this a resolved issue? I am having the same problem, funny thing is that it worked fine on my vista machine, but downloaded and installed vb express 2008 onto my xp machine and it has the problem described above, I am still looking for the solution, but found it odd so many people post the same problem on the same thread and no answer.
Thanks in advance
RichardTuesday, June 30, 2009 9:38 AM
Same issue here with Vista 64 bit enterprise. I have installed the Oracle 11g ODAC 188.8.131.52.21 with Oracle Developer Tools for Visual Studio. VS appears to know about it as now a third data provider shows up under Oracle. If I select the "Oracle Data Provider for .NET", it finds my TNS names entry and successfully tests the connection. When I click on the OK button, I get the "Unable to find the requested .Net Framework Data Provider. It may not be installed" error dialog.
After verifying that the assembly was in C:\Windows\assembly, I checked the machine.config files
Be sure to make a backup copy of the machine.config file before doing any editing !!!
The machine.config file in C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG had an entry for the v184.108.40.206 assembly but not v220.127.116.11. Adding an entry DID NOT solve the problem.
The machine.config file in C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG did not have an entry at all for the new assembly. I added an entry (see below) and that solved the problem.
Add the following entry under
<add name="Oracle Data Provider for .NET" invariant="Oracle.DataAccess.Client" description="Oracle Data Provider for .NET" type="Oracle.DataAccess.Client.OracleClientFactory, Oracle.DataAccess, Version=18.104.22.168, Culture=neutral, PublicKeyToken=89b483f429c47342" />
Nicolaas DealTuesday, July 07, 2009 6:10 PM