July 24, 2007 at 3:32 am
Hi,
I am trying to create linked server from sql server 2005 to sql server 2000 .
both the servers are in different domains. I am getting the following error.
OLE DB provider "SQLNCLI" for linked server "<server name>" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "<servername>" 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 1326, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [1326].
Any advice.
Regards
Bharat
July 24, 2007 at 5:32 am
Have you set remote connections to on. Is named pipes protocol enabled in your server. By default named pipes is disabled in sql server 2005.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 24, 2007 at 5:48 am
Hi sugesh,
remoteconnection is on.Where can i see the namedpipes enabled\disabled.
Thanks
July 24, 2007 at 5:51 am
sugesh,
named pipes is also enabled.
Regards
Bharat
July 24, 2007 at 6:33 am
Check for firewall and login timeout properties. Are you able to login successfully to the target linked server machine using SSMS from the clinet machine.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
July 24, 2007 at 11:17 pm
Hi sugesh,
I have done the following things...
http://support.microsoft.com/kb/914277
Now also I am getting the following error...
OLE DB provider "SQLNCLI" for linked server "<servername>" returned message "Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "<servername>" 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 1326, Level 16, State 1, Line 0
Named Pipes Provider: Could not open a connection to SQL Server [1326].
If u will get the free time look into this issue and do the needful.
Regards
Bharat
July 25, 2007 at 12:03 am
Check the clinet connections. They too should have named pipes protocol enabled. As mentioned earlier named pipes is disabled by default in sql server installation.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply