[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 559
  • Last Modified:

SQL 2005 Cluster node will not come online due to port 1433 conflict

We have a brand new node that we added to an existing cluster.  When we try to start the service, the error log shows:

Server TCP provider failed to listen on [x.x.x.x] <ipv4> 1433].  Tcp port is already in use.

The only difference I see on this box versus the other boxes is that under SQL Server Config, SQL Server 2005 Network Configuration, Protocols, TCP on the IP Addresses tab, at the bottom I see port 1433 for both TCP Dynamic Ports as well as TCP Port.  The other servers just have an entry in Dynamic.  I clear the TCP Port entry, try to restart, and it puts 1433 back in.  Same effect if I remove it in the registry, it keeps re-adding itself.  Any ideas?

Thanks,

Joe
0
netwrked
Asked:
netwrked
  • 4
  • 3
1 Solution
 
ralmadaCommented:
The default instance of SQL Server usually listens on port 1433. If you are configuring a multiple instance cluster, you must use a different port for each additional instance. Although SQL Server can set this port dynamically at startup, you might want to set each named instance to listen on a specific, unused port.
0
 
netwrkedAuthor Commented:
I changed the port number in the SQL Server Configuration to a new port, it still keeps changing it back to 1433.   Is there somewhere else I need to make the port changes?
0
 
netwrkedAuthor Commented:
BTW, I checked my other nodes, they all show they are all listening on 1433 according to their respective ERRORLOG files.
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
ralmadaCommented:
Have you restarted the server after changing the port?
Please take a look at this:
http://msdn.microsoft.com/en-us/library/ms177440(SQL.90).aspx 
0
 
netwrkedAuthor Commented:
That is the problem, when I try to start the server, I get the:

"Server TCP provider failed to listen on [x.x.x.x] <ipv4> 1433].  Tcp port is already in use" message in the ERRORLOG.

For the heck of it, I removed the 0 from all the TCP Dynamic Ports per the suggestion of the article you linked.  I then entered 1433 into each IPn TCP Port.  When I tried to start the SQL Server, it changes all the TCP Dynamic Ports back to 0 and all the TCP Port to blank except for IPAll where both Dynamic and port say 1433!
0
 
netwrkedAuthor Commented:
That worked, many thanks for the assist!

Joe
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now