Re: Cannot bind to port 1433
- From: Allen Kinsel <allen.kinsel@xxxxxxxxxxxxxxxx>
- Date: Wed, 10 Oct 2007 18:04:19 GMT
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
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?
Posted by NewsLook (Trial Licence) from http://www.ghytred.com/NewsLook/about.aspx
.
- Prev by Date: Re: Is there a reliable way to do this?
- Next by Date: Re: Error: 18456, Severity: 14, State: 16.
- Previous by thread: Is there a reliable way to do this?
- Next by thread: Re: Error: 18456, Severity: 14, State: 16.
- Index(es):
Relevant Pages
|
Loading