Error 15429 Sql Server 2005
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Setup Linked server - 2 installed instances of SQL on the same server. SQL Server > SQL Server Database null is an invalid product name sp add linked server Engine Question 0 Sign in to vote I have a server setup with 2
Login Failed For User Linked Server
separate SQL installs on it. I am trying to setup a linked server from one DB to the other, but I
Sp_addlinkedsrvlogin
cannot get it to work. I have never done this before, plus I am not very good at SQL.. I am strictly server. I have combed the internet, but I cannot find anything that works.
Sp_addlinkedserver
Currently this is what I am doing.. I am right clicking on the Linked server folder and choosing New Linked Server - The default provider is (Microsfot OLE DB Provider for SQL Server. I put the name of the server in the Linked Server area; Product name is SQL server - Data Source is the name of the SQL server as identifed in the services (Is that correct)? I recieve an error when I run it (An exception occured while executoing a Transact-SQL statement or batch, ->(Microsoft.SQLServer.ConnectionInfo)-> (Null) is an invalid product name. (Microsoft SQL Server, Error: 15429). Any help would be appreciated. Thanks, Friday, February 19, 2010 2:12 PM Reply | Quote Answers 0 Sign in to vote Give a try to the link belowhttp://www.sql-articles.com/articles/dba/linked-server-part-1Vidhya Sagar. Mark as Answer if it helps! Marked as answer by TToby123456 Monday, February 22, 2010 12:17 PM Friday, February 19, 2010 7:24 PM Reply | Quote Moderator All replies 0 Sign in to vote Can you right click the linked server in SSMS and script it out and post the code back here. That may help identify the problem.Also, you should select the top radio for "SQL Server". not OLE DB. No other configuration is needed for OLE DB if you are linking to SQL ServerTed Krueger Blog on lessthandot.com @onpnt on twitter Friday, February 19, 2010 2:25 PM Reply | Quote Moderator 0 Sign in to vote Give a try to the link belowhttp://www.sql-articles.com/articles/dba/linked-server-part-1Vidhya Sagar. Mark as Answer if it helps! Marked as answer by TToby123456 Monday, February 22, 2010 12:17 PM Friday, February 19, 2010 7:24 PM Reply | Quote Moderator Microsoft is conducting an online survey to under
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 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 https://social.msdn.microsoft.com/Forums/sqlserver/en-US/6ad63940-a5e8-4287-b486-c718c9fe759f/setup-linked-server-2-installed-instances-of-sql-on-the-same-server?forum=sqldatabaseengine you, helping each other. Join them; it only takes a minute: Sign up Having trouble adding a linked SQL server up vote 9 down vote favorite 1 I'm trying to pull in data from a remote SQL Server. I can access the remote server using SQL authentication; I haven't had any luck using the same credentials with http://stackoverflow.com/questions/841339/having-trouble-adding-a-linked-sql-server sp_addlinkedserver. I'm trying something like this: Exec sp_dropserver 'Remote', 'droplogins' go EXEC sp_addlinkedserver @server='Remote', @srvproduct='', @provider='SQLNCLI', @datasrc='0.0.0.0' EXEC sp_addlinkedsrvlogin @useself='FALSE', @rmtsrvname='Remote', @rmtuser='User', @rmtpassword='Secret' Select Top 10 * from Remote.DatabaseName.dbo.TableName Here's what I get: OLE DB provider "SQLNCLI" for linked server "Remote" returned message "Login timeout expired". OLE DB provider "SQLNCLI" for linked server "Remote" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". Msg 53, Level 16, State 1, Line 0 Named Pipes Provider: Could not open a connection to SQL Server [53]. Again, I can access the server directly (in SQL Management Studio) using these exact credentials, so it's not a problem with my network or credentials. Most of the examples I've seen online seem to involve Windows domain accounts, as opposed to SQL security logins. Does this not work with SQL authentication? sql-server linked-server share|improve this quest
= N'MYSERVERNAME', @provider=N'SQLNCLI', @datasrc=N'MYINSTANCENAME, @catalog=N'SOMENAME'I dropped the same http://aby-john.blogspot.com/2009/04/sql-server-2005-linked-server-scripting.html and tried to add it with the above script and it gave me the errorMsg 15429, Level 16, State 1, Procedure sp_addlinkedserver, http://dba.stackexchange.com/questions/1382/how-do-i-fix-a-login-timout-in-sql-server-2005-when-using-a-linked-server-and-a Line 42'(null)' is an invalid product name.Solution :- Add the product name also in the sp parameters.An sp_helptext on the sp showed this:-create linked server procedure sys.sp_addlinkedserver @server sysname, -- server name @srvproduct nvarchar(128) = NULL, -- product name (dflt to ss) @provider nvarchar(128) = NULL, -- oledb provider name @datasrc nvarchar(4000) = NULL, -- oledb datasource property @location nvarchar(4000) = NULL, -- oledb location property @provstr nvarchar(4000) = NULL, -- error 15429 sql oledb provider-string property @catalog sysname = NULL -- oledb catalog propertyasetc etc ...The Script Linked Server as Create To command somehow missed the @srvproduct parameter.So the modified sql statement will be EXEC master.dbo.sp_addlinkedserver @server=N'MYSERVERNAME', @srvproduct=N'MSSQLSERVER', @provider=N'SQLNCLI', @datasrc=N'MYINSTANCENAME, @catalog=N'SOMENAME' Posted by Aby at 1:01 PM 1 comment: coldsurfer said... thank u sir! May 30, 2013 at 2:14 PM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... Subscribe To Posts Atom Posts Comments Atom Comments Blog Archive ► 2015 (1) ► August (1) ► 2012 (1) ► January (1) ▼ 2009 (7) ► October (3) ► July (1) ▼ April (1) Sql Server 2005 Linked Server Scripting issue ► March (1) ► February (1) ► 2008 (3) ► December (3) About Me Aby View my complete profile
log in tour help Tour Start 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 more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top How do I fix a login timout in SQL Server 2005 when using a linked server and a stored procedure called from a SQL Agent Job? up vote 4 down vote favorite 1 I have a sql agent job running on ServerA. This job executes a stored procedure ServerA.DatabaseA.dbo.SPROC_A, inside this SPROC there is a query that selects data from ServerB.DatabaseB.SchemaB.TableB. There is a linked server set up from ServerA to ServerB with the security context set to: "Be made using the login's current security context". When the job executes the SPROC and the SPROC tries to select from the remote table the following error is thrown: Executed as user: domain\user. Named Pipes Provider: Could not open a connection to SQL Server [1450]. [SQLSTATE 42000] (Error 1450) OLE DB provider "SQLNCLI" for linked server "ServerB" returned message "Login timeout expired". [SQLSTATE 01000] (Error 7412) OLE DB provider "SQLNCLI" for linked server "ServerB" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". [SQLSTATE 01000] (Error 7412). The step failed. I have made sure that the remote server allows remote connections and that the [domain\user] login has appropriate access to the remote server and database. Does anybody have a resolution to this? It started out as a problem with trying to perform SQL authentication across the wire so we created the domain user and now I'm having this timeout issue. edit We now have named pipes enabled on the production servers and I am still getting an error. Executed as use