Error 7399 Sql 2008
Contents |
19, 201022 0 0 0 When setting up linked server to third-party Databases, it is recommended to run the third-party
Sql Server Error 7399
provider in out-of-process mode, because when the provider is run in-process sql server error 7399 invalid authorization specification (within the same process as SQL Server), then any issues with the provider can affect SQL Server microsoft sql server error 7399 process which could also result in crashing SQL server.
To how to set a provider to run out-of-process, uncheck "Allow In Process" property of theSql Server Error 7399 Linked Server
provider:
There are certain permissions 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 andMssql 7399
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 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 reSERVER - 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. microsoft sql server error 7399 linked server I always find that using linked server have been of concern and
Microsoft Sql Server Error 7399 Invalid Authorization Specification
trouble at a number of places. So when the mail landed – well I was not surprised that there sql server error 7399 access denied was a problem. It is common and hence the resolution for the same is also common yet not discussed. So I thought this blog will bring the nuances that I thought https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider/ 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 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 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/ 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 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 pro
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 http://stackoverflow.com/questions/4153121/sql-server-linked-server-error 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 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up SQL Server Linked Server error up vote 2 down error 7399 vote favorite 1 I am using SQL Server 2008 on Windows Server 2003. I want to use a linked server to open a Visual Foxpro DBF file, using driver Microsoft OLD DB Provider for Visual Foxpro from SQL Server 2008 linked server feature. When I establish linked server connection by using Microsoft OLD DB Provider for Visual Foxpro, to open a Foxpro DBF file, I meet with the sql server error following error, any ideas what is wrong? Can not retrieve required data from this request (Microsoft.SqlServer.Management.Sdk.Src) Meeting exception when executing Transact-SQL or batch (Microsoft.SqlServer.ConnectionInfo) Error from Microsoft OLD DB Provider interface "VFPOLEDB" of linked server "DBFServer", access is defined. Can not retrieved required interface "IID_IDBSchemaRowset" from OLE DB interface "VFPOLEDB" of linked server "DBFServer" (Microsoft SQL Server error 7399) regards, George tsql sql-server-2008 linked-server foxpro visual-foxpro share|improve this question edited Nov 11 '10 at 15:28 asked Nov 11 '10 at 9:51 George2 14.9k84267422 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote accepted Check 'Allow Inprocess' on the VFPOLEDB provider: See Cindy Winegarden's answer on http://social.msdn.microsoft.com/forums/en-US/sqlreportingservices/thread/e54d20dd-b65b-4cff-9349-6499e6e069e2 for how to do it. Edit: this is the relevant part of the answer: Here's what Stepahnie posted to her thread in the microsoft.public.data.oledb NNTP newsgroup on April 10: "Finally, I found an option ' Allow inprocess' in linked server -> providers -> VFPOLEDB in MSSQL2005. With enable this option, I can connect to vfp with oledb. While diabling this option, it works only 50% with successful connection.... And I have another MSSQL2005 with the same setup (except the option 'allow inprocess' disabled), all the connection make to vfp is