Error 7399 Authentication
Contents |
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 linked server microsoft sql server error 7399 linked server have been of concern and trouble at a number of places. So when the microsoft sql server error 7399 invalid authorization specification mail landed – well I was not surprised that there was a problem. It is common and hence the resolution for
Sql Server Error 7399 Access Denied
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
Msg 7399 Level 16 State 1 Line 1 Access Denied
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 Server Management Studio-------------------- The linked server has error 7399 linked server oracle 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 to linked server properties and go to “security” tab and choose the proper authenti
19, 201022 0 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 same process as SQL
The Ole Db Provider Sqlncli11 For Linked Server Reported An Error. Authentication Failed
Server), then any issues with the provider can affect SQL Server process which could also cannot initialize the datasource object of ole db provider sqlncli11 for linked server result in crashing SQL server.
To how to set a provider to run out-of-process, uncheck "Allow In Process" property linked server error 7303 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 run linked server queries successfully locally and remotely. 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/ 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 the logged in user account. If the logged in user is a https://blogs.msdn.microsoft.com/dataaccesstechnologies/2010/08/19/permissions-needed-to-set-up-linked-server-with-out-of-process-provider/ 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 serverRecent PostsRecent Posts Popular TopicsPopular Topics Home Search Members http://www.sqlservercentral.com/Forums/Topic1541303-391-1.aspx Calendar Who's On Home » SQL Server 2008 » SQL https://www.experts-exchange.com/questions/28237090/SQL-Server-2012-Linked-Server-Authentication-Error-7399-7303.html Server 2008 - General » Agent Job Authentication error accessing... Agent Job Authentication error accessing linked server Rate Topic Display Mode Topic Options Author Message CarunclesCaruncles Posted Thursday, February 13, 2014 9:40 AM SSC Journeyman Group: General Forum Members Last Login: Friday, February error 7399 26, 2016 7:31 AM Points: 90, Visits: 231 I have a SQL agent job which has been running daily for a year. It fires a stored proc which populates a table then runs this statement:Exec Xp_Cmdshell 'bcp Sfidata.dbo.tblOrderDetail IN "C:\OWDCGiftOrderTransfer\tblorderdetailOWDC.txt" -n -S OWDC -U sa -P password'OWDC is a linked server at another location.I sql server error made some changes to the proc, but did not touch the line above. Now I'm getting this error when the job runs from the Agent:Date 2/13/2014 9:45:38 AMLog Job History (Export GiftOrders and GiftCerts to OWDC)Step ID 1Server VSQL2Job Name Export GiftOrders and GiftCerts to OWDCStep Name Gather Recent Gift Orders and Send DetailDuration 00:00:00Sql Severity 16Sql Message ID 7412Operator Emailed Operator Net sent Operator Paged Retries Attempted 1MessageExecuted as user: NT AUTHORITY\SYSTEM. The OLE DB provider "SQLNCLI10" for linked server "owdc" reported an error. Authentication failed. [SQLSTATE 42000] (Error 7399) Cannot initialize the data source object of OLE DB provider "SQLNCLI10" for linked server "owdc". [SQLSTATE 42000] (Error 7303) OLE DB provider "SQLNCLI10" for linked server "owdc" returned message "Invalid authorization specification". [SQLSTATE 01000] (Error 7412). NOTE: The step was retried the requested number of times (1) without succeeding. The step failed.However, I can run the proc from SSMS and it runs fine and gives no errors. Any
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > SQL Server 2012 Linked Server Authentication (Error 7399 & 7303) Want to Advertise Here? Solved SQL Server 2012 Linked Server Authentication (Error 7399 & 7303) Posted on 2013-09-11 Windows Server 2012 MS SQL Server MS SQL Server 2008 1 Verified Solution 8 Comments 7,826 Views Last Modified: 2013-09-12 I am working with SQL Server 2012 and I would like to create a linked server on a shared network drive. I have several TXT and CSV files that are ftp’d to the shared directory nightly. To avoid reimporting the files every day I thought linking the files to the shared drive was a pretty good solution. (http://www.users.drew.edu/skass/sql/TextDriver.htm) I had a similar process working on a local instance SQL Server Express 2005 / 2008 on my laptop using “login’s current security context” but once I tried to replicate the functionality on an Enterprise SQL Server I ran into several problems. I was hoping to get some suggestions on what might be configured incorrectly. I attached a screenshot of what I have set up now that doesn’t work. I attached a screen shots to show what I have configured (LnkSvr_All_01.jpg). The login SQLuser has access to \\Domain\Shared\. If I login to windows server 2012 using SQLuser, I can navigate to the shared drive using windows explorer. However in SQL server management studio, I am apparently lacking some authentication piece. Any assistance would be greatly appreciated. The test connection to the linked server failed. Additional information: An exception occurred while executing a Transaction-SQL statement or batch. (Microsoft.SqlSever.ConnectionInfo) Cannot initialize the data source object of OLE DB provider “Microsoft.Jet.OLEDB.4.0” for linked server “FTPsvr” OLE DB provider “Microsoft.Jet.OLEDB.4.0” for linked server “FTPsvr” returned message “Unspecified error”. (Microsoft SQL server, Error:7303) LnkSvr-All-01.jpg Error-7399.JPG Error-7303.JPG 0 Question by:HRISTeam Facebook Twitter LinkedIn Google LVL 14 Best Solution byDaniel_PL Hi, When you use linked server by using OLE DB provider temporary DSN is being c