Is there anyway to get this to work?

This is what I get:
OLE DB provider "SQLNCLI10" for linked server "P100S005" returned
message "Client unable to establish connection due to prelogin
failure".
Msg 10054, Level 16, State 1, Line 0
TCP Provider: An existing connection was forcibly closed by the remote
host.
OLE DB provider "SQLNCLI10" for linked server "P100S005" returned
message "Client unable to establish connection".
Msg 26, Level 16, State 1, Line 0
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.

I understand that it's probably not supported, but we have an
application usíng SQL7 that we can't move right now.

The setup is
SQL 2008 X64 on Windows 2008 R2 and
SQL 7 on Windows NT4

If I try to connect from the same SQL2K8 to the same SQL7 using Import
wizard I get it working when I use "SQL Native Client" (SQLNCLI) as
source provider but not when I use "SQL Server Native Client 10.0"
(SQLNCLI10) as source provider. It seems like it's SQLNCLI10 that is
the problem.

When I try to link the servers I can't find any way to use SQLNCLI
instead of SQLNCLI10 even if it say's SQLNCLI in sys.servers

/Peter

Hey Peter...

I have had the same problem but with SQL Server 2000 32bit from SQL Server
2008 64bit. The solution that I implemented to fix my linked server problem
was to create the sp_tables_info_rowset_64 stored procedure in the master
database on the 32bit server. This procedure is needed because it is called
by 64-bit servers when running remote queries to 32bit SQL Servers.

There is no issues with adding the stored procedure and running via the
linked server call. Try it out and let us know if it works or if you
experience a different error message.

Squirrel
http://www.lockergnome.com/sqlsquirrel/


"Peter Lindberg" wrote:

Squirrel, thank you for the answer. I've had the same issue with SQL
2000 and the solution for that is the same as you suggest. But it
doesn't work for SQL 7.

I can link to this SQL 7 from a server running X64 SQL2K3 SP2 and
SQL2K5 SP3.

Anyone, more suggestions!

Could it be possible to link it and get it to use SQLNCLI instead of
SQLNCLI10?

/Peter



On Mon, 22 Feb 2010 20:27:01 -0800, SQLSQUIRREL
<SQLSQUIRREL (AT) discussions (DOT) microsoft.com> wrotc:

Hi plTAK, did you find an answer for this problem?
I'm in the exactly same problem... but with 2008 R2 against 7.0

I apreciate any comment

Thanks