Take the 2-minute tour ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sorry to raise if this has been asked before. The SQL Server service is defined as manual, whenever I start it I get (event viewer):

> Server TCP provider failed to listen on [ 'any' 1433]. Tcp port is already in use.

The SQL Server (MSSQLSERVER) service terminated with service-specific error Only one usage of each socket address (protocol/network address/port) is normally permitted.. <<

Odd thing both my ethernet and WiFi adapters have ipv6 disabled and it has ran fine for ages.

ENV: W2008-R2, SQL Server 2012 BI SP1; all MSFT patches applied.

TIA & Knd Regds

Arturo Medina

#

share|improve this question
add comment

2 Answers 2

Find out what process is already using TCP 1433. You can do this through the use of TCPView. That utility is a sysinternals tool that gives you the information you need. Just start it, pause the data view, and look at which process is using the local port of 1433 with the TCP protocol.

Note: You'll probably want to uncheck "Resolve Addresses" in the Options menu item so that you will be able to see the default instance port number.

Then once you know the process that is already using that port, you can take the appropriate action or reach out to the appropriate personnel that may know more about the process, why it's there, etc.

Or you could always change the port in which your SQL Server instance is listening on, but I'd personally be extremely curious as to which process is already using that port.

share|improve this answer
    
To be honest, I can't say for sure why that process is listening on TCP 1433, or anything further. I'd take that information you have (you should remove that comment you just posted, and ensure that sensitive information is removed) and post a follow-up question on serverfault.com asking about the process and why it's using TCP 1433. –  Thomas Stringer Mar 27 at 19:07
1  
Many thanks for your time Thomas, I'll try that. –  user36285 Mar 27 at 19:12
    
Of course, always glad to help! –  Thomas Stringer Mar 27 at 19:13
    
Thomas, thanks again for taking the time. In the end the issue solved itself! Quite odd. –  user36285 Mar 31 at 23:47
    
@user36285 Ha! I tend to be doubtful of things just fixing themselves :-) But keep an eye on it! And of course, always glad to help! –  Thomas Stringer Apr 1 at 0:03
add comment

To determine what executable is listening on a port, use netstat -a -n -b and look for 1433.

For example:

C:\Users\administrator.ADVENTUREWORKS>netstat -a -n -b

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:1433           0.0.0.0:0              LISTENING
 [sqlservr.exe]

If it is sqlservr.exe that is listening then the next step is to use SQL Configuration Manager to see what instances of SQL Server are installed. One of them is using tcp1433.

share|improve this answer
    
Many thx, I used your example, to verify that everything runs fine. –  user36285 Mar 31 at 23:55
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.