April 2, 2015 at 8:01 am
I have changed SQL Server from default port to another port number. All appears fine. If SQL Server is restarted it is all fine, however, when the server is restarted SQL Server fails to start. If you then log into the server and manually start the services they start just fine. So, it appears that something blocks the port or uses the port upon server startup for a few seconds. The AV folks say that they are not blocking ports and that it AV service actually starts 15 seconds after the SQL start failure.
So, the question becomes is how can I track down what is blocking or using that port?
This is Win2012/SQL2014 CU3
Server failed to listen on xxxxx::xxxxxxxxxx <ipv6> xxxxx. Error: 0x2741. To proceed, notify your system administrator.
Server failed to listen on fe80::5efe:10.255.196.25%18 <ipv6> 14001. Error: 0x2741. To proceed, notify your system administrator.
TDSSNIClient initialization failed with error 0x2741, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The requested address is not valid in its context.
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.
SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
April 2, 2015 at 8:59 am
what port number have you selected?
To see a list of processes listening on the server use the following
netstat -abno -p TCP
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
April 2, 2015 at 9:04 am
At the server teams direction we just changed the SQL Server services to AUTOMATIC (Delay) and restarted the server and it is all good. They are thinking that the port is simply not active when SQL attempts to start.
This is a brand new physical box and our first SQL2014. Not that that has anything to do with it.
April 2, 2015 at 9:05 am
If IP All is set to No and if the IP addresses tab has some IP addresses that have ‘Enabled’ set to ‘Yes’ but the actual IP is no longer active on the system, SQL Server service fails to start with an error message like that.
-- Gianluca Sartori
April 2, 2015 at 9:08 am
Understood. However, and I have checked and double checked all of the settings and they are all right. If any of those settings were wrong then SQL wouldn't start at all though either. It starts fine except when the server restarts. We just put the Automatic delay and all is good.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply