Very Computer

[DBNMPNTW]ConnectionOpen (CreateFile()).
[OLE/DB provider returned message: Client unable to
establish connection]

I've done this many times among SQL 7.0 servers.  I
recently configured a remote pair involving 7.0 & 2000 the
same way as I have among the 7.0's.  All have the same
domain, username, & pw.  A remote stored procedure call
worked when the SQL 2000 server called the SQL 7.0, but
not in the other direction.

An example of calling a SQL 7.0 database (on TEST) from
SQL 2000:

    INSERT INTO tbl_demographics

However, I also need to pull the id's in the other
direction, from the SQL 2000 server to an SQL 7.0 server,
so that data for only relevant people is transferred (back
to SQL 2000).  

An example of calling a SQL 2000 server (on ATLAS) from a
SQL 7.0 server is:

    INSERT INTO tbl_ids (person_id)

This error message above occurs when I used remote
procedure calls to remote servers.  But much the same
message occurs when I use linked servers, except for the
[DBNMPNTW] part.

I would appreciate any suggestions.

Also post your sp_addlinkedServer statement which you used
to connect them in the first place.

--
- Anith

--
- Anith

On the SQL 7.0 server, I ran this:

USE master
GO
EXEC sp_addlinkedserver
    'ATLAS',
    N'SQL Server'
GO

I then checked the master..sysservers table, and ATLAS,
the SQL 2000 server, was in it.  (It had also been there
from my linking through Enterprise Manager, but I deleted
it before running sp_addlinkedserver.)

Using Enterprise Manager for the SQL 7, I SELECT'ed a
table residing on the SQL 2000.  The error message is:

[OLE/DB provider returned message: Client unable to
establish connection]
[DBNMPNTW]ConnectionOpen (CreateFile()).

Login and pw are the same on both servers.

Then I tried suggestion 3, and got the same error message.

-- Jerry

Quote:>-----Original Message-----
>1. Do a sp_addlinkedServer
>2. Then check the master..syservers table to see if the
>   Server is being added. If so there should not be any
>   problem.
>3. Another option is use sp_serveroption 'Data Access' on
>   the Server to TRUE & try an OPENQUERY.

>--
>- Anith

>.