/*******************Error******************************/
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems
/*************************************************/
spid15s Error: 26023, Severity: 16, State: 1.
spid15s Server TCP provider failed to listen on [ 'any' <ipv6> 1433]. Tcp port is already in use.
spid15s Error: 17182, Severity: 16, State: 1.
spid15s TDSSNIClient initialization failed with error 0x2740, status code 0xa. Reason: Unable to initialize the TCP/IP listener. Only one usage of each socket address (protocol/network address/port) is normally permitted.
spid15s Error: 17182, Severity: 16, State: 1.
spid15s TDSSNIClient initialization failed with error 0x2740, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Only one usage of each socket address (protocol/network address/port) is normally permitted.
spid15s Error: 17826, Severity: 18, State: 3.
spid15s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
spid15s Error: 17120, Severity: 16, State: 1.
spid15s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
/*************************************************/
Issue: Port dedicated to SQL server is being used by some other service.
Solution: You can always download TCP view and identify application which is using SQL port
Download tool: TCPView and install “https://docs.microsoft.com/en-us/sysinternals/downloads/tcpview”
This will show you which application is using SQL port. In case you are not able to kill that connection, restarting the server will fix the issue.
No comments:
Post a Comment