Microsoft SQL Sever 2014 Express Advanced SP2 (version 12.2.5000.0) fails to start after TLS 1.0 is disabled.

Matrix2020 26 Reputation points
2020-12-14T05:16:57.993+00:00

Our Nessus results recommended to disable TLS 1.0 on our Windows Server 2012 R2 standard server. However once we disable TLS 1.0 (using Registry Editor) and enable TLS 1.1 and 1.2 on the server, the Microsoft SQL Sever 2014 Express Advanced SP2 (version 12.2.5000.0) fails to start.

When we try to start the SQL Server, we see this error:
“Windows could not start SQL Server (SQLEXPRESS) on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 5023.”

The System Event Log has the this error:
"A fatal error occurred while creating an SSL client credential. The internal error state is 10013."

After enabling TLS 1.0 (using Registry Editor), the SQL Server (SQLEXPRESS) can start.

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
12,815 questions
{count} votes

Accepted answer
  1. Shashank Singh 6,246 Reputation points
    2020-12-14T09:09:16.223+00:00

    TDSSNIClient initialization failed with error 0x139f, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The group or resource is not in the correct state to perform the requested operation.

    I can see similar error documented in this tls-1-2-support-for-sql-server-2008-2008-r2-2012-and-2014 The solution mentioned is

    The above errors are reported because the SQL Server client driver fixes were not applied on the server. Please refer KB3135244 and apply the applicable client driver fixes on the server. In the KB link go to Client component downloads and download and install the respective client component you are using and then I guess it should work.

    PS: I strongly suggest you to upgrade to SQL Server 2014 SP3 and above, the issue seems more related to internal MS problem and SP should solve this


1 additional answer

Sort by: Most helpful
  1. AmeliaGu-MSFT 13,961 Reputation points Microsoft Vendor
    2020-12-15T07:40:33.53+00:00

    Hi @Matrix2020 ,

    Are there any other different version of SQL Server instances on your machine? According this old thread, , this issue may be caused by another instance of SQL Server with a lower version (SQL Server 2008, 2012) on the machine.
    And please make sure you have installed .NET framework version 3.5 SP1, or make sure your system is fully up to date via Windows Update.

    Best Regards,
    Amelia


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments