locked
SQL Services issue RRS feed

  • Question

  • Hi Team,

    When we restart SQL Server Services from Configuration manager, it's getting failing. This is SQL Server 2016 (AlwaysOn)

    But when i reboot windows server then sql services comingup successfully.

    2018-10-12 22:40:57.27 spid14s     Server is listening on [ 'any' <ipv6> 52065].
    2018-10-12 22:40:57.27 spid14s     Error: 26023, Severity: 16, State: 1.
    2018-10-12 22:40:57.27 spid14s     Server TCP provider failed to listen on [ 'any' <ipv4> 52065]. Tcp port is already in use.
    2018-10-12 22:40:57.27 spid14s     Error: 17182, Severity: 16, State: 1.
    2018-10-12 22:40:57.27 spid14s     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. 
    2018-10-12 22:40:57.27 spid14s     Error: 17182, Severity: 16, State: 1.
    2018-10-12 22:40:57.27 spid14s     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. 
    2018-10-12 22:40:57.27 spid14s     Error: 17826, Severity: 18, State: 3.
    2018-10-12 22:40:57.27 spid14s     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.
    2018-10-12 22:40:57.27 spid14s     Error: 17120, Severity: 16, State: 1.
    2018-10-12 22:40:57.27 spid14s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
    2018-10-12 22:40:57.28 spid8s      Database mirroring has been enabled on this instance of SQL Server.

    Saturday, October 13, 2018 5:43 AM

Answers

  • Hi Shashank,

    I compared this server with other servers. But i didn't find any difference.

    I can able to restart sql services in all other servers.

    Did you checked that your machine is patched with KB article what the blog was suggesting. There are 2 columns KB that introduced the regression and KB that fixed it. DID YOU MADE SURE you double checked that NO such KB is affecting your environment

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    • Marked as answer by VijayKSQL Wednesday, October 17, 2018 5:36 PM
    Monday, October 15, 2018 8:21 AM

All replies

  • What you are seeing may be related to some windows hotfix please refer to below blog

    https://blogs.msdn.microsoft.com/psssql/2018/07/26/july-10-2018-windows-updates-cause-sql-startup-issues-due-to-tcp-port-is-already-in-use-errors/

    Make sure you read it completely there are lot of things in the blog 


    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    Saturday, October 13, 2018 7:57 AM
  • Looks something similar:

    Here

    Saturday, October 13, 2018 8:32 PM
  • Hi Shashank,

    I compared this server with other servers. But i didn't find any difference.

    I can able to restart sql services in all other servers.

    Monday, October 15, 2018 5:55 AM
  • Hi Vijay,

    You have posted the error, in the error we have "Tcp port is already in use.".

    Please can you check, Is some other service already listening to the port?

    Regards,

    Sharat



    • Edited by SharatGupta Monday, October 15, 2018 6:56 AM
    Monday, October 15, 2018 6:55 AM
  • Hi Sharat,

    no other service listening this port.

    Monday, October 15, 2018 7:34 AM
  • Hi Vijay,

    Please can you try restarting the SQL Server service from Services.

    There are multiple ways to start as SQL Server service.

    1) From command prompt using "netstart" command.

    2) From Configuration manager

    3) From Services.

    Try restarting from Services.

    Sharat

    Monday, October 15, 2018 7:55 AM
  • Hi Shashank,

    I compared this server with other servers. But i didn't find any difference.

    I can able to restart sql services in all other servers.

    Did you checked that your machine is patched with KB article what the blog was suggesting. There are 2 columns KB that introduced the regression and KB that fixed it. DID YOU MADE SURE you double checked that NO such KB is affecting your environment

    Cheers,

    Shashank

    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it

    My TechNet Wiki Articles

    MVP

    • Marked as answer by VijayKSQL Wednesday, October 17, 2018 5:36 PM
    Monday, October 15, 2018 8:21 AM
  • Hi Vijay,

    You have said: "service restart from Configuration manager restart fails" and "on rebooting windows server SQL service starts" on this particular machine, Correct?

    I read some Microsoft documentation on AlwaysOn

    There are multiple instances of SQL running on multiple Nodes under a Cluster in AlwaysOn.

    I would like to know How many Nodes and SQL Instances you have on this Cluster? Is it a valid question.

    Regards

    Sharat

    Monday, October 15, 2018 10:38 AM
  • To me this sounds like something else is using the port, and you have configured a "static" post (not dynamic) meaning that SQL Server refuses to start if the port isn't available. Just what you asked for. I.e., either hunt down whatever is using the port, or change the port that your SQL Server is using to dynamic or some other post which is available (for sure).

    Tibor Karaszi, SQL Server MVP (Web Blog)

    Tuesday, October 16, 2018 6:39 AM