Microsoft Sql Server Error 7302
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site microsoft sql server error 7302 oraoledb oracle About Us Learn more about Stack Overflow the company Business Learn more about
Sql Server Error 7302 Db2
hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join cannot create an instance of ole db provider for linked server the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up “Cannot create an instance of msdainitialize OLE DB provider” error as Windows Authentication user up vote 12 down vote favorite 7 I am trying to run openrowset from MS SQL Server on an Oracle server. When i execute the following command: select * from OPENROWSET('OraOLEDB.Oracle','srv';'user';'pass', 'select * from table') the following error occurs Msg 7302, Level 16, State 1, Line 1 Cannot create an instance of OLE DB provider "OraOLEDB.Oracle" for
Sql Server 2012 Error 7302
linked server "(null)". Can anyone tell me how I can use openrowset with OraOLEDB.Oracle? I am using 64 bit version of MS SQL Server and Oracle OLEDB driver. Edit I have tried this on two machines running Windows 7 x64 & Windows Server 2008 x64 with MS SQL Server 2008 x64. Both showed the same error message. sql-server oracle oledb windows-authentication linked-server share|improve this question edited Nov 21 '13 at 14:10 patrickmdnet 2,3381627 asked Jan 24 '13 at 11:14 th1rdey3 2,05441544 I am trying to run OpenQuery against my linked server and getting same error. My linked server is using OraOLEDB.Oracle provider and I have already enabled the allow In Process option. The funny part is I have been using this linked server without any issue since last week, I did sql server reboot and it suddenly started to give error. –Amit Patel Jan 24 '13 at 17:22 add a comment| 4 Answers 4 active oldest votes up vote 28 down vote In SQL Server Enterprise Manager, open \Server Objects\Linked Servers\Providers, right click on the OraOLEDB.Oracle provider, select properties and check the "Allow inprocess" option. Recreate your linked server and test again. share|impro
days looking on internet for a solution on a linked server error know as ‘7302', there are a lot of hits and the cannot initialize the data source object of ole db provider oraoledb.oracle for linked server 7303 same 3 or 4 solutions keep coming up, I tried them all cannot create an instance of ole db provider "msdasql" for linked server but no success. To save you from going through endless solutions I am going to sum up all
The 32-bit Ole Db Provider "oraoledb.oracle" Cannot Be Loaded In-process On A 64-bit Sql Server.
the possible solutions, ending with the most valuable solution, well at least it was the best fix for me. Here are links to linked server articles I wrote before: - http://stackoverflow.com/questions/14499977/cannot-create-an-instance-of-ole-db-provider-error-as-windows-authentication-u building a linked server - Creating jobs and queries with linked server Now, the dreading 7302 error Could not create an instance of OLE DB provider ‘OraOleDB' First a solution that saved our asses last time, but this won't always do the trick! "After installing a new service pack to the mssql server in 2011, the linked server stopped working, giving an http://www.thebuttonfactory.nl/?p=1503 7302 error ‘Could not create an instance of OLE DB provider ‘MSDAORA'. If your LS stops working after it has been working fine for months and all the tips above are working, i found a quick work around to get your Linked server to work again, just simply check the dynamic parameter box and save and then uncheck it again." But this time we didn't get away with it this easy, almost the same error, different solution needed once again this error occurs after a series of windows updates we performed, so we started undoing the updates, but ofcourse the error stayed. On the internet they advise you to change the DCOM security of the MSDAINITIALIZE (Acces Permissions was on Use default, change it to customize, if not already, change the other 2 in customize as well.) I added the domain user to the permission section. But this solution didn't work in my case. secondly we opened the Registry and look for: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{2206CDB0-19C1-11D1-89E0-00C04FD7A829} and change the owner to administrator, but in my case administrator was already the owner, so no luck here. (source: http://blogs.msdn.com/b/dataaccesstechnologies/archive/2011/09/28/troubleshooting-cannot-create-an-instance-of-ole-db-provider.aspx) I
he was facing while creating a Linked Server to an Oracle database. He was trying to create a Linked Server to a Oracle Database from a SQL Server 2005 instance. He had http://www.sqldbadiaries.com/2010/12/27/cannot-create-an-instance-of-ole-db-provider-oraoledb-oracle-for-linked-server/ the Oracle Client components installed on the server hosting the SQL Server instance. After giving all the details in the Linked Server properties when clicking on Ok, he would receive the following error message. Since the linked server is Oracle, the first thing that I tried was to check if the Server hosting the SQL Server instance, was able to connect to the listener on the Oracle Database Server using sql server tnsping. tnsping successfully connected to the Oracle database from the SQL Server box. Then I moved on to check the Provider details while creating the Linked Server. The Linked Server provider was Oracle Provider for OLE DB. This is the driver that gets installed along with the Oracle Client Components. This KB article states that Error 7302 can be a result of MSDAORA.dll not being registered correctly. In this case ole db provider it had to be an issue with the dll related to Oracle Provider for OLE DB i.e.OraOleDB.dll. Before checking the dll related issues, I wanted to check if something was missing in the registry. The list of Providers in the Linked Server is populated from the Providers key in the registry. This key is located under the instance name under the below key. The entries in the registry looked like this. I could not find anything unusual here. Now it was confirmed that something must be wrong with the OraOleDB.dll. This dll is located under the bin directory of the folder where Oracle Client Components are installed (usually called oracle_home). When I navigated to that folder, I could not find any such files. To confirm this, I checked that directory on a *working* instance, the OraOleDB.dll was listed there. Now my job was easy. On the server which was having issues with the Linked Server, the Oracle Client Components were either not installed correctly or it was corrupt. I copied the dll from the *working* server and pasted it under