April 13, 2010 at 1:52 pm
Trying to get a linked server running from SQL 2008 to SQL 7 SP4 and running into issues with authentication...
I have it currently linked to sa = sa for security...but that is not working...
I had thought about trying to set up an alias...but was not sure if that would help or not...
Any help is appreciated.
Error message is as follows:
===================================
The test connection to the linked server failed.
===================================
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Program Location:
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQuery(String cmd)
at Microsoft.SqlServer.Management.Smo.LinkedServer.TestConnection()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LinkedServerConnectionTest.Invoke()
===================================
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 "DS06601" returned message "Client unable to establish connection due to prelogin failure".
OLE DB provider "SQLNCLI10" for linked server "DS06601" returned message "Client unable to establish connection". (.Net SqlClient Data Provider)
------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.00.2531&EvtSrc=MSSQLServer&EvtID=10054&LinkId=20476
------------------------------
Server Name: ds098017
Error Number: 10054
Severity: 16
State: 1
------------------------------
Program Location:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
April 14, 2010 at 1:28 am
This was removed by the editor as SPAM
April 14, 2010 at 9:23 am
Hi,
Thanks for the verification...I hadn't explicitly looked for confirmation on the above...once I got the error and after googling I had seen some 'methods' that were reported to have worked (using a DSN from the 2008 server with older MDAC)...
I don't think I am going to head down that road and have another option...
Thanks for the info,
Lee
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply