Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 319578 - Last Review: April 6, 2006 - Revision: 9.2
Error message when you change the IP address on a SQL Server failover cluster node: "Bind failed"
This article was previously published under Q319578
SYMPTOMS
Attempts to bring a SQL Server 2000 or SQL Server 2005 virtual instance online
on a cluster may fail, or the SQL Server virtual instance on the cluster
may come online successfully, but the SQL Server virtual instance on the
cluster will only listen on Named Pipes. Client connections made over Named
Pipes will succeed, but client connections over TCP/IP fail.
The SQL
Server error log reports the following error message if the Virtual SQL Server
does not successfully bind to port 1433:
SuperSocket Info: Bind failed on TCP port 1433
If the Virtual SQL
Server is set to bind to 0 or a dynamic port, the Virtual SQL Server still
unsuccessfully binds and an error message similar to the following occurs:
SuperSocket Info: Bind failed on TCP port 0
This article discusses one possible cause of this error message. The
information in this article helps only if you are experiencing this exact same
scenario. For other possible causes of the error message, see the following
articles in the Microsoft Knowledge Base:
293107Â
(http://kbalertz.com/Feedback.aspx?kbNumber=293107/EN-US/
)
PRB: TCP\IP Port in Use by Another Application
312935Â
(http://kbalertz.com/Feedback.aspx?kbNumber=312935/
)
FIX: SQL Server fails to bind TCP/IP port at startup
308091Â
(http://kbalertz.com/Feedback.aspx?kbNumber=308091/EN-US/
)
BUG: Hide Server Option Cannot Be Used on Multiple Instances of SQL Server 2000
307197Â
(http://kbalertz.com/Feedback.aspx?kbNumber=307197/EN-US/
)
PRB: SQL Virtual Cluster Server Fails to Bind to the Port on Which it is Listening
CAUSE
Changing the Virtual SQL Server IP address with the Cluster
Administrator tool. For a default instance of virtual SQL Server, the following
registry value points to a previous IP address:
HKLM\Software\Microsoft\MSSQLServer\ClusterFor a named instance of virtual SQL Server, the
following registry value points to a previous IP address:
HKLM\Software\Microsoft\Microsoft SQL Server\Instance Name\Cluster\ClusterIpAddr
RESOLUTION
To resolve the problem, follow the steps in Microsoft
Knowledge Base article Q244980 for the correct way to change the Virtual SQL
Server IP address. When you get to step 7 in the "More Information" section of
the article, select
Remove and replace an existing IP Address:
244980Â
(http://kbalertz.com/Feedback.aspx?kbNumber=244980/
)
HOW TO: Change the Network IP Addresses of SQL Server Virtual Servers
If you are using SQL Server 2005, follow the steps described in the "How to: Change the IP Address of a SQL Server 2005 Failover Cluster" topic in SQL Server Books Online to resolve the problem.
APPLIES TO
- Microsoft SQL Server 2000 Standard Edition
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
| kbsql2005cluster kbprb KB319578 |
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please