OraOLEDB.Oracle provider is not registered on the local machine

Question

I just migrated from XP to Win 7. I am guessing this error has to do with switching operating systems. I wrote a .net application that basically massages a large amount of d

Answer 1

Do the following test:

Open a Command Prompt and type: tnsping instance_name

where instance_name is the name of the instance you want to connect (if it's a XE database, use "tnsping xe"

If it returns ok, follow steps of Der Wolf's answer. If doesn't return ok, follow steps of Annjawn's answer.

It solved for me in both cases.

Answer 2

1. Right Click on My Computer
2. Click on properties
3. Click on Advanced System Settings
4. Click on "Environment Variables" button.
5. In the system Variable section find the "PATH" variable
6. Edit the "PATH" variable and add Oracle installation path to it (from your local machine) like ;C:\oracle\product\10.2.0\client_1\bin

Answer 3

It only worked for me after I changed the 'Platform target' to 'x64' (considering I'm using Oracle 12c 64 bits)

To do that, I did:

1. Right click on the project name (at the Solution Explorer panel locate, in general, at the left)

2. Clicked on 'Build' (in the new opened window)

3. Changed the 'Platform target' from 'Any CPU' to 'x64'

That solved the problem.

Answer 4

If you can't change compile use x64, try uninstall x64 version of odac and install 32bit version. Then, don't forget to add install directory like C:\oracle and also the child directory C:\oracle\bin to the PATH environment variable. This worked out for me in .net 4 application.

Answer 5

I had the same issue after installing the 64 bit Oracle client on Windows 7 64 bit. The solution that worked for me:

1. Open a command prompt in administrator mode
2. cd \oracle\product\11.2.0\client_64\BIN
3. c:\Windows\system32\regsvr32.exe OraOLEDB11.dll

Answer 6

My team would stumble upon this issue every now and then in random machines that we would try to install our platform in (we use oracle drivers 12c ver 12.2.0.4 but we came across this bug with other versions as well)

After quite a bit of experimentation we realized what was wrong:

Said machines would have apps that were using the machine-wide oracle drivers silently locking them and preventing the oracle driver-installer from working its magic when would attempt to upgrade/reinstall said oracle-drivers. The sneakiest "app" would be websites running in IIS and the like because these apps essentially auto-start on reboot. To counter this we do the following:

1. Disable IIS from starting automagically on restart. Do the same for any other apps/services that auto-start themselves on reboot.
2. Uninstall any previous Oracle driver and double-check that there are no traces left behind in registry or folders.
3. Reboot the machine
4. (Re)Install the Oracle drivers and re-enable IIS and other auto-start apps.
5. Reboot the machine <- This is vital. Oracle's OLE DB drivers won't work unless you reboot the machine.

If this doesn't work then rinse repeat until the OLE DB drivers work. Hope this helps someone out there struggling to figure out what's going on.