SuperSocket Info: Bind failed on TCP port 1433.

Print-vriendelijke versieStuur deze pagina doorPDF version

When starting Microsoft's SQL server on an SBS 2003 server, the following error occurs:

Event Type: Error
Event Category: (2)
Event ID: 17055
Date: 2007/07/17
Time: 22:23:14
User: N/A
Computer: SERVER
19012 :
SuperSocket Info: Bind failed on TCP port 1433.

It seems that TCP port 1433 is used by another service or application.
Further investigation shows that the SQL$SBSMONITORING instance is the one that is listening to port 1433.

That instance shouldn't be listening to 1433 at all.
If you pull up the SQL Server Network Utility, the local SQL server instance should have the Named Pipes and TCP/IP in the enabled protocols.
The Monitoring, MSFW (ISA) and Sharepoint instance should have nothing listed in the enabled protocols by default.
Can you check this and remove it if they are enabled?

If enabled, you should disable them and restart all SQL Server instances. It might solve your problem!

If not, and eventid 19011 occurs, check this:

Description: "ConnectionListen(Shared-Memory (LPC)): Error 5" -

Review the REG_MULTI_SZ key under:
"HKLM\Software\Microsoft\Microsoft SQL server\{instancename}\MSSQLServer\SuperSocketNetLib\ProtocolList".
It should contain entries for "tcp" and "np" and maybe more if you have more subkeys under "SuperSocketNetLib".

Also check the two REG_SZ keys under "HKLM\Software\Microsoft\Microsoft SQL Server\{instancename}\MSSQLServer\SuperSocketNetLib\Tcp\TcpDynamicPorts" and
"HKLM\Software\Microsoft\Microsoft SQL Server\{instancename}\MSSQLServer\SuperSocketNetLib\Tcp\TcpPort".

In some cases, both values were empty. Changing both values to "2624" (as seen on another working server) and the MSSQL MSDE2000 engine started without the above error.

Post new comment

The content of this field is kept private and will not be shown publicly.
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Enter the characters shown in the image.