Error 7399 Oledb
Contents |
SERVER - Linked server creation error: OLE DB provider "SQLNCLI11" for linked server returned message "Invalid authorization specification" October 3, 2015Pinal DaveSQL, msg 7330, level 16, state 2, line 1 SQL Server, SQL Tips and Tricks6 commentsOne of the linked server error 7303 blog reader sent me the below mail. I always find that using linked server have cannot initialize the datasource object of ole db provider sqlncli11 for linked server been of concern and trouble at a number of places. So when the mail landed – well I was not surprised that there https://support.microsoft.com/en-us/kb/2450479 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 was the resolution and which helped our blog reader.Hi Pinal, I have two SQL Server instances 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/ 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 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
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/26267224/the-ole-db-provider-microsoft-ace-oledb-12-0-for-linked-server-null more about Stack Overflow the company Business Learn more about hiring developers or http://mangalpardeshi.blogspot.com/2009/01/linked-server-error-msg-7399-level-16.html 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 The OLE DB provider “Microsoft.ACE.OLEDB.12.0” for linked server “(null)” error 7399 up vote 8 down vote favorite 1 I'm trying to run the following statement but am receiving the error messages just below. I have researched answers to no end and none have worked for me. I'm running Office 365 (64bit). I have loaded the Microsoft Access Database Engine (64bit). This is in Visual Studio 2013 with SSDT as well as SQL Server 2012. I do not have access sql server error to changing environment or startup parameters to SQL Server. Any help is appreciated. SELECT * FROM OPENROWSET('Microsoft.ACE.OLEDB.15.0', 'Excel 12.0;Database=C:\Users\UserName\Folder\SomeFile.xlsx;;HDR=NO;IMEX=1', [Table 1$]) Msg 7399, Level 16, State 1, Line 1 The OLE DB provider "Microsoft.ACE.OLEDB.15.0" for linked server "(null)" reported an error. The provider did not give any information about the error. Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "Microsoft.ACE.OLEDB.15.0" for linked server "(null)". Here's what I have tried: First, I ran... sp_configure 'show advanced options', 1; RECONFIGURE; GO sp_configure 'Ad Hoc Distributed Queries', 1; RECONFIGURE; GO Followed by...with no love. EXEC sys.sp_addsrvrolemember @loginame = N'<
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)