February 3, 2011 at 8:18 am
I had setup a linked server to a SS7.0 instance from a SS2005 instance and all worked fine.
I decided to move the application to a new machine that is running SS2008 R2 and when I use the exact same setup, it tells me:
TITLE: Microsoft SQL Server Management Studio
------------------------------
The linked server has been updated but failed a connection test. Do you want to edit the linked server properties?
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
TCP Provider: An existing connection was forcibly closed by the remote host.
Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server.
OLE DB provider "SQLNCLI10" for linked server "SS7.0-Machine" returned message "Client unable to establish connection due to prelogin failure".
OLE DB provider "SQLNCLI10" for linked server "SS7.0-Machine" returned message "Client unable to establish connection". (Microsoft SQL Server, Error: 10054)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=10054&LinkId=20476
------------------------------
BUTTONS:
&Yes
&No
------------------------------
After seeing this, I thought perhaps there was a problem with the firewall so I tried to just ping the SS7 machine... no problem. Then I created a report in BI Studio with a direct connection to the SS7 machine - no problem. The data came across just fine. So, I think I have ruled out a problem with network security.
So, what do I do next? Can anyone help with this one?
February 7, 2011 at 10:36 am
jpence (2/3/2011)
I had setup a linked server to a SS7.0 instance from a SS2005 instance and all worked fine.I decided to move the application to a new machine that is running SS2008 R2 and when I use the exact same setup, it tells me:
Client unable to establish connection because an error was encountered during handshakes before login. Common causes include client attempting to connect to an unsupported version of SQL Server, server too busy to accept new connections or a resource limitation (memory or maximum allowed connections) on the server.
The bolded portion jumps out at me. Double-check BOL to verify that Linked Server Connections to SS7 from SSMS are actually supported.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply