Linked Server Error 7399 Authentication Failed
Contents |
SERVER - FIX – Linked Server Error 7399 Invalid authorization specification June 11, 2016Pinal DaveSQL1 commentI have personally seen when people use Linked Server there are a number of issues sql server error 7399 invalid authorization specification from authentication to performance. These issues are part of working with
Microsoft Sql Server Error 7399 Linked Server
something that has so many variations and permutations of actually going wrong. Many a times I sql server error 7399 access denied suggest people to keep away from it as much as possible. But it cannot happen all the times and there are code blocks in their application that relies on cannot initialize the datasource object of ole db provider sqlncli11 for linked server this as a requirement.This is one of the common error I see in various forums. When someone is new to SQL Server and tried to create a linked server, he/she would just give server name and choose SQL Server as server type and hit OK. But SSMS would provide below errorTITLE: Microsoft SQL Server Management
The Linked Server Has Been Created But Failed A Connection Test
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 "SQLNCLI11" for linked server "BIGPINAL" reported an error. Authentication failed. Cannot initialize the data source object of OLE DB provider "SQLNCLI11" for linked server "BIGPINAL". OLE DB provider "SQLNCLI11" for linked server "BIGPINAL" returned message "Invalid authorization specification". (Microsoft SQL Server, Error: 7399) -------------------- BUTTONS: &Yes &No -------------------- Above message has two messagesA Question: The linked server has been created but failed a connection test. Do you want to keep the it?An Error: Microsoft SQL Server, Error: 7399 - The OLE DB provider "%ls" for linked server "%ls" reported an error. %lsWe can click Yes and linked server would be created but it won’t work. Once we click on Test Connection as shown below – we would get same error what we go
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 when the provider is run in-process (within the msg 7399 level 16 state 1 line 1 access denied same process as SQL Server), then any issues with the provider can affect SQL the ole db provider "sqlncli11" for linked server reported an error. authentication failed. Server process which could also result in crashing SQL server.
To how to set a provider to runThe Test Connection To The Linked Server Failed Error 18456
out-of-process, uncheck "Allow In Process" property of the provider:
There are certain permissions that have to be set on MSDAINITIALIZE to be able to initialize the provider out-of-process and http://blog.sqlauthority.com/2016/06/11/sql-server-fix-linked-server-error-7399-invalid-authorization-specification/ 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. 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 https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider/ 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" for linked serverhere 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 http://stackoverflow.com/questions/5198381/linking-server-in-sql-server-2008-r2 company Business Learn more about hiring developers or posting ads with us Stack Overflow http://mangalpardeshi.blogspot.com/2009/01/linked-server-error-msg-7399-level-16.html 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 linked server 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 server error 7399 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.1k56214354 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 answer
error you get while running a query against a linked Server.You create a Linked Server with Flat Files, Excel or DBF in SQL Server using Microsoft.Jet.OLEDB.4.0 and when you try run a query against it you get the error--Error--OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server " " returned message "Cannot start your application. The workgroup information file is missing or opened exclusively by another user.".Msg 7399, Level 16, State 1, Line 2The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "" reported an error. Authentication failed.Msg 7303, Level 16, State 1, Line 2Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "".Well whatever study I have done on this particular error, I have observed that you will get this error only when try to query from a remote machine. And this is something to do with the Security Context of the Linked Server.Solution to this problem is very simple. Simply follow steps -1.Open the Management Studio and navigate to Server Objects and then to Linked Server.2.Right click on your Linked Server Name, and click on Properties.3.Go to Security Page. Now for solving above problem you have 2 option, you can try any of the below 2 option.A] Select the option "Be made without using a security context" by clicking on radio button.ORB] Select the last option "Be made using this security context ".As soon as click on the radio button before "Be made using this security context ", the"Remote login" and "With password" text boxes become active to be filled in.Now in the "Remote login", enter Admin as the login user. Leave the password text box as blank.Now just click on OK, and now can run the query against your linked server without any error.- Mangal Pardeshi. Posted by Mangal Pardeshi at Friday, January 09, 2009 Labels: Linked Server 2 comments: A3:49:00 AMHi,I'm getting the same error but it's all local. I've been searching for the answer to this error for a day now and everything I have tried only works temporarily.DREADED!ReplyDeleteDavid12:05:00 AMMangal, Option B worked for me. Keep up the good work. It saved me some timeReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2015 (10)