Ms 7399 Error
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 when
Microsoft Sql Server Error 7399 Invalid Authorization Specification
the provider is run in-process (within the same process as SQL Server), sql server error 7399 access denied then any issues with the provider can affect SQL Server process which could also result in crashing SQL msg 7399 level 16 state 1 line 1 access denied server.
To how to set a provider to run out-of-process, uncheck "Allow In Process" property of the provider: There are certain permissions that haveError 7399 Linked Server Oracle
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. MSDAINITILIAZE is initiatedMsg 7330, Level 16, State 2, Line 1
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" for linked serverSERVER - 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 msg 7399 sql server of the blog reader sent me the below mail. I always
Msg 7303, Level 16, State 1, Line 1
find that using linked server have been of concern and trouble at a number of places. sql server startup account So when the mail landed – well I was not surprised that there was a problem. It is common and hence the resolution for the same is https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider/ 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, 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 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, 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 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 p
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 http://mangalpardeshi.blogspot.com/2009/01/linked-server-error-msg-7399-level-16.html 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 http://sqlanddotnetdevelopment.blogspot.com/2012/09/linked-server-error-message-7399.html 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 sql server 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 sql server error 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 &
2The OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "" reported an error. Authentication failed.Msg7303, Level 16, State 1, Line 2Cannot initialize the data source object of OLE DB provider "Microsoft.Jet.OLEDB.4.0" for linked server "". This error generally comes only when you 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 theSQL ServerManagement Studioand go toServer Objectsand then toLinked Server.2. Right click on your Linked Server Name, and click onProperties.3. Go to Security Page. Here there are two options. You can try any one option. Select the option "Be made without using a security context" by clicking on radio button. OR Select the last option "Be made using this security context". When click on the radio button before "Be made using this security context ", the"Remotelogin" and "With password" text boxes become active to be filled in.Now in the "Remotelogin", enterAdminas theloginuser. 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. Posted by Arun Ladha at 9:55 AM Reactions: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Linked server error message 7399 1 comment: Ali ToprakFebruary 7, 2015 at 3:11 PMAllah razı olsun saatlerce bu çözümü aradımReplyDeleteAdd commentLoad more... Newer Post Older Post Home Subscribe to: Post Comments (Atom) Developer Arun Ladha View my complete profile Google+ Badge Translate Follow by Email Total Pageviews Blog Archive ► 2016 (6) ► May (1) ► February (3) ► January (2) ► 2015 (22) ► November (1) ► September (1) ► August (2) ► July (1) ► June (4) ► May (2) ► April (2) ► March (4) ► February (2) ► January (3) ► 2014 (43) ► December (4) ► November (3) ► October (3) ► September (5) ► August (3) ► July (4) ► June (3) ► May (3) ► April (4) ► March (4) ► February (4) ► January (3) ► 2013 (46) ► December (4) ► November (3) ► October (3) ► September (5) ► August (4) ► July (3) ► June (3) ► May (3) ► A