December 2, 2008 at 4:42 am
Hi,
I am getting the following error while accessing data from SQL Server 2000 from SQL Server 2005.
OLE DB provider "SQLNCLI" for linked server "hqserver" returned message "Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'netstats'.
I tried connecting from SQL Server Management Studio and I was able to connect using the netstats user id and execute queries against the database.
But if I execute the same query from using the linked server, I get the mentioned error.
Any help is much appreciated.
Cheers
December 2, 2008 at 5:18 am
Mohammed Imran Ali (12/2/2008)
Hi,I am getting the following error while accessing data from SQL Server 2000 from SQL Server 2005.
OLE DB provider "SQLNCLI" for linked server "hqserver" returned message "Communication link failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote host.
Msg 18456, Level 14, State 1, Line 0
Login failed for user 'netstats'.
I tried connecting from SQL Server Management Studio and I was able to connect using the netstats user id and execute queries against the database.
But if I execute the same query from using the linked server, I get the mentioned error.
Any help is much appreciated.
Cheers
I also received such message previoiusly, ther ei s some firewall installed at the host side
kshitij kumar
kshitij@krayknot.com
www.krayknot.com
December 4, 2008 at 10:00 am
Thank you for the reply Kshitij.
You are right. There are firewalls installed between both hosts and both were in different domains. The appropriate network configurations were taken care of and network connectivity is fine when I got this error message.
I was able to fix the issue by changing the Remote connections to use both tcp/ip and named pipes under SQL Server 2005 Surface area configuration > Surface area configuration for services and connections > Remote connections. [By default remote connections are disabled in SQL Server 2005]
After making this change, created a linked server [Choose SQL Server instead of other data sources]. Under security, choose the option "Be made using this security context" for Local server login to remote server login mappings.
The query works a charm 🙂 :smooooth:
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply