September 5, 2003 at 9:37 am
I am not much of an IP guru. I booted my SQL 2000 cluster and my instance, in the SQ log, is reporting: SuperSocket Info: Bind failed on TCP port 1433. From the doco I have read, it seems to be some sort IP conflict or something like that. I can ping the IP address and map a drive using that ip address. Any ideas?
September 5, 2003 at 9:41 am
From a command prompt, you can run a netstat -an and see if 1433 is still being used. It's not an IP conflict so much as a port conflict. Something else on the physical server was using TCP port 1433 at that time. If nothing is currently using 1433, you should be able to bring the SQL Server offline and back online through Cluster Administrator and it should bind to 1433 properly.
K. Brian Kelley
http://www.truthsolutions.com/
Author: Start to Finish Guide to SQL Server Performance Monitoring
K. Brian Kelley
@kbriankelley
September 5, 2003 at 5:01 pm
Sometimes other programs grab port 1433 before sql server starts.
If after running Brian's command you find port 1433 is used you will need to find the application, and make it dependant on sql server starting to avoid this in the future.
Steven
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply