servers "Client unable to establish connection"

We have several linked SQL servers running both SQL 7 (sp4) and SQL 2000 (sp3). Recently, when we run the following command from SQL 7 query analyzer to a SQL 2000 database, select * from remoteserver.database.dbo.tablename, we get this message:

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

The databases are linked with specific remote login and password. The same command works the opposite direction, in other words from the SQL 2000 database to SQL 7 database. This was working last week but all of a sudden stopped. Of course, no one admits to changing anything on either of the servers. The SQL 2000 is on Windows 2003 server.

Thanks.

LccTom,

It is possible that some of the recent w2k3 patches disabled the file sharing and remote network connectivity on your w2k3 machine. Can you try if you can remote access to the w2k3 machine, such as file sharing? If you can't, you need to enable the file sharing because the namepipe provider[DBNMPNTW] depends on it.

Also, if you want TCP connection, you need to make firewall exception for the SQL tcp listening port, default to 1433 for a default instance.

|||We have no OS service packs installed but for some reason, it started working again Wednesday morning. Thanks for the reply and I'll make sure to look at the file sharing if it happens again. I reported it to my network people also.

server?

I have multiple servers. From one production server (A), I can establish Li
nked Servers to other servers. However, I am not able to establish a Linked
Server to one specific server (B). The servers are on different domains. H
owever, I am able to link f
rom A to other servers on the same Domain as B.
-- From the production server A I can open Query Analyzer directly to server
B -- so I do believe that the Client Network Utility is correct
-- I have recreated the Linked Server/security panel for the login I"m using
, and believe the login/password is set up correctly.
-- Both server A and server B are clustered, running Win2003 and SQL2000 wit
h patches.
Here is the error message I receive when I try to do a select * from B.maste
r.dbo.sysobjects (or any other db/talble) when logged in to A in Query Analy
zer:
Server: Msg 7303, Level 16, State 2, Line 1
Could not initialize data source object of OLE DB provider 'MediaCatalogDB.1
'.
OLE DB error trace [OLE/DB Provider 'MediaCatalogDB.1' IDBInitialize::In
itialize returned 0x80030003].
BOL indicates this is due to two things: the server is set up with wrong dat
a in linked server or the login is incorrect.
Any other suggestions? Thanks much.
LindaAfter posting the message, I recreated the linked server in question again.
This time all is well.
So sorry for the post!|||Hi Linda:
How did you fix this? I am having the same problem. I am trying to link to
sql server in a different domain. I am getting the error message that sql
server does not exist. Thanks

server Trouble to Oracle

I'm currently trying to establish a linked server to an Oracle
database.

Setup:
Connecting to 8x version of Oracle
Using 9i client tools (Net Manager)
SQL-Server 2000
Windows 2000

I installed the Oracle 9i client tools, and set up a Service for the
Oracle connection. Testing from the 9i client produces a successfull
connection.

I then opened SQL-Server and created a new Linked Server with the
following setup:

Name - PYR_Link
Provider - Microsoft OLE DB Provider for Oracle
Product Name - PYR
Data Source - PYR (9i Service Name)
Provider string - MSDAORA

I get the unspecific 7399 error that OLE DB provider MSDAORA reported
an error, trace 'Initialize returned 0x80004005'

I've searched through the archives, checked all of the relevant
Microsoft articles I could find, and still have no idea what is wrong.
SQL-Server reports that the provider is registered in the system, but I
can't figure out what I'm missing.

Help or a guide for troubleshooting would be much appreciated.

TimAn update - When I run sp_catalog in Query Analyzer, the error message
is more detailed. It says the provider could nor resolve the service
name. Still strange, considering the Net Manager client connects fine.|||Hi Tim, this error could occur when the oracle domain is not recognised.

Try to find out the Oracle domain (e.g. 'world') and change your linked
server to connect to that domain, like product name PYR.world and data
source PYR.world.

Good luck!
Maurits

<tim.pascoe@.cciw.ca> schreef in bericht
news:1123770210.158827.38320@.g47g2000cwa.googlegro ups.com...
> I'm currently trying to establish a linked server to an Oracle
> database.
> Setup:
> Connecting to 8x version of Oracle
> Using 9i client tools (Net Manager)
> SQL-Server 2000
> Windows 2000
> I installed the Oracle 9i client tools, and set up a Service for the
> Oracle connection. Testing from the 9i client produces a successfull
> connection.
> I then opened SQL-Server and created a new Linked Server with the
> following setup:
> Name - PYR_Link
> Provider - Microsoft OLE DB Provider for Oracle
> Product Name - PYR
> Data Source - PYR (9i Service Name)
> Provider string - MSDAORA
> I get the unspecific 7399 error that OLE DB provider MSDAORA reported
> an error, trace 'Initialize returned 0x80004005'
> I've searched through the archives, checked all of the relevant
> Microsoft articles I could find, and still have no idea what is wrong.
> SQL-Server reports that the provider is registered in the system, but I
> can't figure out what I'm missing.
> Help or a guide for troubleshooting would be much appreciated.
> Tim