February 3, 2004 at 2:59 am
On one of our production servers the TCP listener for SQL Server failed to start when the MSSQL Server service was restarted. It would not start until the machine was rebooted. This has never been a problem before and the only thing that has changed is the Administrator password for our NT domain. MS Sql server runs under its own domain user which is itself a member of domain admins.
Any thoughts ?
Nigel Moore
======================
February 3, 2004 at 4:09 am
Was it the supersocket error recorded in the sql error log?
I've seen it before. Sometime correctable (by a reboot) and sometimes not... when it occured on a cluster.
Cheers,
- Mark
February 3, 2004 at 4:25 am
ListenOn connection '1433' is already in use..
was recorded in log.
Nigel Moore
======================
February 3, 2004 at 6:33 am
What this means was something else was using port 1433. Generally, if you can figure out what program is, if you get it to release 1433, you can simply stop and restart SQL Server without resorting to restarting the whole box.
K. Brian Kelley
@kbriankelley
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply