I'm trying to setup a linked server from SQL Server 2005 (64bit) SP2
to SQL Server 2000 (32bit) SP3. I use the same setup as works for
several other version/SP combinations, but get the error below. This
used to work, probably before SP2 was installed.
The linked server works from 32bit 2005 SP1 and SP2. I've looked at
some similar error reported through groups, but they either relate to
preSP3 on 2000 or to setup errors on the linked server, eg, the
security settings for the login.
This is hindering my migration of systems from my 32bit 2000
environment to the 64bit 2005.
=================================================
TITLE: Microsoft SQL Server Management Studio
------------------------------
"The linked server has been created but failed a connection test. Do
you want to keep the linked server?"
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
Named Pipes Provider: Could not open a connection to SQL Server [53].
OLE DB provider "SQLNCLI" for linked server "DWS" returned message
"Login timeout expired".
OLE DB provider "SQLNCLI" for linked server "DWS" 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.". (Microsoft SQL Server, Error: 53)
=======================
Any ideas?
steve - 30 Nov 2007 10:59 GMT
> I'm trying to setup a linked server from SQL Server 2005 (64bit) SP2
> to SQL Server 2000 (32bit) SP3. I use the same setup as works for
[quoted text clipped - 35 lines]
>
> Any ideas?
Sorry all. My mistake! I set the SQL Native Client Alias up under
32bit. Create the alias under the 64bit section, specify which user to
authenticate properly and the linked server works fine.