SQL errors on boot in Application Event Log

[k8277]

My problem is when rebooting my SQL Server 2000 SP3 on W2k I will see errors in the Application Event log.

Here is what I am seeing:

Source = MSSQLSERVER
Event ID = 17055
Description = 19012: SuperSocket Info: Bind failed on TCP port 1433.

I do have a second box that is almost identical used for development where the problem is not happening and at the same point in the Application log on the dev box, I will receive a record of SQL Server listening on IP Address: Port 1433 and then binding on 127.0.0.1: 1433. I am not getting this on my production box. Everything is working fine, but I don't know if I am at risk for problems.

Any help would be appreciated.

 

[mrdenny]

What is happenind is one of two things.

1. You have a firewall installed on the SQL Server which is blocking port 1433.
2. Something else is using port 1433 while the machine is booting.

The reason that everything is still working is that everything is probably connecting through NBT instead of TCP. Which isn't really a problem, it's just a little less effecent.

If this is happening every single time you reboot the server then it's probably a filewall. If you stop and restart the service (without rebooting) and SQL is able to start listening on port 1433 then the problem is that something is using port 1433 on boot.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[k8277]

Thanks Denny,

I do not have a firewall installed, so it must be something grabbing port 1433 during boot up. Is there a tool to determine what could be doing this?

 

[mrdenny]

not really. Odds are by the time you can log in what ever is using the port has closed. Check google, I think that there are some apps that can map what port is being used to the app that's using it. You can probably get one, and schedule it to run when the machine starts up and mabey get a log that way.

Denny

--Anything is possible. All it takes is a little research. (Me)

 

[k8277]

I used a tool from Mircosoft's site (portqry) and it tells me that SQL Server is using 1433, so you are probably right in that it is able to get it back after I see the error message.

 

[mrdenny]

yeah, looks like it.

Denny

--Anything is possible. All it takes is a little research. (Me)