Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

Dismiss

[Microsoft][ODBC SQL Server Driver] Client Unable to establish connection

1,225 views

Skip to first unread message

Rekha Joshi

unread,

Jul 11, 2003, 6:14:11 PM7/11/03

I am trying to make an ODBC connection to a server from a
client.
Have a server A ( MSSQL 2000 sp3) running on MachineA
(WINDOWS 2000 SERVER SP3). On the same machine there is
another instance of SQl Server 2000 sp3 called A/A_MW.

The users is able to see the sql server A but not able to
see A/A_MW.
Whiel creating an ODBC connection the connection fails and
generates an error message

Connection Failed
SQL Server Error: 01000
SQLState:08001
[Microsoft][ODBC SQL Server Driver][Named Piper]
Connection Open (CreateFail())
Client Unable to establish connection
SQL Server Error: 00001
SQLState:08001
[Microsoft][ODBC SQL Server Driver] Client Unable to
establish connection

Can anybody help me figuring out what could be the cause
for the error.

Thanks in Advance,

Rekha

Peter Yang [MSFT]

unread,

Jul 14, 2003, 1:01:47 AM7/14/03

Dear Rekha,

Thanks for your posting. From your post I understand that you are not able
to make an ODBC connection to a named instance while you can connect
correctly to the default instance.

Before we go further on the issue, I would like to confirm the following
information with you:

1. Which method and tool did you use to connect to the SQL server named
instance? Any detail is helpful.

2. How did you configure ODBC DSN?

Firstly I suggest that you use Query Analyzer to check if you can connect ¡
°A/A_MW¡± instance.

If you are not able to connect ¡°A/A_MW¡± by using Query Analyzer, please
check the settings

1. On the Microsoft SQL Server 2000 server, start the SQL Server Network
Utility

2. Click the General tab, and then select the instance you want from the
Instances drop-down menu.

3. Make sure TCP/IP and named pipe are listed in ¡°Enabled protocols¡±.

If you are able to connect to the named instance by using Query Analyzer,
you may need to check your application for this specific issue.

Also, the issue can occur if the client computer does not have the SQL
Server 2000 client utilities and/or Microsoft Data Access Components (MDAC)
2.6 are unaware of named instancing and therefore are only able to connect
to the default instance.

I suggest that you install the SQL server 2000 client utilities and
Microsoft Data Access Components (MDAC) version 2.6, or later on your
client computer. You can refer to the following articles for more
information:

265808.KB.EN-US INF: How to Connect to an SQL Server 2000 Named Instance
with the
http://support.microsoft.com/default.aspx?scid=KB;EN-US;265808

270126 PRB: How to Manage Client Connectivity to Both SQL Server 2000
Virtual
http://support.microsoft.com/?id=270126

You can download MDAC 2.6 SP2 from the following link
http://www.microsoft.com/downloads

If anything is unclear or you have further questions on the issue, please
feel free to post back.

Thanks & Regards,

Peter Yang
MCSE2000, MCSA, MCDBA
Microsoft Partner Online Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

0 new messages