Error 7399 Sql Server 2005
Contents |
SERVER - FIX – Linked Server Error 7399 Invalid authorization specification June 11, 2016Pinal DaveSQL1 commentI have personally seen when people use Linked Server there sql server error 7399 invalid authorization specification are a number of issues from authentication to performance. These microsoft sql server error 7399 issues are part of working with something that has so many variations and permutations of sql server error 7399 linked server actually going wrong. Many a times I suggest people to keep away from it as much as possible. But it cannot happen all the times msg 7399 sql server and there are code blocks in their application that relies on 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
Query Timeout Expired Sql Server
as server type and hit OK. But SSMS would provide below errorTITLE: Microsoft SQL Server 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 "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
up Recent PostsRecent Posts Popular TopicsPopular Topics
Linked Server Query Timeout
Home Search Members Calendar Who's On Home » SQL Server execution terminated by the provider because a resource limit was reached linked server 2005 » SQL Server 2005 General Discussion » Error 7399 - Resource limit was reached Error linked server query timeout expired 7399 - Resource limit was reached Rate Topic Display Mode Topic Options Author Message tzertuchetzertuche Posted Tuesday, June 1, 2010 2:18 PM Grasshopper Group: General Forum http://blog.sqlauthority.com/2016/06/11/sql-server-fix-linked-server-error-7399-invalid-authorization-specification/ Members Last Login: Wednesday, August 7, 2013 1:37 PM Points: 20, Visits: 117 Two SQL 2005 servers speaking via Linked Server.Query will work for small date range and dataset once a longer, larger dataset is chosen we recieve the following error:OLE DB provider "SQLNCLI" for linked server "rhino" returned message "Query timeout expired".Msg http://www.sqlservercentral.com/Forums/Topic930970-149-1.aspx 7399, Level 16, State 1, Line 125The OLE DB provider "SQLNCLI" for linked server "rhino" reported an error. Execution terminated by the provider because a resource limit was reached.Msg 7421, Level 16, State 2, Line 125Cannot fetch the rowset from OLE DB provider "SQLNCLI" for linked server "rhino". .Query: Simple find gap query executed from one server to another via a linked server.SELECT LastDayNbr AS [Last Day Before Gap],NextDayNbr AS [First Day After Gap],[Gap Start] = DATEADD(DD,1,LastDayNbr), [Gap End] = DATEADD(DD,-1,NextDayNbr),[Total Number of Gap Days] = CAST(CAST(NextDayNbr AS DATETIME) -DATEADD(dd,1,LastDayNbr) AS INT) INTO #TempGapSummaryFROM (SELECT LastdayNbr = ( SELECT MAX(pos2.trans_date) AS DayNbr FROM rhino.pos_data.dbo.pos_product_activity pos2 WHERE pos2.trans_date < pos1.trans_date AND pos2.trans_date <= @NewEndDate AND pos2.cus_cd = @Chain AND pos2.POS_Freq = @POs_Freq ) ,NextdayNbr = trans_dateFROM rhino.pos_data.dbo.pos_product_activity pos1WHERE pos1.trans_date >= @NewbeginDateAND pos1.trans_date <= @NewEndDateAND pos1.cus_cd = @ChainAND pos1.POS_Freq = @pos_freq ) AS AWHERE (NextDayNbr - LastDayNbr) > 1--@MinToleranceAND (NextDayNbr - LastDaynbr) < 30--@maxToleranceORDER BY LastDayNbrCurrent Current TimeOut Para
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/5198381/linking-server-in-sql-server-2008-r2 of this site About Us Learn 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: sql server Sign up Linking Server in SQL Server 2008 R2 up vote 9 down vote favorite Can anyone guide me around to 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 sql server error 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 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 57k56214353 asked Mar 4 '11 at 19:33 Jeff 2235923 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