MS SQL Express 2014 service fails to start on Window Server 2008
I'm getting the following Event Viewer errors when trying to start the SQL Server (SQLEXPRESS) Service:
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
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.
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.
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.
Server TCP provider failed to listen on [ 'any' <ipv4> 49172]. Tcp port is already in use.
I've tried restarting the Server but get the same result.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
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.
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.
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.
Server TCP provider failed to listen on [ 'any' <ipv4> 49172]. Tcp port is already in use.
I've tried restarting the Server but get the same result.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Usually, server updates do not impact/affect sql. including .net updates.
Within SQL there are error logs.
another option, is to try to start the service directly in the command line wiithout it going into the background to see what might be going on.
Under what credentials does the sql server service run? local account/local network or a specific credentialed domain/local user?
depending on the answer if a specific user, check whether that account changed in terms of changes to what it can do. Presumably you are not getting login error, meaning the password on the service does not match the current account password.
Within SQL there are error logs.
another option, is to try to start the service directly in the command line wiithout it going into the background to see what might be going on.
Under what credentials does the sql server service run? local account/local network or a specific credentialed domain/local user?
depending on the answer if a specific user, check whether that account changed in terms of changes to what it can do. Presumably you are not getting login error, meaning the password on the service does not match the current account password.
If you gave multiple SQL servers installed... That might explain the issue.