Sql Server will not start with TCP enabled

Hello, My SQL server restarted last night after some windows updates and now my sql instance will not start. I thought it may be the updates so i uninstalled them to no avail. After a few hours I have found that if i use named pipes only it startes fine. Once TCP/IP is enabled it bombs out again. Again help would be fantastic.
matthenkelAsked:
Who is Participating?
 
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
>> Server TCP provider failed to listen on [ 'any' <ipv4> 1433]. Tcp port is already in use.

As I mentioned earlier in my comment, your TCP IP port 1433 is already in use..( Hope you have one another instance of SQL Server in your machine)
Change it to 1435 and try starting SQL Server service which might help..

>> Any other ways to check for something grabbing that port

Try restarting your Server ( machine) once and try checking whether port 1433 is in use by some other application or another instance of sql server..
0
 
Raja Jegan RSQL Server DBA & Architect, EE Solution GuideCommented:
Kindly check whether remote connections are enabled properly as per:

http://support.microsoft.com/kb/914277

Also check for your TCP/IP configurations once and if you receive errors again, then post the exact error encountered so that it can be fixed..
Also make sure that the assigned TCP port is not used by other applications..
0
 
kenwagersCommented:
Does it have a TCPI/IP address assigned?  i've seen this where the interface did not have an IP number assigned, and SQL Server wouldn't start.

Check by typing 'IPCONFIG' at the command prompt.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
matthenkelAuthor Commented:
I have remote connections enabled but cannot start SQL with TCP/IP enabled.  the errors are as follows

Application log

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

TDSSNIClient initialization failed with error 0x2740, status code 0xa.

Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.

SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

System Log

The SQL Server (VISTASQL05) service terminated with service-specific error 10048 (0x2740).

When I run a net stat it shows 1433 as listening

0
 
mitleirCommented:
You need to find out what is running on that port.  Try running a netstat -ab to see if you can find the executable associated on that port.

Alternatively, you could change the port that is configured if you need to start up SQL immediately in the SQL Network configuration.
0
 
matthenkelAuthor Commented:
Running a netstat doesnt show anything running on 1433 but when i change the port to 1434 it opens with no issues so your right, its defiently a port issue. Any other ways to check for something grabbing that port
0
 
mbarsheshat01Commented:
try netstat -ab | more
Also to verify that 1433 is taken you can use:
telnet localhost 1433  (Use ^] and q to disconnect).
It is most likely that you have more than one instance of SQL running
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.