sql server connect: I have an instance of SQL Server that gets recycled every night (SQL 2000
sp4, windows 2000 sp4). Every couple of weeks or so users can't connect in
the morning, and I see in the SQL log the error message 'SuperSocket Info:
Bind failed on TCP port 1433.' When I restart the SQL service, it seems to
clear it up.

I've done some research on this, and it looks like it can be caused by
something else using port 1433. Does anyone know if there is a way to
monitor this port to see if something else is using it?

If your referring to a one off check of what is using a port you can use
tcpview from Microsoft. If your referring to a monitoring system, Id suspect
the easiest way would be to put something together in .net that is run
to start the sql service. It could simply check the port and if its free
then start sql otherwise kill the offending process and start sql server.

-Allen Kinsel

[quoted text, click to view]



Posted by NewsLook (Trial Licence) from http://www.ghytred.com/NewsLook/about.aspx

Check if you have any 3r party backup software running or any anti-virus
running?
It is possible that if any 3rd part applications are accessing SQL Server
files and if your SQL Server service is not running then there's a
possibility that it might fail to bind TCP/IP.

Also take a look at: http://support.microsoft.com/kb/307197

Thank you,
Saleem Hakani
HTTP://WWW.SQLCOMMUNITY.COM (World Wide Microsoft SQL Server Community)
SQLTips, SQL Forums, SQL Blogs, SQL RADIO, SQL Events, SQL Scripts, SQL
Articles, SQL Clinic and a lot of SQL fun.
Register (Free):
http://www.sqlcommunity.com/RegistrationLoginPage/tabid/68/Default.aspx?returnurl=%2fHome%2ftabid%2f36%2fDefault.aspx


[quoted text, click to view]