Microsoft Sql Server Error 7399 Linked Server
Contents |
19, 201022 Share 0 0 When setting up linked server to third-party Databases, it is recommended to run the third-party provider in out-of-process mode, because microsoft sql server error 7399 invalid authorization specification when the provider is run in-process (within the same process as SQL
Sql Server Error 7399 Access Denied
Server), then any issues with the provider can affect SQL Server process which could also result in crashing msg 7399 level 16 state 1 line 1 access denied SQL server.
To how to set a provider to run out-of-process, uncheck "Allow In Process" property of the provider: There are certain permissions error 7399 linked server oracle that have to be set on MSDAINITIALIZE to be able to initialize the provider out-of-process and run linked server queries successfully locally and remotely. MSDAINITIALIZE is a COM class that is provided by OLE DB. This class can parse OLE DB connection strings and load/initialize the provider based on property values in the connection string.Cannot Initialize The Data Source Object Of Ole Db Provider "sqlncli11" For Linked Server
MSDAINITILIAZE is initiated by users connected to SQL Server. If windows authentication is used to connect to SQL Server, then the provider is initialized under the logged in user account. If the logged in user is a SQL login, then provider is initialized under SQL Server service account. Based on the type of login used, permissions on MSDAINITIALIZE have to be provided accordingly.
When these permissions are not set for the logged in users, we get Access Denied errors as below: Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)" reported an error. Access denied. Msg 7301, Level 16, State 2, Line 1 Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "(null)". Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) An exception has occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The OLEDB Provider "MSDAORA"SERVER - Linked server creation error: OLE DB provider "SQLNCLI11" for linked server returned message "Invalid authorization specification" October 3, 2015Pinal DaveSQL, SQL Server, SQL Tips and Tricks6 commentsOne of the blog reader sent me the below mail. I always find that using the ole db provider sqlncli11 for linked server reported an error. authentication failed linked server have been of concern and trouble at a number of places. the ole db provider sqlncli11 for linked server does not contain the table So when the mail landed – well I was not surprised that there was a problem. It is common and
Invalid Authorization Specification Sql
hence the resolution for the same is also common yet not discussed. So I thought this blog will bring the nuances that I thought was the resolution and which helped our blog reader.Hi Pinal, https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider/ I have two SQL Server instances on same machine and I want to fetch data from each other. So I went ahead and created linked server. In SQL Server Management Studio, Server Objects > Right-click, Linked Servers, and then selected New linked server. I gave the remote server name as SQL16NODEB\SQL2014 and “Server type” as SQL Server as shown below.While saving I got error as belowTITLE: Microsoft SQL http://blog.sqlauthority.com/2015/10/03/sql-server-linked-server-creation-error-ole-db-provider-sqlncli11-for-linked-server-returned-message-invalid-authorization-specification/ Server Management Studio-------------------- The linked server has been created but failed a connection test. Do you want to keep the linked server? --------------------The OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014" reported an error. Authentication failed.Cannot initialize the data source object of OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014". OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014" returned message "Invalid authorization specification". (Microsoft SQL Server, Error: 7399)If I hit No, the linked server is not created. If I created Yes, linked server is created, but any query is failing with the same error.What should I do?Thanks,
and as expected, it failed with the same error.OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014" returned message "Invalid authorization specification".Msg 7399, Level 16, State 1, Procedure sp_testlinkedserver, Line 1The OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014" reported an error. Authentication failed.Msg 7303, Level 16, State 1, Procedure sp_testlinkedserver, Line 1Cannot initialize the data source object of OLE DB provider "SQLNCLI11" for linked server "SQL16NODEB\SQL2014".The message "Invalid authorization specification" means that linked server settings to connect to the server are not correct. To fix that, we need to go back
Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Working with Oracle » Linked Server with Oracle http://www.sqlservercentral.com/Forums/Topic635800-1042-1.aspx Database 12 posts,Page 1 of 212»» Linked Server with Oracle Database Rate Topic Display Mode http://stackoverflow.com/questions/5198381/linking-server-in-sql-server-2008-r2 Topic Options Author Message pbyrumpbyrum Posted Tuesday, January 13, 2009 1:32 PM SSC-Enthusiastic Group: General Forum Members Last Login: Thursday, October 29, 2015 12:41 PM Points: 113, Visits: 227 I have a 64-bit SQL Server 2005 on Windows 2003 Server Standard Edition server. I have the Oracle 11g client installed, the 64 bit version. I also have linked server an ODBC connection to the Oracle DB and that works. I have a Data Link (UDL) to access the Oracle table and that works. I also have the correct user name and password. The TNSNames.ora is good. The linked server is created successfully, and I can see where you can select Tables and Views in the Catalogs. So, everything looks good. However, when I select to view the tables, I get sql server error the following error: The OLE DB Provider "OraOLEDB.Oracle" for linked server "PBLA" reported an error. Access denied. Cannot obtain the required interface ("IID_IDBSchemaRowset") from OLE DB provider "OraOLEDB.Oracle" for linked server "PBLA". (MS SQL Server Error 7399)Any suggestions?Thank you! Post #635800 PaulB-TheOneAndOnlyPaulB-TheOneAndOnly Posted Saturday, January 17, 2009 7:42 AM Hall of Fame Group: General Forum Members Last Login: Tuesday, January 28, 2014 8:15 AM Points: 3,065, Visits: 4,639 Some people has fixed the issue by unchecking the "Allow inprocess" optionOn SQL Server Management Studio Server Objects --> Linked Servers --> Providers --> MSDAORA, right click select propertiesIt wouldn't hurt to try. _____________________________________Pablo (Paul) BerzukovAuthor of Understanding Database Administration available at Amazon and other bookstores.Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice. Post #638690 pbyrumpbyrum Posted Monday, January 19, 2009 10:04 AM SSC-Enthusiastic Group: General Forum Members Last Login: Thursday, October 29, 2015 12:41 PM Points: 113, Visits: 227 Thanks that fixed it. Post #639417 PaulB-TheOneAndOnlyPaulB-TheOneAndOnly Posted Sunday, January 25, 2009 12:45 PM Hall of Fame Group: General Forum Members Last Login: Tu
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 About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join 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 Linking Server in SQL Server 2008 R2 up vote 9 down vote favorite Can anyone guide me around to linking a server to another in SQL Server 2008 R2? I am getting the following error when trying to do so in Management Studio. The linked server has been created but failed a connection test. Do you want to keep the linked server? ADDITIONAL INFORMATION: An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo) The OLE DB provider "SQLNCLI" for linked server "CDSPM1" reported an error. Authentication failed. Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "CDSPM1". OLE DB provider "SQLNCLI" for linked server "CDSPM1" returned message "Invalid authorization specification". (Microsoft SQL Server, Error: 7399) sql-server sql-server-2008 linked-server share|improve this question edited Feb 7 '13 at 0:55 abatishchev 57.1k56215354 asked Mar 4 '11 at 19:33 Jeff 2285923 3 What's wrong with a screen shot? –Oded♦ Mar 4 '11 at 19:35 Is the login and password valid for the linked server? –jim31415 Mar 4 '11 at 20:23 add a comment| 6 Answers 6 active oldest votes up vote 7 down vote accepted Seems like Authentication problem. Test by creating the linked Server using "Server Type" as "Sql Server". Then go into "Security" and set your user mapping. As a test, create a SQL login on the remote system and specify that on the "Be made using this security context" Be sure that you can PING the "Linked Server" name first. HTH share|improve this answer answered Mar 5 '11 at 13:09 VDMT 1088 Thanks! It saved my day. Mainly the "Be made using this security context" part. –Ramon Araujo Jul 19 at 5:14 add a comment| up vote 1 down vote Use drop down and choose SQL Server Native Client instead of SQL Server share|improve this answer answered Feb 7 '13 at 0:55 abatishchev 57.1k56215354 Just selecting this worked for me immediately when nothing else did.