May 7, 2008 at 11:07 am
I want to do Linked one of 2000 server from SQL 2005.
All the server are in same domain I tried connecting through SQL authentication I am using same account with sysadmin rights I am getting error 53.
When I tried to Link different server it works fine. Does it requires any firewall setting?
May 7, 2008 at 11:40 am
Are you able to connect to Sql Server 2005 remotely i.e have you enabled remote connections please confirm..
[font="Verdana"]- Deepak[/font]
May 7, 2008 at 12:08 pm
Yes it is.
May 7, 2008 at 2:12 pm
I am getting this error below: I am trying to connect to SQL 2000 server
OLE DB provider "SQLNCLI" for linked server "PROD_CD" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "PROD_CD" 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].
September 16, 2008 at 12:15 pm
I am getting the same error. Did you ever find a answer to this?
September 16, 2008 at 12:54 pm
have u enabled named pipes??..
September 16, 2008 at 2:40 pm
If your linked server is going from 2005 (x64) to 2000 (x86), you need to reapply instcat.sql on your SQL2000 server. This is a file included in the SQL2000 SP4 install.
I haven't had this problem in awhile ... I don't remember if this only applies for x64 to x86 or not.
September 17, 2008 at 9:03 am
See if this link helps you at all:
http://www.sqlservercentral.com/Forums/Topic553730-146-1.aspx#bm553792
MCITP, Database Administrator
A hodgepodge of Information Technology and Life
LinkedIn Profile
My Twitter
November 6, 2008 at 10:03 am
Hi,
I have the same problem. I have 6 VM servers that are supposed to have the same setup- SQL 2005 (64 bit) on Windows 2003. I am trying to create Linked server from 3 servers to the other three using the network Alias (TCP/IP with Port 1433) on each server. It worked on 2 of them. Only one server give me the same error message as yours. I checked both the source and target servers. They both allow Remote Connection using TCP/IP only. I don't know why the error message has "Named Pipes"
And if I create the Linked server with the server name directly without using the network Alias, it works fine. But I am trying to use the same Alias name (for Linked server) on each source servers pointing the different target servers for easy deployment of the user code.
Can we trace or get the named pipes out the picture here. I do not intend to use the named pipe any way. And I think I set up the SQL Network configuration right (the same with the others). Why does this one act differently?
Any idea where I should look?
Thanks!
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply