Home Dashboard Directory Help
Search

Connection failure - Server doesn't support requested protocol by venkn


Status: 

Closed
 as Fixed Help for as Fixed


1
0
Sign in
to vote
Type: Bug
ID: 495024
Opened: 10/1/2009 8:17:09 PM
Access Restriction: Public
1
Workaround(s)
view
1
User(s) can reproduce this bug

Description

-- While connecting using the Named pipes - it failed with the below error:

TITLE: Connect to Server
------------------------------

Cannot connect to np:venk2k8\katmai.

------------------------------
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

-- Checked the SQL Server Network Configuration for this instance
-- Could find Named Pipes disabled.
-- It gives a message that the "Server doesn't support requested protocol"
-- It can very well give a valid message.
-- Now checked the HelpLink -> it pointed me to the
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1


-- The important thing here is -> we should provide more meaningful message to the end user.
-- This should atleast let the end user suggest to check if the protocol is enabled.
Details
Sign in to post a comment.
Posted by Microsoft on 12/7/2009 at 2:10 PM
Now posted for SQL Server 2008, at http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL%20Server&ProdVer=10.0&EvtID=-1&EvtSrc=MSSQLServer&LCID=1033
Posted by Microsoft on 11/9/2009 at 9:40 AM
Added The TCP, or named pipes protocols are not enabled.
And added in part: Use the SQL Server Surface Area Configuration tool to enable SQL Server to accept remote connections over the TCP or named pipes protocols... As we discussed in e-mail.
Closing as fixed.
Posted by venkn on 11/6/2009 at 5:53 AM
Hi Rick,

Thanks for your response.

We are getting the same error message in SQL 2008 as well.

Let me explain the scenario..,

1.    Connecting to SQL Server in the following way: np:VENK2K8\KATMAI
a.    It fails with the below error message:
TITLE: Connect to Server
------------------------------
Cannot connect to np:VENK2K8\KATMAI.
------------------------------
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 28 - Server doesn't support requested protocol) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
------------------------------
BUTTONS:

OK
------------------------------
Comment:
It gives a messages as “Server doesn’t support requested protocol”. Which is a not a clear message. Are we not supporting Named Pipes??

b.    It also points to a link For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

Comment:
This link gives possible causes of this error message as below:
Explanation
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
The firewall on the server has refused the connection.
A specified SQL Server instance name is not valid.
The SQL Server Browser service (sqlbrowser) is not started.

User Action
To resolve this error, try one of the following actions:
Make sure that you have configured the firewall on the server instance of SQL Server to open the SQL Server Browser port.
Make sure that the SQL Server Browser service is started on the server.
Check the spelling of the SQL Server instance name that is specified in the connection string.
Use the SQL Server Surface Area Configuration tool to enable SQL Server to accept remote connections. For more information about the SQL Server Surface Area Configuration Tool, see Surface Area Configuration for Services and Connections.

So, the recommendations are:
1.    We give a clear message and not “Server doesn’t support requested protocol”
2.    In the Explanation section, add a point which talks to check if the protocol is enabled.

Hope this helps. If you need any further information, please do let me know.

I appreciate if you can make these changes in SQL 2008, as it will bring clarity in the error message we provide to customers.

Regards,
Venkat.
Posted by Microsoft on 10/16/2009 at 8:44 AM
Your comment has been forwarded to me (Rick.Byham@microsoft.com) for action. I'm not entirely clear what you would like to see. That is, you have disabled Named Pipes and get a message that "The Server doesn't support requested protocol." It looks like this error is related to SQL Server 2005. At this time we don't expect to release more 2005 documentation. But perhaps you think this is unclear for SQL Server 2008 as well. Can you tell me a bit more about what you think I should do to address your comment. Thanks.
Sign in to post a workaround.
Posted by venkn on 10/1/2009 at 8:20 PM
1. Enable the Named Pipes protocol in "Configuration Manager -> SQL Network Configuration"
2. Try to connect to the instance -> force the connection to use Named Pipes. For ex: in the connection string:

np:venk2k8\yukon

The connection will succeed.