| Event Id | 19012 |
| Source | MSSQLServer |
| Description | SuperSocket Info: Bind failed on TCP port %1. |
| Event Information | According to Microsoft Cause: When a SQL Server instance starts, it tries to reserve a port for its TCP/IP sockets communications. If SQL Server is configured to use a static TCP port, and that port is unavailable at startup time, SQL Server starts but cannot accept TCP/IP connections. It can still accept Shared Memory, Named Pipes, or Multiprotocol connections if it is configured to do so. There are several reasons why the configured port may not be available. The most common causes are listed below: 1.Another application was using ports that SQL Server was configured to listen on when the SQL Server instance started. 2.You have multiple instances installed on the computer, and more than one instance is configured to be "hidden." When you "hide" a server, the port is always set to 2433. If you hide multiple instances for a computer, only the first instance to start can actually use port 2433; the rest will not be able to accept TCP connections, because the first instance of SQL Server is using the port. 3.If the instance of SQL Server 2000 is clustered and you have changed the IP address using an unsupported method, SQL Server may not be able to bind to the configured port. 4.If you are running a version of SQL Server 2000 prior to SP3 and are using maintenance plans or any other process launched from with the SQL Server process space, SQLMaint.exe (or other launched executable) could be taking control of the configured SQL Server port during a restart. This is a known issue. 5.If you are using port redirection software, the software could prevent SQL Server from binding to its configured port. Resolution: 1.In many cases, restarting the SQL Server instance will allow TCP/IP sockets connections to succeed. 2.As a temporary workaround, you can configure your clients to connect using any of the other protocols that this SQL Server instance is configured to listen on. 3.Ensure that you are not using any port redirection software. 4.You can set up a port scanner such as portqry to determine what applications are using which ports on your server. You may want to look for applications that use different ports over time as well as those that actually use the port you configured for SQL Server, as this will let you know which applications dynamically choose ports. For more information about this error, see Microsoft Knowledge Base article 293107. 5.You can consider switching to dynamic ports for your SQL Server named instances (this is not an option for default instances). This will allow SQL Server to switch to a different port if the most recently used port is not available at startup. Using dynamic ports can affect how you configure your client applications, firewalls, and Kerberos Service Principle Names (SPNs) so ensure your environment is prepared to handle this configuration. For more information about dynamic ports, see "Network Libraries" in Books Online and Microsoft Knowledge Base article 823938. 6.Upgrade to the latest SQL Server service pack or rollup. You must be on at least SQL Server 2000 SP3 to prevent a process started within the SQL Server process space from interfering with the binding during a restart. For more information about this scenario, see Microsoft Knowledge Base article 312935. 7.If a clustered SQL Server instance is reporting the bind failure, and you have ever changed the IP address, the IP address may not be completely updated. For more information about this scenario, see Microsoft Knowledge Base article 319578. 8.Avoid "hiding" multiple instances of SQL Server. For more information about why the Hide Server option cannot be used on multiple instances of SQL Server, see Microsoft Knowledge Base article 308091. 9.In rare cases, adding a registry key can help to avoid the bind failed error. For more information about the particular scenario, see Microsoft Knowledge Base article |
| Reference Links | Event Id:19012 of Source Id:MSSQLServer |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.