cannot start SQL Server 2019 after windows update but now works after go back to previous version of windows 10

0

I've been working with SQL Server 2019 for months now on a stand-alone machine. After I updated Windows 10 on 11/15/20, I can no longer start the service, though I can still start my 2017 version of SQL Server just fine (through SSMS or configuration manager).

Meanwhile, even though uninstalling the most recent Windows 10 updates didn't help me, using Recovery to go back to the previous version of Windows 10 did make it possible to start the SQL server service.

So my question has now become how do I proceed going forward? I can pause window updates for 35 days, but at some point, it seems that I am forced to update. How do I prevent the interruption of my SQL Server service?

Also would still love to know how to deal with Service master key errors as outline below.

Not clear to me how to deal with the Service Master key errors like this:

2020-11-30 16:20:48.65 spid9s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2020-11-30 16:20:48.65 spid9s      An error occurred during Service Master Key initialization. SQLErrorCode=33095, State=1, LastOsError=2.

Since I cannot use T-SQL to alter it since I can even get into the program, is there some other way to modify it? Do the subsequent errors all follow from this failure?

If I uninstall and reinstall the 2019 version, will I be able to attach the databases that are already attached to this instance of 2019? Or would I only be able to restore them from the latest backups?

Here's the error log file:

2020-11-30 16:20:47.44 Server      Microsoft SQL Server 2019 (RTM-GDR) (KB4517790) - 15.0.2070.41 (X64) 
    Oct 28 2019 19:56:59 
    Copyright (C) 2019 Microsoft Corporation
    Standard Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 19041: )

2020-11-30 16:20:47.44 Server      UTC adjustment: -5:00
2020-11-30 16:20:47.44 Server      (c) Microsoft Corporation.
2020-11-30 16:20:47.45 Server      All rights reserved.
2020-11-30 16:20:47.45 Server      Server process ID is 12908.
2020-11-30 16:20:47.45 Server      System Manufacturer: 'HP', System Model: 'HP Pavilion Desktop 590-p0xxx'.
2020-11-30 16:20:47.45 Server      Authentication mode is WINDOWS-ONLY.
2020-11-30 16:20:47.45 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLSERVER2019\MSSQL\Log\ERRORLOG'.
2020-11-30 16:20:47.45 Server      The service account is 'NT Service\MSSQL$SQLSERVER2019'. This is an informational message; no user action is required.
2020-11-30 16:20:47.45 Server      Registry startup parameters: 
     -d C:\Program Files\Microsoft SQL Server\MSSQL15.SQLSERVER2019\MSSQL\DATA\master.mdf
     -e C:\Program Files\Microsoft SQL Server\MSSQL15.SQLSERVER2019\MSSQL\Log\ERRORLOG
     -l C:\Program Files\Microsoft SQL Server\MSSQL15.SQLSERVER2019\MSSQL\DATA\mastlog.ldf
2020-11-30 16:20:47.45 Server      Command Line Startup Parameters:
     -s "SQLSERVER2019"
2020-11-30 16:20:47.49 Server      SQL Server detected 1 sockets with 6 cores per socket and 6 logical processors per socket, 6 total logical processors; using 6 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2020-11-30 16:20:47.49 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2020-11-30 16:20:47.49 Server      Detected 32595 MB of RAM. This is an informational message; no user action is required.
2020-11-30 16:20:47.49 Server      Using conventional memory in the memory manager.
2020-11-30 16:20:47.49 Server      Page exclusion bitmap is enabled.
2020-11-30 16:20:47.57 Server      Buffer Pool: Allocating 8388608 bytes for 5215255 hashPages.
2020-11-30 16:20:47.60 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2020-11-30 16:20:47.62 Server      Buffer pool extension is already disabled. No action is necessary.
2020-11-30 16:20:47.66 Server      Query Store settings initialized with enabled = 1, 
2020-11-30 16:20:47.66 Server      The maximum number of dedicated administrator connections for this instance is '1'
2020-11-30 16:20:47.67 Server      This instance of SQL Server last reported using a process ID of 4420 at 11/30/2020 4:10:09 PM (local) 11/30/2020 9:10:09 PM (UTC). This is an informational message only; no user action is required.
2020-11-30 16:20:47.67 Server      Node configuration: node 0: CPU mask: 0x000000000000003f:0 Active CPU mask: 0x000000000000003f:0. This message describes the NUMA configuration for this computer. This is an informational message only. No user action is required.
2020-11-30 16:20:47.68 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2020-11-30 16:20:47.69 Server      In-Memory OLTP initialized on standard machine.
2020-11-30 16:20:47.76 Server      [INFO] Created Extended Events session 'hkenginexesession'

2020-11-30 16:20:47.76 Server      Database Instant File Initialization: enabled. For security and performance considerations, see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2020-11-30 16:20:47.77 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.
2020-11-30 16:20:47.78 Server      clflushopt is selected for pmem flush operation.
2020-11-30 16:20:47.79 Server      Software Usage Metrics is disabled.
2020-11-30 16:20:47.79 spid9s      Starting up database 'master'.
2020-11-30 16:20:48.08 spid9s      2 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2020-11-30 16:20:48.10 Server      CLR version v4.0.30319 loaded.
2020-11-30 16:20:48.27 spid9s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2020-11-30 16:20:48.38 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2020-11-30 16:20:48.65 spid9s      Service Master Key could not be decrypted using one of its encryptions. See sys.key_encryptions for details.
2020-11-30 16:20:48.65 spid9s      An error occurred during Service Master Key initialization. SQLErrorCode=33095, State=1, LastOsError=2.
2020-11-30 16:20:48.68 spid9s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2020-11-30 16:20:48.69 spid9s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2020-11-30 16:20:48.75 spid9s      SQL Trace ID 1 was started by login "sa".
2020-11-30 16:20:48.75 spid9s      Server name is 'DESKTOP-97RP1DK\SQLSERVER2019'. This is an informational message only. No user action is required.
2020-11-30 16:20:48.76 spid22s     Error: 17190, Severity: 16, State: 1.
2020-11-30 16:20:48.76 spid22s     Initializing the FallBack certificate failed with error code: 15, state: 29, error number: 0.
2020-11-30 16:20:48.76 spid22s     Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2020-11-30 16:20:48.76 spid22s     Error: 17182, Severity: 16, State: 1.
2020-11-30 16:20:48.76 spid22s     TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property. 
2020-11-30 16:20:48.76 spid22s     Error: 17182, Severity: 16, State: 1.
2020-11-30 16:20:48.76 spid22s     TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property. 
2020-11-30 16:20:48.76 spid22s     Server is listening on [ ::1 <ipv6> 50022].
2020-11-30 16:20:48.76 spid14s     Starting up database 'mssqlsystemresource'.
2020-11-30 16:20:48.76 spid25s     Starting up database 'CBOE2020'.
2020-11-30 16:20:48.76 spid26s     Starting up database 'CBOE2018'.
2020-11-30 16:20:48.76 spid28s     Starting up database 'AdventureWorksDW2012'.
2020-11-30 16:20:48.76 spid22s     Server is listening on [ 127.0.0.1 <ipv4> 50022].
2020-11-30 16:20:48.76 spid27s     Starting up database 'msdb'.
2020-11-30 16:20:48.76 spid22s     Server local connection provider is ready to accept connection on [ \\.\pipe\sqlsatellitelaunchSQLSERVER2019 ].
2020-11-30 16:20:48.76 spid22s     Resource governor reconfiguration encountered an issue (HRESULT code : 0x80040002, reason: Construction of Launchpad Connection failed), while sending active external resource pool ids to launchpad. This will not fail reconfigure.
2020-11-30 16:20:48.77 spid22s     Error: 17826, Severity: 18, State: 3.
2020-11-30 16:20:48.77 spid22s     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.
2020-11-30 16:20:48.77 spid22s     Error: 17120, Severity: 16, State: 1.
2020-11-30 16:20:48.77 spid22s     SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the operating system error log for information about possible related problems.
ms-sql
asked on Super User Nov 30, 2020 by mbd • edited Dec 2, 2020 by Ramhound

0 Answers

Nobody has answered this question yet.


User contributions licensed under CC BY-SA 3.0