Event Type: Error Event Source: MSSQLSERVER Event Category: (2) Event ID: 17055 Date: 08/08/05 Time: 1:58:58 PM User: N/A Computer: GPS Description: 19012 : SuperSocket Info: Bind failed on TCP port 1433. Data: 0000: 44 4a 00 00 10 00 00 00 DJ...... 0008: 04 00 00 00 47 00 50 00 ....G.P. 0010: 53 00 00 00 00 00 00 00 S.......What is really causing this? How can this be fixed?
Other potential causes of the bind failed message include:
- 319578 PRB: Error Message:"Bind Failed" Occurs After IP Address Changes on a Cluster
- 307197 PRB: TCPIP Port in Use by Another Application
- 293107 PRB: TCPIP Port in Use by Another Application
Do you have comments on this Ask the Expert Q&A? Let us know.
Related Q&A from Kevin Kline, Director of SQL Server Solutions, Quest Software
Monitoring and Administration expert Kevin Kline discusses the obstacles of database administration when a publisher resides on a different domain.continue reading
A common SQL Mail error is addressed by monitoring and administration expert Kevin Kline.continue reading
Monitoring and Administration expert Kevin Kline discusses the installation of SQL Server client tools on Windows XP Pro.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.