This content has been marked as final. Show 5 replies
It's a known bug.
You can also just run regsvr32 on oraoledb11.dll to register the provider 'manually' as well.
"it is a known bug."
I could not find the bug ID / do you know it / how to find it?
I am looking for an official Oracle statement saying that their installer is not registering the Oledb provider properly.
Here is what you are looking for.
NOTE> Installing the 126.96.36.199 Oracle Provider for OLE DB from the Client Install Media Does Not Properly Register the Provider [ID 1380742.1]
Bug:13417266 WHILE UPGRADING TO 188.8.131.52, INSTALLER FAILS TO REGISTER ORAOLEDB DLL
hi all !!
We have installed the client 184.108.40.206.0 , and I register the oraOLEDB , and the vb6 programs raise the error "Provider cannot be found. It may not be properly installed" , and we re install MDAC , and continue with these problem.
can you give us any sugestion?
Thanks, just ran into this issue too. The workaround of the bug is incomplete in My Oracle Support. In order to register the driver correct you need to run the regsvr32 comand from an elevated command prompt otherwhise you will get this: http://social.technet.microsoft.com/Forums/en-US/itprovistasecurity/thread/71037d62-d842-44a3-86df-6ed74df6fc39